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

[Galder Zamarreno]

Hmmmm, we're gonna have users screaming about this.

In the past, if you're developing a client app in Eclipse, you only 
needed jbossall-client.jar and log4j.jar but this won't be the case with 
AS5 as I've just found out when trying to run a client app against 
trunk. Eclipse for example does not read manifest classpath entries:

http://forums.bea.com/thread.jspa?threadID=570001075

I've just talked to Max who confirmed it. I'll let him explain the gory 
details of Eclipse.

Cheers,

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 at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>
>>
>>
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development

-- 
Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat