2009/9/29 Henri Gomez <[email protected]> > I read the Eclipse/PDE integration part of the maven-bundle-plugin > documentation. > > From this reading, the maven plugin will feed PDE with informations to > use the maven project has an eclipse project. > > But what should be done, when we project has been updated via Eclipse > to keep in sync with its maven nature ? >
if you've just been changing the source and no extra imports are required then a simple Maven rebuild would suffice - the problem comes when you add new dependencies using the PDE manifest editor unfortunately we have no way to know about these additions (unless we wrote our own Eclipse plugin) let alone how to map the Eclipse project references into Maven pom dependencies in the past I've added new dependencies to the pom by hand (or with m2e) and then rebuilt with Maven to check everything is consistent, but this is definitely not ideal! BTW, this is a general issue with trying to keep PDE's manifest-first build in sync with other approaches that generate the manifest (ie. Maven/Ant) http://www.manning-sandbox.com/message.jspa?messageID=92010#92010 Should I take a look at Sonatype Tycho for this maven<->eclipse interaction > ? > Tycho supports both pom-first and manifest-first approaches, and attempts to keep both sides in sync - so it's probably worth a look if that's what you need... > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Cheers, Stuart
