[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] objectweb.asm 3.1
- From: Chris Aniszczyk <zx@xxxxxxxxxxxxxxxxx>
- Date: Tue, 3 Feb 2009 16:17:11 -0600
- Delivered-to: firstname.lastname@example.org
+1 for 3.1
A goal for Galileo should be to remove redundant dependencies and use the latest possible.
On Tue, Feb 3, 2009 at 4:15 PM, Scott Lewis <slewis@xxxxxxxxxxxxxxxxx>
Jan and Markus,
It seems that the platform is now using objectweb asm version 3.1 and we are currently using version 3.0 (for r-OSGi dynamic proxy creation)
Our import package in the r-osgi bundle currently looks like this:
So with this markup, 3.1 is *not* included in the version range. If I set the version range to include 3.1 everything compiles ok using the platform provided 3.1. I haven't done any runtime testing though.
So, my question is: can/could we use 3.1 rather than 3.0? If so, it would save us some distribution size/dependency.
Here's the platform CQ for ASM 3.1: http://dev.eclipse.org/ipzilla/show_bug.cgi?id=3064
If we are to use 3.1, we would need to submit a piggyback CQ pretty soon...but that should be very easy.
ecf-dev mailing list
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465