Le 25 août 08 à 12:44, Rob Walker a écrit :

I always feel like I'm a bit old-school and not keeping up with newer trends because I stick with Ant by preference ... glad to see I'm not alone!
-  Rob

Craig Phillips wrote:
Hi,
One problem I see, almost exclusively or certainly prevalent in the eclipse/equinox world, when I read things like this (beside not being a fan of maven, to put it mildly) is the continual emphasis on / usage of "Require-Bundle"; "Require-Bundle" can really be a nuisance, especially for those of us that want to separate interface from implementation (conceptually, not just syntactically); Just an observation, but I run into this "nuisance" frequently and it's a pain to undo...
Craig Phillips, Praxis
PS - I still prefer to run BND from ANT vice some mysterious hard wired maven-phase based slight-of-hand... there's no replacement for simplicity and explicitness

I am then interested to know how you manage the classpath of your project. Because there is a little gap between the bnd/MANIFEST.MF that only declare a dependency on some packages, and the actually jars your are building against. So do you manage your jars dependencies manually ? with an old-school lib folder ? Or you have a dependency manager setup ? Ivy or maven just to retrieve the jars ? I thought of a third solution, but I didn't found any such tool: use an OBR to compute the dependencies and retrieve the jars. I used the Felix OBR resolver implementation and I managed to do a similar plugin to IvyDE [1] (just a proof of concept here, implemented with lot of hacks). But I am not sure if the "obr service" can be used for that kind of classpath computing, as its main goal, as far as I understand, is to get bundle into a OSGi runtime environment. There is that "compile" vs "runtime" classpath issue. But not sure if that is an issue... WDYT ?

Nicolas

[1] http://ant.apache.org/ivy/ivyde/





________________________________

From: Richard S. Hall [mailto:[EMAIL PROTECTED]
Sent: Fri 8/22/2008 9:15 PM
To: dev@felix.apache.org
Subject: Maven & OSGi plans



I am not sure if this will be beneficial to us or not, since it sounds like a) they plan on duplicating or effort around the Bundle Plugin and b) they are getting really cozy with Eclipse, but it is an interesting
read nonetheless:

   http://blogs.sonatype.com/jvanzyl/2008/08/21/1219331495607.html

-> richard




--


Ascert - Taking systems to the Edge
[EMAIL PROTECTED]
+44 (0)20 7488 3470
www.ascert.com


Reply via email to