Peter Kriens <[EMAIL PROTECTED]> writes: > Wow ... I was just nagging BJ Hargrave about exactly this subject when > he told me you had written this mail. This topic is very close to my > heart. The OSGi metadata is so rich that it could make the build > process a lot easier if it could take advantage of it. Unfortunately, > maven's model is much more simplistic and can not take advantage of > this rich model. On the other hand of the spectrum we have Eclipse > which is a fantastic tool, but is not very suited for continuous > builds. > <snip>some great comments</snip>
I was recently pointing out to some developers at ApacheCon that with the OSGi meta-data all one really needs (in theory) to construct build-time and run-time classpaths are Java import statements. I would love to see an environment did all library dependency and path management for me. A couple of other notes: Despite its flaws, I wouldn't count Maven out yet. It has succeeded more than any other effort in standardizing library repositories. >From what I understand there is interest and support for ensuring all libraries that are loaded on the 'official' maven repositories at least include OSGi manifest properties (not that this ensures they're osgi compliant). It would be a start at least. Finally, I've recently been using Rake (ruby's build tool) for Java and Actionscript builds. Some folks from the Apache Incubator ODE project wrote up some rake classes for easier handling of Java builds and access to Maven style repositories: http://buildr.rubyforge.org -- J Aaron Farr jadetower.com [US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
