[
https://issues.jboss.org/browse/JBIDE-11182?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-11182:
-------------------------------------
The legitimate issue with doing this, Max, is that then a user may deploy an app (such as
one that uses AOP) first, and then decide it needs to be loaded immediately on startup,
before the server completes its startup routine. In this case, the user would deploy it
first, and THEN change where it's "deployed to", for example moving it from
metadata to the in-server area. There will be no cleanup of the previously deployed
version, and then there will be one version in the server location, one in metadata, and
hte deployment scanner instructed to add both.
This will lead to duplicate versions of the app trying to be loaded by jboss, and this
will lead to errors.
The workflow under this situation would need to be something like:
1) Create server / app
2) Change viewer to show all
3) Change the deploy setting / location
4) Add / deploy app to server
5) clean up the old version manually
This may be confusing for some users. Some users may end up deploying it first, then
changing the value, then dealing with the two deployed versions and being confused for a
time
make show only deployed the default for modules page
----------------------------------------------------
Key: JBIDE-11182
URL:
https://issues.jboss.org/browse/JBIDE-11182
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Fix For: 3.3.0.Beta2
as discussed in JBIDE-10733
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira