How does the maven-eclipse-pluging know to create .classpath for Eclipse?
I've created a custom packaging type for my integration test module to prevent undesirable activity. So, for now, only the "compile" and "resources" phases are actually doing anything. Now, when I run eclipse:eclipse on the project, I get a .project file and .settings directory, but there is no .classpath. I'd really like for my integration tests to be in the .classpath file since they are Java-based, but I don't know what triggers the maven-eclipse-plugin to generate that file - unless it's the packaging type, in which case I'm basically hosed. If it's just a matter of having another specific lifecycle event added to my packaging type, that's an easy fix.
Thanks, Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
