4 Replies Latest reply on Oct 20, 2008 2:06 AM by starksm64

Addition of a "standard" configuration

dimitris Oct 17, 2008 12:02 PM

We need to look into adding the configuration used for our tck testing into our distribution under a new "standard" config.

The main problem is the increase in the distro by about 32mb, so one solution is to create a shared lib directory to store all the static libraries, e.g. a top level:

shared/lib

The various configs 'standard/all/defaul' could then point to that directory, rather than replicating the libs.

1. Re: Addition of a "standard" configuration

starksm64 Oct 17, 2008 2:04 PM (in response to dimitris)

Creating a share lib with the common jboss libs seems like the best compromise relative to the full canonical server we want to do. I would have it be under server so as not to confuse server/shared as a configuration.

We would need a new jboss.shared.lib.url system property defaulting to ${jboss.server.base.url}/lib
Actions
2. Re: Addition of a

dimitris Oct 18, 2008 3:59 AM (in response to dimitris)

Scott, you mean JBOSS_HOME/lib be the default? How are we going to distinguise the boot libs from the shared libs?
Actions
3. Re: Addition of a

alesj Oct 18, 2008 5:55 AM (in response to dimitris)

"dimitris@jboss.org" wrote:
you mean JBOSS_HOME/lib be the default?

No, I think he means JBOSS_HOME/server/lib.
See jboss system properties:
- http://www.jboss.org/community/docs/DOC-10730

This makes sense, unless you have a config named 'lib'. :-)
Actions
4. Re: Addition of a "standard" configuration

starksm64 Oct 20, 2008 2:06 AM (in response to dimitris)

Right, I mean JBOSS_HOME/server/lib is the default location of the shared lib. Unless of course you want an unambiguous, but annoying default of lib-yes-lib-not-a-config-named-lib ;)
Actions

Go to original post