cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niclas Hedhman <>
Subject Re: Choreographed releases (was [RANT] This Maven thing is killing us....)
Date Fri, 07 Jul 2006 00:12:27 GMT
On Wednesday 05 July 2006 18:29, Steve Loughran wrote:
> Now that Cocoon is using OSGi, does that change versioning rules?
> Because that lets components run different versions of things
> side-by-side, doesnt it?

To some extent. Individual Java Packages can be versioned and one can declare 
a runtime dependency on a specific, ranged or 'later than' version of a 

But problems will still surface.

A dependsOn B
A dependsOn C ver1.0 (only)
B dependsOn C ver1.1 (or later)

In such case, the classes of C may clash and therefor OSGi will not be able to 
(reliably) resolve A (i.e. 'wire' the classloading) and therefor not attempt 

But in many cases it is possible to have scenarios working, which may not even 
be possible to build from Ant and Maven, hence the Eclipse insistence on 
having their own build system, which resolves OSGi packages according to the 


View raw message