You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall" <he...@ungoverned.org> on 2007/10/02 20:52:07 UTC
Felix Commons
I had a thought that I wanted to run by people...
Since there is some consternation about what to do with Felix Commons
(i.e., whether or not to release bundles or just release POM files),
what about the possibility of just releasing POM files, but releasing
the actual JAR files independently of Apache?
For example, with the new OBR plugin we could easily create an OBR repo
that someone could place at a third-party site, e.g., the original OBR
Source Forge site.
I am not sure if this would be muddying the waters or not, but the
effort to do this would clearly have to be outside of the Apache mandate
(i.e., an independent effort). For example, if we did decide to release
POMs, then nothing could stop a third party from creating real bundles
and making them available on a web site, right? So, this could work in a
similar fashion.
The rationale for doing something like this is that it seems like we as
a community do not have man power or perhaps will power (for good
reason) to be responsible for maintaining a large bundle repository.
Of course, if the mere act of releasing a POM encompasses as much need
for oversight as a bundle JAR file, then this approach wouldn't save us
much either.
Any thoughts from people with more knowledge than myself on such topics?
-> richard
Re: Felix Commons
Posted by Carsten Ziegeler <cz...@apache.org>.
Richard S. Hall wrote:
> I had a thought that I wanted to run by people...
>
> Since there is some consternation about what to do with Felix Commons
> (i.e., whether or not to release bundles or just release POM files),
> what about the possibility of just releasing POM files, but releasing
> the actual JAR files independently of Apache?
>
> For example, with the new OBR plugin we could easily create an OBR repo
> that someone could place at a third-party site, e.g., the original OBR
> Source Forge site.
>
> I am not sure if this would be muddying the waters or not, but the
> effort to do this would clearly have to be outside of the Apache mandate
> (i.e., an independent effort). For example, if we did decide to release
> POMs, then nothing could stop a third party from creating real bundles
> and making them available on a web site, right? So, this could work in a
> similar fashion.
>
> The rationale for doing something like this is that it seems like we as
> a community do not have man power or perhaps will power (for good
> reason) to be responsible for maintaining a large bundle repository.
>
> Of course, if the mere act of releasing a POM encompasses as much need
> for oversight as a bundle JAR file, then this approach wouldn't save us
> much either.
>
> Any thoughts from people with more knowledge than myself on such topics?
I have not more knowledge :) but as everyone probably knows I was
interested in commons releases some time ago, but did not proceed as
there were imho too many different opinions.
Anyway, I think we should try to persuade other projects to make their
libs OSGi aware by adding the required meta data (for example all
commons projects at Apache). We've discussed this briefly some time ago.
Your suggestion could be a good addition as well, so I'm not sure about
the legal consequences, but I guess that if we go the way you propose we
don't have to care about the legal issues (but that's just a guess).
I think we can just go one step further and make everything simpler. Why
do we need to release the poms at all? The poms stored in svn have two
problems to be used:
a) they are snapshots - we could make them final and increase with every
change the last part of the version number.
b) we need multiple versions of a wrapper library. So we should change
the directory structure, like
commons
+ servlet-api
+ 2.3 - pom.xml
+ 2.4 - pom.xml
We never release and if people want to create wrappers they can just
check out commons and do a mvn deploy into their local repository.
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: Felix Commons
Posted by Ralph Goers <Ra...@dslextreme.com>.
Pardon me for butting in and I might be way of base, but perhaps the
problem could be solved in a different way? If I understand correctly,
the issue with bundles is that they might contain 3rd party jars with
licenses that are incompatible with Apache? If so, could they be
packaged at apache without the 3rd party jars but then be installed into
a user's local repository using a Maven plugin that repackages them to
include the jars?
Ralph
Rob Walker wrote:
> To me - the difficult issue is the one Richard nails "maintaining a
> large bundle repository"
>
> The problem is, I'd say, some bundles have a very common utility and
> wide use e.g. log, http etc. For those we'll likely get helpers to
> look after them, as is the case now. But many bundles are components
> that are key to only some applications - so the pool of people to
> maintain them will be smaller i.e. those with an interest and
> knowledge in that application space. Even with Http we find this a
> little - there's a few of us who try and look after it because we use
> it in specific parts of our applications, but we're not always the
> best people to know all about Http serving even if we had the time to
> devote.
>
> Seems to me - we need to make it as easy, worthwhile and encouraging
> as possible for anyone to be a bundle maintainer - either long term,
> or even for a short period whilst it fits naturally with their job or
> application needs.
>
> OBR seems like a decent way to start in that - something that's
> accessible, easy for people to contribute too, and doesn't have too
> much red tape.
>
> Just my 10c
>
> -- Rob
>
> Richard S. Hall wrote:
>> I had a thought that I wanted to run by people...
>>
>> Since there is some consternation about what to do with Felix Commons
>> (i.e., whether or not to release bundles or just release POM files),
>> what about the possibility of just releasing POM files, but releasing
>> the actual JAR files independently of Apache?
>>
>> For example, with the new OBR plugin we could easily create an OBR
>> repo that someone could place at a third-party site, e.g., the
>> original OBR Source Forge site.
>>
>> I am not sure if this would be muddying the waters or not, but the
>> effort to do this would clearly have to be outside of the Apache
>> mandate (i.e., an independent effort). For example, if we did decide
>> to release POMs, then nothing could stop a third party from creating
>> real bundles and making them available on a web site, right? So, this
>> could work in a similar fashion.
>>
>> The rationale for doing something like this is that it seems like we
>> as a community do not have man power or perhaps will power (for good
>> reason) to be responsible for maintaining a large bundle repository.
>>
>> Of course, if the mere act of releasing a POM encompasses as much
>> need for oversight as a bundle JAR file, then this approach wouldn't
>> save us much either.
>>
>> Any thoughts from people with more knowledge than myself on such topics?
>>
>> -> richard
>>
>
Re: Felix Commons
Posted by Rob Walker <ro...@ascert.com>.
To me - the difficult issue is the one Richard nails "maintaining a
large bundle repository"
The problem is, I'd say, some bundles have a very common utility and
wide use e.g. log, http etc. For those we'll likely get helpers to look
after them, as is the case now. But many bundles are components that are
key to only some applications - so the pool of people to maintain them
will be smaller i.e. those with an interest and knowledge in that
application space. Even with Http we find this a little - there's a few
of us who try and look after it because we use it in specific parts of
our applications, but we're not always the best people to know all about
Http serving even if we had the time to devote.
Seems to me - we need to make it as easy, worthwhile and encouraging as
possible for anyone to be a bundle maintainer - either long term, or
even for a short period whilst it fits naturally with their job or
application needs.
OBR seems like a decent way to start in that - something that's
accessible, easy for people to contribute too, and doesn't have too much
red tape.
Just my 10c
-- Rob
Richard S. Hall wrote:
> I had a thought that I wanted to run by people...
>
> Since there is some consternation about what to do with Felix Commons
> (i.e., whether or not to release bundles or just release POM files),
> what about the possibility of just releasing POM files, but releasing
> the actual JAR files independently of Apache?
>
> For example, with the new OBR plugin we could easily create an OBR
> repo that someone could place at a third-party site, e.g., the
> original OBR Source Forge site.
>
> I am not sure if this would be muddying the waters or not, but the
> effort to do this would clearly have to be outside of the Apache
> mandate (i.e., an independent effort). For example, if we did decide
> to release POMs, then nothing could stop a third party from creating
> real bundles and making them available on a web site, right? So, this
> could work in a similar fashion.
>
> The rationale for doing something like this is that it seems like we
> as a community do not have man power or perhaps will power (for good
> reason) to be responsible for maintaining a large bundle repository.
>
> Of course, if the mere act of releasing a POM encompasses as much need
> for oversight as a bundle JAR file, then this approach wouldn't save
> us much either.
>
> Any thoughts from people with more knowledge than myself on such topics?
>
> -> richard
>
--
Ascert - Taking systems to the Edge
robw@ascert.com
+44 (0)20 7488 3470
www.ascert.com