[jbosscache-dev] Jarring jars
Manik Surtani
manik at jboss.org
Tue Feb 20 09:56:11 EST 2007
Fair enough; and for specific cases (such as microcontainer in
2.1.0/2.2.0 for the IOC stuff) we could just package the 4 mc jars
into a single one and use that as a single dep ... ?
--
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 16 Feb 2007, at 20:03, Vladimir Blagojevic wrote:
> I vote for this approach.
>
> On Fri, 2007-02-16 at 10:42 -0600, Brian Stansberry wrote:
>> For proper AS build integration, the component-info.xml in
>> repository.jboss.com for a JBC release should include this kind of
>> thing:
>>
>> <import componentref="javassist">
>> <compatible version="3.3.0.GA"/>
>> <compatible version="3.4.GA"/>
>> </import>
>>
>> Properly maintaining that element can drive the documentation of
>> compatibility.
>>
>> Re: reducing dependencies, how about (for 2.0):
>>
>> 1) Standardize on JGroups 2.5 and chuck concurrent.jar.
>> 2) Chuck JDK 1.4 compatibility, which IMHO is a lot of trouble for
>> little gain. Since AS 4.2 ships with 1.4.x, we're going to have
>> to do
>> bug fixes on 1.4.x for a number of years. That makes it a semi-
>> living
>> branch for those non-JBAS users who require JDK 1.4.
>> 3) See if any of the PojoCache dependencies can be eliminated or
>> reduced
>> to optional (e.g. microcontainer).
>
>
> _______________________________________________
> jbosscache-dev mailing list
> jbosscache-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
More information about the jbosscache-dev
mailing list