(This is a repost of a previous mail, with a new, more appropriate subject
For the eclipse part, you should run eclipse:eclipse from the root project to use project dependency instead of binary dependency (ie a module will directly use another module as its dependency instead of using the produced jar).
hmmm OK, I was using the eclipse plugin from http://m2eclipse.codehaus.org, and the dependencies were set that way (binary) by the "Maven2/Update Source Folders" option from the project context menu. I like the plugin as it lets me run mvn from the context menu, it executes a build whenever I modify the pom. So the way to go right now would be to eclipse:eclipse the main module, and then NOT to use the plugins "Maven2/Update Source Folders" option but manually add things to pom, and then eclipse:eclipse again? I found something about a marriage of those two http://jira.codehaus.org/browse/MECLIPSE-78 but I don't know if it's still valid, or maybe there is another way to get those two working together? hmm??? -- Wojtek Biela --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
