Bennett, Timothy (JIS - Applications) wrote:
Gang,
As soon as my SVN authentication issues are resolved, I'll be committing
the inital code of the maven2 osgi-plugin in the Felix source repo.
Great! We are moving to M2 in the Cocoon trunk, and currently we have a
rather ad hoc build system for our OSGi bundles. So a M2 OSGi plugin
will be very interesting.
I've noticed that currently the root of the Felix trunk contains
Richard's committment of the oscar2 source. I'm thinking we need some
root-level directories under the Felix trunk to structure our different
*products* and artifacts that we'll be producing.
I would prefer a standard maven (2) multi project layout with one maven
project for each bundle.
So maybe we need a *framework* directory in the root of the Felix trunk,
and the all of Richard's code moved under that directory. WDYT? Maybe a
different directory name? Just something to differentiate it from the
tools type of source I'll be committing.
With one (maven) project per bundle this would currently mean
directories for felix, shell, sheltui and bundlerepository, IIUC.
Eclipse use one directory for each plugin (bundle) and it seem to scale
well.
In fact, I envision we'll need other directories under "tools". One for
the maven-osgi-plugin, and at least one other for the work that Andreas
is doing on the Eclipse plugin for Oscar (I guess renamed now as Felix
Studio).
Yes.
Maybe in the future, we might have non-core, non-framework
services and bundles that we'll decided to version control that will
have their own product directory under the trunk root.
In the future we might want to have separate release cycles for
different bundles, but currently it would complicate things without any
gain. We can restructure with trunk, tags and branches at the bundle
level if/when we actually need it.
/Daniel
