Re: [jboss-dev] jbossall-client.jar now references external libs

Is there going to be a maven2 pom for the jbossall-client.jar that references all dependent jars that are in the manifest class-path? The 5.0.0.beta4 one currently does not. Aaron On 12/06/2008, at 1:28 AM, Dimitris Andreadis wrote: > Yes, they'll need the whole jboss/client dir. > > Max Rydahl Andersen wrote: >> I'm curious how this affects users (and hence tooling). >> I assume users now instead of having jbossall-client.jar on the >> classpath will need to have an exact >> copy of client/*.jar etc. when running against jboss ? >> /max >>> Paul changed jbossall-client.jar so now instead of embedding the >>> content of the other client >>> libraries, it now references them through MANIFEST.MF Class-Path entry. >>> >>> This makes it possible to introduce drop-in replacements for client >>> libs, if needed, without >>> worrying about jbossall-client.jar >>> >>> http://jira.jboss.com/jira/browse/JBAS-4355 >>> _______________________________________________ >>> 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 _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development