[
https://issues.jboss.org/browse/GTNPORTAL-2449?page=com.atlassian.jira.pl...
]
Marko Strukelj commented on GTNPORTAL-2449:
-------------------------------------------
This is actually a hack:
-Dexo.conf.dir=$PWD/../standalone/configuration/gatein
-Dgatein.conf.dir=\\\${jboss.server.config.dir}/gatein
Both of these values refer to the same location on disk. Both have to be specified as
system properties, none of them initializes itself to the value of the other as a
fallback.
Also the code that uses exo.conf.dir doesn't resolve ${X} systax, while the code that
used gatein.conf.dir does.
The gatein.conf.dir syntax is better as you remove a dependency on system variables.
The issue with the proposed patch is that now everyone using GateIn would have to set
JBOSS_HOME environment property if I read this correctly, whereas until now this was not
necessary.
In terms of ergonomics it's a step back ...
I think the proper way to fix this is to address the issues I described in the beginning,
by:
- allowing using ${X} syntax to specify exo.conf.dir, or
- completely doing away with exo.conf.dir and only using gatein.conf.dir
In that case you don't need $PWD, nor $JBOSS_HOME any more.
I suspect there's enough mess around ConfigurationManager and exo.kernel.container
code that fixing this is not completely trivial.
Short of that, $PWD should be automatically used if $JBOSS_HOME is not explicitly set.
Can not start server when run script outside "bin"
directory on JBoss 7
-----------------------------------------------------------------------
Key: GTNPORTAL-2449
URL:
https://issues.jboss.org/browse/GTNPORTAL-2449
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Hai Nguyen
Attachments: GTNPORTAL-2449.patch
In file bin/standalone.conf, I see the property "exo.conf.dir" which declared
by $PWD/../standalone/configuration/gatein. So we can not start server if we stay where
outside "bin" directory
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira