At a simple level we have 2 projects, A and B, where B depends on A. Currently we have an eclipse project for each, and a project dependency set up in eclipse. Then for our automated build we have a script that parses the eclipse project files, generates Ant build.xml files and goes from there.*
From what I've seen so far Maven flips this model on it's head, so we'dgenerate the eclipse project files from the Maven project.xml.
Now I've managed to set up 2 Maven projects so that B depends on the jar generated by A, but this doesn't translate very well into the Eclipse projects. This is mainly because the reference in Eclipse for project A is to the jar built by Maven, not the actual eclipse project A. So if in Eclipse I make a change in project A that affects some code in project B I end up with the red-underlining errors, and no amount of "Rebuild All" in Eclipse sorts it - I have to go and do the Maven build.
This isn't exactly ideal - it does mean that the usage of Eclipse is less intuitive than it used to be - I've got to sell this change to a team of developers who'll definitely moan about this!
Can anybody think of a way to set this up? Or would it require an enhancement to be made to the eclipse plugin to generate the reference in the .classpath as a project ref rather than a jar?
thanks in advance
James
* for those of you wondering why we do this, the script basically does things like parsing the ant results to build up a set of web pages / mail the dev team if there are errors etc. All these things seem to be things that Maven plugins can do for us, so it seems sensible to move to a standard product, rather than a custom perl script
_________________________________________________________________
Use MSN Messenger to send music and pics to your friends http://www.msn.co.uk/messenger
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
