[
https://jira.jboss.org/jira/browse/JBIDE-3896?page=com.atlassian.jira.plu...
]
Rob Stryker resolved JBIDE-3896.
--------------------------------
Resolution: Done
implemented. There's a checkbox in the wizard which allows you to clone a config
immediately.
Once the config is coppied, the following becomes part of the launch configuration:
-Djboss.server.base.url=file:/home/rob/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_4.2_Server_(1)/jbossConfig/
This *cannot* be changed by the user. Similar to other restricted fields (and as in the
Tomcat Server Adapter), there will be no error upon a change, however, the change will not
persist. For example, if you open the launch confiuguration, change the value, save it,
and re-open the configuration, you'll see the change was not persisted.
Add possibility to create a new JBoss AS profile when create a new
server
-------------------------------------------------------------------------
Key: JBIDE-3896
URL:
https://jira.jboss.org/jira/browse/JBIDE-3896
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.0.0.CR2
Environment: JBDS 2.0.0.CR2
Reporter: Joao Paulo Viragine
Assignee: Rob Stryker
Priority: Minor
Fix For: 3.1.0.M1
Attachments: JBIDE-3896.jpg
When we are developing, sometimes we need various JBoss AS profiles.
It would be nice if we could create a new JBoss AS profile (to preserve default or
production original) when create a new server
.
JBDS/JBoss Tools may ask for base profile (for be based on) and then make a
"copy" (only conf, deploy and lib folders) to the new specified profile name.
--
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