[
https://jira.jboss.org/jira/browse/JBIDE-5597?page=com.atlassian.jira.plu...
]
Rob Stryker resolved JBIDE-5597.
--------------------------------
Resolution: Partially Completed
To be clear, when the server is started up is when it adds all the possible locations for
the deployment scanner to scan. So modifying the deployment page or enabling custom
folders for each module will *not* be recognized without a server restart.
However I have now fixed it so that it should recognize a switch to any folder already
mentioned in the editor before startup.
To be clear, the suggested policy of changing a project's deploy location is:
1) UNDEPLOY the module so it is removed from the old legacy location
2) change the module's deploy location in the editor
2a) If the server is started and the new deploy location is one that likely was unknown
by the tooling during the initial startup, restart the server
3) redeploy the module
Full Publish of ESB projects does not redeploy and also can't
deploy at all from eclipse workspace directory (deploy option)
----------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-5597
URL:
https://jira.jboss.org/jira/browse/JBIDE-5597
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.M4
Environment: Fedora 9, SOA-P 5.0 Beta1, JBDS 3 M4
Reporter: Aaron Pestel
Assignee: Rob Stryker
Fix For: 3.1.0.CR2
Attachments: TestDeploy.zip
Create a new ESB project, add it to a SOA-P server, in the JBossAS view, right-click on
the project and choose "Full Publish" - it doesn't republish the project
like it used to. Can also modify the project (jboss-esb.xml) and select full publish and
it still won't republish, have to remove project from server and re-add project to
server.
JBDS project now seems to be setup by default to deploy to JBoss deploy directory as
opposed to the Ecplise workspace. I changed it to deploy to the workspace (like I think
previoius versions defaulted to), and couldn't even get the project to deploy that
way.
If this isn't reproducible enough, please let me know and I'll attach a project
with more clear steps.
Thanks!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira