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

[Scott Stark]

What does eclipse need then, bundle manifest headers? Ship a ant 
script/java class that lets the user make an uber jar from the manifest 
classpath.

Sacha Labourey wrote:
> I agree, this will be a big usability issue. For the sake of making OUR life
> easier (patching), we are going to make EVERYBODY's life more difficult,
> that's nonsense. If you need a patching mechanism, write a script which will
> just do that, but do not impact user usability.
>
>   
>> -----Original Message-----
>> From: jboss-development-bounces at lists.jboss.org [mailto:jboss-
>> development-bounces at lists.jboss.org] On Behalf Of Galder Zamarreno
>> Sent: jeudi, 6 novembre 2008 16:48
>> To: JBoss.org development list
>> Subject: Re: [jboss-dev] jbossall-client.jar now references external
>> libs
>>
>> 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,
>>
>>