On 30/04/07, Peter Neubauer <[EMAIL PROTECTED]> wrote:
Hi there, over at OPS4J we are using a combination of Maven, BND (great tool Peter!) and setup provided by the PaxConstruct and PaxRunner projects, http://wiki.ops4j.org/confluence/display/ops4j/Pax+Construct.
Just a quick FYI - originally Pax Construct was more about setting up local sandpits to try out OSGi (at least that was the original use case) rather than provide full dev support or a continuous build system. However, after using it at OPS4J, and more recently in tutorials, people have asked for more full-blown development features (improved eclipse support, including round-tripping, 'template' projects for embedding jars and a way to snapshot + share an existing project layout as a template ... say for example a skeleton Pax Wicket project). Anyway, to get back to the subject, I'd be really interested in helping out with the RFP, as I think at the moment the lack of a good build system - and ways to generate a skeleton project/bundle - are what's holding a lot of people back from trying out OSGi*. (* based on feedback after people have tried out Pax Construct)
Maven is not a great tool , especially not in OSGi context, but for now it seems the best. Niclas Hedhman and me have been playing around
The maven repository is great (saves time locating required projects) but it could make better use of metadata and the versioning is fragile. Several times you see people blowing away their local repo, to 'reboot' the maven system. The pain with Maven plugins/pojos is how hard it is to share / extend pojos from another project. Their dependency injection system uses javadoc tags, so you can't really extend a pojo without including the source :(
with RDF meta data for projects, Rules Engines as the primary logic and OSGi as the container for modules called Silk. However, lately Raffael Herzog has been picking up the task and is building a quite exciting tool called Loom, based on HiveMind as container (heavily adapted in order to support dynamic loading, very close to OSGi), Drools and Ivy as a more powerful dependency manager than Maven http://wiki.ops4j.org/confluence/display/ops4j/Loom. By incorporating the BND tool and being able to describe dependencies as packages, not artifacts, Loom is probably well suited to solve most of the problems, but would need some OSGi specific looking into. /peter _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
-- Cheers, Stuart _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
