[ https://issues.jboss.org/browse/JBIDE-12424?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-12424: ---------------------------------------- Fix Version/s: 4.1.0.Alpha1 Priority: Critical (was: Major) Labels: f2f2012 (was: ) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12424?page=com.atlassian.jira.plugi... ] Usman Saleem commented on JBIDE-12424: -------------------------------------- Max, I tried changing parameters as VM arguments (such as -Djboss.server.base.dir), however, these specific parameters are overridden by plugin even if we try to modify them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12424?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-12424: -------------------------------- Release Notes Text: (was: I am able to get this scenario working as follows: - Create a custom profile in EAP6 directory by copying 'standalone' to 'custom' - Rename 'standalone' to 'standalone_' or similar - In JBDS 5, Create a new Runtime Environment for EAP 6 - Browser for non default configuration file in 'custom' and specify the path: /jbeap6/custom/configuration/standalone-full-ha.xml NOTE: The browse button will give an absolute path, and the wizard will show an error because absolute paths are not allowed. Currently we do not turn this into a relative path, but, the user is able to simply remove the absolute portion and replace with ../../custom/configuration/standalone-full-ha.xml - In the 'Servers' view, double click on defined runtime environment to bring 'Overview' - Open Launch Configuration - Uncheck Always update arguments related to runtime (checked cause default values to be appended next time it is launched) - Specify -Djboss.server.base.dir=../custom as VM argument - Notice the defaults 'standalone' path for logging, update them if needed - Apply/OK - Attempt to start the server This works 100% as expected. SO it seems the only issue here is that the 'browse' button in the runtime wizard returns a global path rather than a relative path. I'm committing a fix for that single issue now. :D) I am able to get this scenario working as follows: - Create a custom profile in EAP6 directory by copying 'standalone' to 'custom' - Rename 'standalone' to 'standalone_' or similar - In JBDS 5, Create a new Runtime Environment for EAP 6 - Browser for non default configuration file in 'custom' and specify the path: /jbeap6/custom/configuration/standalone-full-ha.xml NOTE: The browse button will give an absolute path, and the wizard will show an error because absolute paths are not allowed. Currently we do not turn this into a relative path, but, the user is able to simply remove the absolute portion and replace with ../../custom/configuration/standalone-full-ha.xml - In the 'Servers' view, double click on defined runtime environment to bring 'Overview' - Open Launch Configuration - Uncheck Always update arguments related to runtime (checked cause default values to be appended next time it is launched) - Specify -Djboss.server.base.dir=../custom as VM argument - Notice the defaults 'standalone' path for logging, update them if needed - Apply/OK - Attempt to start the server This works 100% as expected. SO it seems the only issue here is that the 'browse' button in the runtime wizard returns a global path rather than a relative path. I'm committing a fix for that single issue now. :D -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12424?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-12424: ------------------------------------- While I understand your point, we're trying to balance a few different things here. We definitely don't want to clutter the UI with tons of options, so we have no UI for setting the server base dir. The UI for the new runtime allows you to select a config file, which really could be anywhere on your machine. You could even have your standalone-ha.xml over in /home/rob and have the relative path be ../../../../../home/rob/standalone-ha.xml This only designates what your config file is. It does not designate your server base directory. A user who wants a new configuration file AND a new base directory would need to dig through the options (in this case the launch config) to set that flag. But users who only want to change the config file and have it live somewhere else on their machine unrelated to a server base directory can do that all through the runtime wizard now without errors. I guess I disagree, but you're welcome to open another jira to track that specific issue if you really feel there should be more UI for verifying the base directory or if you can come up with another use case that seems to fail or is not-intuitive enough. Like I said, it's a fine line between flexibility and clutter. I feel that currently it's balanced pretty well, but if you really see a specific workflow that fails, please open another bug and we can discuss it :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12424?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-12424. --------------------------------- I verified that it works as Rob explained - if you want to use a custom dir instead of standalone there's no other way than fiddling with the launch configuration. I also checked that the browse button returns relative path to the config xml as it should. Tested with JBDS 6.0.0.CR1 B111. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira