[jbosscache-dev] Re: Logging jars

[Bela Ban]

They should, but they are not... :-)

Manik Surtani wrote:
> Ant scripts should pick this up correctly anyway.  .sh and .bat 
> scripts should also be written with a for loop when building 
> classpaths rather than hardcoding libs; I'll have a look and check 
> that these are in tact.
> -- 
> Manik Surtani
>
> Lead, JBoss Cache
> JBoss, a division of Red Hat
>
> Email: manik at jboss.org
> Telephone: +44 7786 702 706
> MSN: manik at surtani.org
> Yahoo/AIM/Skype: maniksurtani
>
>
> On 12 Sep 2006, at 13:41, Ben Wang wrote:
>
>> +1. We currently have many scripts that use for tutorial and 
>> examples. How can we sync them up quickly between each release and 
>> test them out can be the key.
>>
>> -----Original Message-----
>> From: jbosscache-dev-bounces at lists.jboss.org 
>> [mailto:jbosscache-dev-bounces at lists.jboss.org] On Behalf Of Bela Ban
>> Sent: Tuesday, September 12, 2006 4:47 AM
>> To: Manik Surtani
>> Cc: jbosscache-dev at lists.jboss.org
>> Subject: Re: [jbosscache-dev] Re: Logging jars
>>
>> I'm all for version numbers in JARs, but we also need scripts that add
>> (e.g.) all JARs in a given dir to the classpath, rather than list them.
>> If we list them explicitly, we have to change those scripts when we 
>> change the JAR name.
>>
>> Manik Surtani wrote:
>>> I was trying it out as per our discussions on dev.
>>>
>>> Also, I think it is best to have version numbers on such jars just so
>>> we're clear on what versions we're using (I couldn't tell which
>>> version of JCL we had before, for example)
>>>
>>> What does everyone think about version numbers in the jars we use,
>>> like this?
>>>
>>> Cheers,
>>> -- 
>>> Manik Surtani
>>>
>>> Lead, JBoss Cache
>>> JBoss, a division of Red Hat
>>>
>>> Email: manik at jboss.org
>>> Telephone: +44 7786 702 706
>>> MSN: manik at surtani.org
>>> Yahoo/AIM/Skype: maniksurtani
>>>
>>>
>>> On 11 Sep 2006, at 18:29, Brian Stansberry wrote:
>>>
>>>> Hey dude,
>>>>
>>>> Looks like you checked in commons-logging-1.1.jar and 
>>>> log4j-1.2.13.jar.
>>>> Was this intentional?  These files have a different name from what's
>>>> in the Eclipse project classpath, so that breaks Eclipse.  I can
>>>> check in a fixed Eclipse .classpath file, but don't want to if you're
>>>> going to revert the library change.
>>>>
>>>> Brian Stansberry
>>>> Lead, AS Clustering
>>>> JBoss, a division of Red Hat
>>>
>>> _______________________________________________
>>> jbosscache-dev mailing list
>>> jbosscache-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
>>>
>>
>> -- 
>> Bela Ban
>> Lead JGroups / Manager JBoss Clustering Group JBoss - a division of 
>> Red Hat
>>
>> _______________________________________________
>> jbosscache-dev mailing list
>> jbosscache-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
>
>

-- 
Bela Ban
Lead JGroups / Manager JBoss Clustering Group
JBoss - a division of Red Hat