[jboss-dev] new shared JBOSS_HOME/server/lib directory

[Aleksandar Kostadinov]

I'm not the best one to give opinion on that but here it is.

The change will complicate things and confuse users. As well doesn't 
seem scalable to me. When we have more server configurations, we'll need 
more lib directories (platforms more affected)... The change could break 
user utilities that expect the old layout, etc.

IMHO a straightforward approach will be to remove the 
JBOSS_HOME/server/*/lib directories altogether and have all libraries in 
JBOSS_HOME/lib or another directory. Then appropriate libraries for 
every server configuration be selected in a configuration file 
(conf/jboss-service.xml?).

Best Regards,
Aleksandar

Dimitris Andreadis wrote, On 11/04/2008 12:38 PM (EEST):
> The new JBOSS_HOME/server/lib directory pointed to at by the 
> jboss.shared.lib.url property currently contains the libraries shared by 
> the default and all configurations.
> 
> So server/default/lib is now empty and server/all/lib contains only:
> 
> avalon-framework.jar
> hibernate-jbosscache2.jar
> jacorb.jar
> jbosscache-core.jar
> jbosscache-pojo.jar
> jgroups.jar
> 
> The new directory is added to the classpath in conf/jboss-service.xml:
> 
>    <classpath codebase="${jboss.server.lib.url}" archives="*"/>
>    <classpath codebase="${jboss.shared.lib.url}" archives="*"/>
> 
> The minimal config remains unchanged.
> 
> https://jira.jboss.org/jira/browse/JBAS-6158
> 
> You probably need to cleanup your build/output/** directory to pick up 
> the change at your next svn update.
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development