[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:comment-tabpanel&focusedCommentId=12733973#comment-12733973 ] 

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