[
https://jira.jboss.org/jira/browse/JBIDE-4374?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-4374:
---------------------------------------
Priority: Critical (was: Major)
Lets get this in - A minimal solution is a line per deployed module and a column saying
where it deploys.
Field is interpreted relative to the default deploy dir - i.e. for module named my.ear:
If field is blank it means default deploy dir,
"deploy.last" will mean it gets deployed to
<deploy_dir>/deploy.last/my.ear,
c:/mydeploys means it goes to c:/mydeploys/my.ear and
../anotherdeploydir means it goes to <deploy_dir>/../anotherdeploydir/my.ear
Questions to solve:
The last two examples here might be for directories that does not exist - what should our
warning/error handling be ?
Should all modules be shown there by default ? Or should it just be those users wanted to
customize ? (im mostly for all)
What if a module gets deleted - should the server remember forget it too or should users
delete it explicitly if customized so if they add the module back they don't have to
reconfigure ?
Modules / deployment page
-------------------------
Key: JBIDE-4374
URL:
https://jira.jboss.org/jira/browse/JBIDE-4374
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Reporter: Rob Stryker
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.1.0.GA
Create a Modules page in the server editor where you can specify the deployment location
of each module you'll be deploying. This is due to the usecase where you need one
module deployed to the default server location (for guaranteed early startup) but another
to the separated metadata or custom location.
--
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