This content has been marked as final.
Show 2 replies
-
1. Re: Moving framework to reactor
alesj Oct 15, 2009 12:05 PM (in response to thomas.diesler)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) -
2. Re: Moving framework to reactor
thomas.diesler Oct 16, 2009 12:51 AM (in response to 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.