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
[EMAIL PROTECTED]
