Hi,

If this setup, looking very easy actually, does it all, we should just
give it a try adding it to the Felix parent pom and test it with the
following projects (yes, the list is somewhat biased :-) ):

  * Felix parent pom
  * OSGi Compendium library bundle
  * OSGi Foundation library bundle
  * Metatype Service (metatype)
  * Configuration Admin Service (configadmin)
  * Declarative Services (scr)

If the framework would be ready for release, we might also include this.

Regards
Felix


Am Montag, den 10.12.2007, 19:29 +0100 schrieb Carsten Ziegeler:
> Richard S. Hall wrote:
> > I think releases of all of these are pending...we just have to decide
> > how to do it...I was waiting for a description of the "maven way" for
> > doing releases for our bundle subprojects...but I suppose we could just
> > hurry up and do manual releases if we must.
> > 
> Yeah, I got the message :)
> 
> Due to lack of time just a short description (sorry)
> 
> Releasing the sub projects independently with maven is simple. We need
> to define some extra configuration like how the released artifacts
> should look like, then of course the signing stuff etc.
> 
> I did this already for the commons project. You'll find a configured pom
> under commons/parent/pom.xml. I think we should add most of this to our
> root parent pom, so this gets inherited.
> 
> And then a sub project can be released with "mvn release:prepare" and
> "mvn release:perform" - that's it.
> 
> Of course there are many caveats and things that can go wrong; so we
> should just try it and fix the problems on the way. One additional thing
> is that a release can only depend on released stuff. So in most cases
> this means, releasing parent pom first, releasing all dependencies and
> then the sub project. Therefore it's easier to not rely on snapshots
> between sub projects. This makes independent releases much easier. As
> soon as there is a need for updating a dependency, it should be done.
> But not automatically.
> 
> Hope this helps as a simple quickstart. I think we should just come up
> with a list of projects we want to release and then we can see how we
> get them out.
> 
> Carsten

Reply via email to