I think we currently need a simple out-of-the-box solution,
just something that won't bloat our distro too much.
Scott's/Dimitris's shared dir does just that.
What you're suggesting Sacha is something OBR (OSGi Bundle Repository)
already does.
.lnk is actually 'equivalent' to a requirement in OSGi import
or our ClassLoadingMetaData's module requirement.
Then it's just a matter of how we implement this requirement/jar pulling .
e.g. where do we put this dependency jars, how much pulling we allow, etc.
Sacha Labourey wrote:
Another option would be to have a "*.lnk" (or whatever
*.alias)
extension which would just contains a URL to the new target (absolute or
relative). That way we get the best of both world.
i.e. default/lib/ would contain things such as:
avalon-framework.jar.lnk
hibernate-jbosscache2.jar.lnk
jacorb.jar.lnk
jbosscache-core.jar-lnk
jbosscache-pojo.jar.lnk
jgroups.jar.lnk
and this new referral deployer would simply dynamically add to the
deployment list the target JAR minus the ".lnk" extension.
Thoughts?
> -----Original Message-----
> From: jboss-development-bounces(a)lists.jboss.org [mailto:jboss-
> development-bounces(a)lists.jboss.org] On Behalf Of Aleksandar Kostadinov
> Sent: mardi, 4 novembre 2008 13:48
> To:
JBoss.org development list
> Subject: Re: [jboss-dev] new shared JBOSS_HOME/server/lib directory
>
> 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(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-development
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development