Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 5.0.0.M3
-
Component/s: installer
-
Labels:None
Description
Because JBossAS Tools has found most people using EAP are using their own downloaded versions of EAP, these versions are secured. Therefore for out-of-the-box experience, users must switch the deployment location to server-based, or unsecure their EAP, etc.
ASTools has switched to defaulting EAP to server-based, and so a solution needs to be provided to allow JBDS to auto-configure the bundled EAP and created server to default to metadata deployment
Gliffy Diagrams
Issue Links
- is related to
-
JBIDE-9319
Default deploy location for JBDS does not work with EAP applications
-
- Closed
-
- relates to
-
JBIDE-9643
Using default deployment location from JBoss AS Runtime
-
- Closed
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
note, the question is wether the behavior is different from JBDS 4.x concerning what the default deploy location will be for the bundled server.
if its the same fine - if not the same then should be fixed.
Max Rydahl Andersen
added a comment - note, the question is wether the behavior is different from JBDS 4.x concerning what the default deploy location will be for the bundled server.
if its the same fine - if not the same then should be fixed. The runtime detection plugin explicitly sets the default server deployment to the server based deployment.
Fixing JBIDE-9319 doesn't have any effect on the runtime detection plugin.
The behavior is the same in JBDS 4.x and JBDS 5.x.
Snjezana Peco
added a comment - The runtime detection plugin explicitly sets the default server deployment to the server based deployment.
Fixing JBIDE-9319 doesn't have any effect on the runtime detection plugin.
The behavior is the same in JBDS 4.x and JBDS 5.x. From my understanding this jira, when I install JBDS with bundled EAP and open up a new workspace I should have server configured to deploy to metadata. This does not happen on jbdevstudio-product-eap-linux-gtk-5.0.0.v201109071858R-H28-M3.jar
Libor Zoubek
added a comment - From my understanding this jira, when I install JBDS with bundled EAP and open up a new workspace I should have server configured to deploy to metadata. This does not happen on jbdevstudio-product-eap-linux-gtk-5.0.0.v201109071858R-H28-M3.jar The requirement was that the deployment location should be set by JBoss AS Tools. The Runtime detection plugin doesn't change the deployment location anymore.
Snjezana Peco
added a comment - The requirement was that the deployment location should be set by JBoss AS Tools. The Runtime detection plugin doesn't change the deployment location anymore. Ah so, then it's verified - adding server the old way produces same default deploy dir as by using runtime detector
Libor Zoubek
added a comment - Ah so, then it's verified - adding server the old way produces same default deploy dir as by using runtime detector 
Rob - in which versions does this need to be fixed ?