On Thu, Mar 13, 2008 at 2:03 AM, Stefano Lenzi <[EMAIL PROTECTED]> wrote:
> Alin Dreghiciu wrote:
> > (not binding)
> >
> > I'm wondering about two facts related to this artifacts:
> >
> > 1. Are this bundle you are talking about 4.0.0 or 4.0.1 ?
>
> I'm speaking about the one that we release and that are inside the repo,
> honestly I don't know if they are 4.0.0 or 4.0.1 ( Does a differences
> exist between 4.0.0 and 4.0.1?)
I do not know in terms of content but 4.0.0 is Eclipse Public License
Version 1.0 ("EPL") and 4.0.1 is Apache License, Version 2.0.
Also the jar files for version 4.0.0 does not contain OSGi headers.
>
>
> > 2. Please don't mind but why is Felix required to have it's own
> > artifacts for this bundles? Are they different then the ones from OSGi
> > Alliance? If the are not why not someone just upload the osgi alliance
> > ones on maven central repo with a packaging like:
> > <groupId>org.osgi</groupId>
> > <artifactId>org.osgi.core</artifactId>
> > <version>4.1.0</version>
> > I recall discussing this with Peter K and he had nothing against this
> > but he was not familiar enough with Maven to do it by itself.
> > And even if Felix is replacing some parts (maybe FrameworkUtil?) Felix
> > still can use the ones from central repo and replace the parts the
> > need with the Felix specific ones by using bundle plugin.
>
> If there is no licensing issue, AFAIK, It seems feasible to me (I hope
> that OSGi Alliance compile the packages for JDK1.3 :P). BTW, if we
> fallow your way I think that case we should completely remove org.osgi.*
> module from our repo.
I don't think there is a license issue, and I think OSGi artifacts are
compiled an the lowest version possible :)
>
> >
> > Just wondering,
> > Alin
>
>
