...
1.
Most java developers do not have problems hacking together apps in their favourite IDE using simple Java semantics like:
- you have a single big classpath
- there you toss in all your jars and compiled sources
- organize modules lazily in separate java projects (the maven approach) or just in a big project just dividing them with packagenames.
2.
Bob just accepts this behaviour as a status-quo developer view.
However, transforming this to OSGi needs sophisticated know-how or willingness to accept some pain.
Until now, this transformation has affected the way people do the first steps (see 1.)
...
Builder
This turns a Project into concrete artifacts on disk.
Because Project already provides a flattened, consistent view on the project and its resources, a builder just needs to decide what bundles it needs
to create + finally do it.
Builder uses the Tinybundles library (core part) (from Pax Swissbox) to easily create bundles with a minimum of technical code.
TODO:
- currently we have 2 builders that are not of so much practical use: one that tosses all hosted resources into one bundle and create manifest with bnd wrap.
The other is a pretty much automatic split demo which is more a demo than practical in real world.
What we want: something that uses the information described in bob.xml (src/test/resources) --> demo descriptor.
- Maven Plugin as a starter:
Next to the fact that we might launch it standalone, i think it would be good to have a simple maven plugin
(that just invokes bob with information gathered by maven reactor) to kickstart testing the whole idea with a
wider range of projects.
–
by Marcel Offermans via Email:
First of all, I'd say the point is not as much to create a "dumb, simple project setup most java developers know". To me that is kind of a "negative" explanation that does not do justice to what we're trying to achieve.
...