On 05/05/07, J Aaron Farr <[EMAIL PROTECTED]> wrote:
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.
Yep - it would be cool to apply the DRY principle to OSGi projects.
At the moment there are so many different places which I need to
keep in sync with the same info (.classpath, manifests, etc.) The
bnd tool and eclipse plugin help, but things still feel messy.
Hopefully a good RFP will start to bring some of this together.
My number 1 gripe is Eclipse's fixed layout for OSGi projects,
if only it was more flexible about where the manifest was!
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.
Perhaps have a plugin approach to integrate other repository systems?
Then a build system could benefit from Maven and other infrastructure
while improving the dependency system to use OSGi metadata.
There's also a close relationship between building and provisioning - for
example in tutorials I've been asked to provide a simple way to rebuild
and update/install bundles, so people can play with bundle versioning.
( in my tutorial there's an extra step involving the command line... )
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
--
Cheers, Stuart
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
