After a long discussion with Ales, we decided to cut the Beta5 release from a framework
branch that uses compatible dependencies
The location of that branch is as you might guess
This effectively renders the reactor/framework stale with respect to the overall
Perhaps, at this point I should explain again what a "reactor project" is ...
It is the home of fast moving jbosgi projects that want to participate in the overall
jbosgi build and be part of the framework and container independent test matrix. Reactor
projects are part of the installer and are QAed by the Hudson environment on different
frameworks and target containers.
Reactor projects cannot introduce dependencies that are not available in the supported
target containers. Eventually, every reactor project will start its own lifecycle in
jboss-osgi/projects when it becomes stable enough. Every project you see in
jboss-osgi/projects (there are currently a little under 20 of them) has once started in
the reactor and was an integral part of the jbosgi build.
It seems that framework has crossed that bridge of introducing incompatible dependencies
and needs to have a trunk version which is independent of the overall jbosgi build. A
framework/trunk version also seems to be needed to make fast progress.
The situation now is that framework still uses the reactor svn location, but is not part
of the reactor build.
As a consequence, I suggest to move framework to its natural location again (i.e.
projects/runtime/framework/trunk) since its life as reactor project has ended.
View the original post :
Reply to the post :