[
https://jira.jboss.org/jira/browse/JBIDE-4374?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4374:
--------------------------------------------
IMO if users do relative to metadata that is their own problem ;)
I follow your argument but it just feels very asymmetric.
But a lot of this can be helped by making the ui show hints about where the actual
deployments go (tooltips, hyperlinks, <default deploy> in ui when field is blank
etc.).
btw. I still think we should have a jboss_config_dir variable instead of just the
{jboss_config} that just gives the name..
Modules / deployment page
-------------------------
Key: JBIDE-4374
URL:
https://jira.jboss.org/jira/browse/JBIDE-4374
Project: 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