Moving framework to reactor

[thomas.diesler]

Folks,

having the framework under its own SVN location

https://svn.jboss.org/repos/jbossas/projects/jboss-osgi/projects/runtime/microcontainer/trunk

does not prove practical at this early phase in project development.

The jboss-osgi examples, the functional tests and the blueprint implementation have been using that framework as the default for a while and I continuously see test failures because of an outdated framework installation.

We already have the notion of "reactor" project that is part of the overall jboss-osgi build. Currently Blueprint is in the reactor already.

I plan to move the framework to the reactor as well. This would remove issues with jboss-osgi test failures because the latest framework SNAPSHOT has not been deployed. It is also impractical to frequently deploy the framework because of the size of its artifacts

[tdiesler@tdvaio trunk]$ ls -l target/
total 9512
-rw-rw-r--. 1 tdiesler tdiesler 4706688 2009-10-09 09:58 jboss-osgi-framework-1.0.0-SNAPSHOT-all.jar
-rw-rw-r--. 1 tdiesler tdiesler 323857 2009-10-09 09:58 jboss-osgi-framework-1.0.0-SNAPSHOT.jar
-rw-rw-r--. 1 tdiesler tdiesler 448742 2009-10-09 09:58 jboss-osgi-framework-1.0.0-SNAPSHOT-javadoc.jar
-rw-rw-r--. 1 tdiesler tdiesler 214299 2009-10-09 09:58 jboss-osgi-framework-1.0.0-SNAPSHOT-sources.jar

After the move you can find the framework here

https://svn.jboss.org/repos/jbossas/projects/jboss-osgi/trunk/reactor/framework

If you work with the framework only and are not concerned with the rest of jboss-osgi, you can use the 'svn switch' command to switch to the new location.

[alesj]

I think you're doing too much of re-factoring. ;-)

(a) package renaming: removed MC naming notion of separation between spi, api, plugins
(b) location: this should be top level jbossas/projects if you ask me

(a) might not be that crucial, as we're not expecting to extend this any futher
e.g. any other MC piece is actually a building block for other things, as it clearly shows here,
hence a strict spi, api, plugins is in order

(b) this is something I would like to debate,
as the current situation is just too tangled up,
no way to know where and how things fit in.

(b) should be the priority and something we should made easily accessible and distributable (short and independent release schedule)

[thomas.diesler]

(b) this is something I would like to debate,
as the current situation is just too tangled up,
no way to know where and how things fit in.

The current situation is that 'framework' is a reactor project of jboss-osgi, which builds as part of the jboss-osgi/trunk

(b) should be the priority and something we should made easily accessible and distributable (short and independent release schedule)

At this stage of development framework has a release cycle of eight weeks, which is the shortest that we do in jboss-osgi. It is also the release cycle of jboss-osgi itself. The next framework release will be on 1-Dec-2009

When framework becomes more stable it can start its own release cycle. The criteria for that is that framework reaches at least Beta (i.e. feature complete) stage.