[jbosstools-issues] [JBoss JIRA] (JBIDE-12424) Specifying a non-default configuration file in non-default profile doesn't work as expected via JBDS 5

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-12424.
---------------------------------

    Release Notes Text: 
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
         Fix Version/s: 4.0.0.CR1
                            (was: 4.1.0.Alpha1)
            Resolution: Done

    
> Specifying a non-default configuration file in non-default profile doesn't work as expected via JBDS 5
> ------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-12424
>                 URL: https://issues.jboss.org/browse/JBIDE-12424
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 3.3.0.Final
>            Reporter: Usman Saleem
>            Assignee: Rob Stryker
>            Priority: Critical
>              Labels: f2f2012
>             Fix For: 4.0.0.CR1
>
>
> Specifying a non-default configuration file in non-default profile doesn't work as expected via JBDS 5. When attempt to start the server, following error is raised:
> The server's configuration file does not exist: /jbeap6/standalone/configuration/jbeap6/custom/configuration/standalone-full-ha.xml
> Looks like jboss tool automatically appending /jbeap6/standalone/configuration
> Note that the custom configuration can be launched via command line as:
> ./standalone.sh -Djboss.server.base.dir=../custom --server-config=standalone-full-ha.xml

--
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