BJ Hargrave wrote:
You are suggesting hosting modified copies of the JAR files created by
others. There is a whole set of legal issues here. You will need a legal
team to review these issues for all non Apache JARs.
Since, I assume, that we will only be dealing with well-known open
source licenses (or at least we can limit ourselves to them), I don't
expect this to be a major issue. Clearly, if these are libraries that we
are already bundlizing for current needs, then it really isn't any
different, since we are already "hosting modified copies" within
individual projects, this just centralizes that practice.
Not sure what you mean here? Perhaps this was true in the distant past.
But all the JARs published by OSGi today have the proper manifest headers.
If they don't please file a bug report.
When R4 was released, the OSGi JAR files did not include bundle manifest
headers, thus we had to create our own bundlized versions of them.
However, this is not the point of the comment...the point is simply that
we cannot expect (or force) everyone to use a build process we specify
for generating manifest headers, so we have to accept (at least for the
foreseeable future) that we will have to bundlize third party JARs. The
point of this proposal is to simply have a centralized place for this
effort.
-> richard
BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
[EMAIL PROTECTED]
Office: +1 407 849 9117 Mobile: +1 386 848 3788
"Richard S. Hall" <[EMAIL PROTECTED]>
08/01/2006 08:08 AM
Please respond to
[email protected]
To
[email protected]
cc
Subject
Re: [VOTE] Felix Commons Initiative
BJ Hargrave wrote:
[ ] +1 Accept the proposal.
[ ] 0 I don't care.
[ X ] -1 Reject the proposal.
I would rather see effort put into Maven to make it painfully simple for
all JARs for be bundles by default.
So, what you are saying is that the entire world should use Maven? I am
not sure we can swing that, but the Maven team would certainly like us
to enforce it...
Heck, even the OSGi Alliance didn't publish their JARs as bundles.
The point is, this is not an "either or" issue...we are doing the maven
plugin too, but there will still be JARs that this will not cover.
-> richard
