Rob,
If possible, it seems the easier solution is to just switch both to
Maven dependencies right now. ASM probably should anyway, since it is so
small. For BCEL you can worry about making a small version later. I know
for a fact that ASM is available in a maven repo because iPOJO depends
on it. I would assume BCEL is available somewhere too.
-> richard
Rob Walker wrote:
I now have a "mangen" version which I've updated to use the newer
Felix searchpolicy classes.
The present version has two external components included in source form:
* mini-bcel - a heavily stripped down version of BCEL, with headers
under an Apache 1.1 license
* asm - originally from ObjectWeb and (c) France Telecom, but under
an open source BSD style license that I believe would permit it's
submission to the Felix SVN
In fact these are "either / or" components - since mangen can be
configured to use either a BCEL class scanner or an ASM class scanner.
Long term - I guess for the ASM part, it would be better to pull in an
ASM Jar from a suitable repository using Maven. The "mini-bcel" part
could be moved to full BCEL - this would result in needing a much
bigger BCEL JAR, since the stripped version is way smaller and just
includes the essential classes.
Problem I have right now is time - I'd like to submit mangen sooner
rather than later, and I don't have time to look at changing making
mangen and build to work in this way. Once in SVN, either I or someone
else can look at tidying this area up later?
So - is it legitimate and ok for me to submit these sources as-is,
leaving them with their respective license headers?
-- Rob
Ascert - Taking systems to the Edge
[EMAIL PROTECTED]
+44 (0)20 7488 3470
www.ascert.com
