Michael McCallum-3 wrote: > >> maybe you want to look into this: http://code.google.com/p/mvnlink/ >> it sounds like it does what you're looking for. > use the m2eclipse.codehaus.org plugin and then run mvn eclipse:m2eclipse >
If you are using m2eclipse, I wouldn't recommend using eclipse:m2eclipse. Instead use one of the project import wizards provided by m2eclipse. They allow to import multiple projects from local system, checkout from SCM or import by Maven coordinates. See http://tinyurl.com/5qzyzx This way project interdependencies and configuration for other Eclipse tools, such as AJDT or WTP will be done automatically. See for example WTP howto. http://tinyurl.com/5zoawl Michael McCallum-3 wrote: > > far better solution... there is one caveat make sure that maven and > eclipse > have different output folders... eclipse generates class are not meant to > be > packaged up... > Because of several issues with option for using separate output folders between Eclipse and Maven CLI, we had to remove it in m2eclipse 0.9.5. If you are not jumping back and forth between Eclipse and command line it works much better for the IDE and the only caveat is that you need to not forget to perform Refresh and Project / Clean after you done something with the project outside IDE. We are still looking at better solution for this issue. In a mean time, if you prefer to use separate output folders, you can do that with a custom profile. See more details at http://tinyurl.com/373bkh#ProjectFAQ-outputFolders regards, Eugene -- View this message in context: http://www.nabble.com/Release-fails-during-SVN-commit-tp19084270p19108305.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
