Ok; just checking; so what is the point of having the maven-eclipse-plugin generate dependencies on subprojects in eclipse ( http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html#useProjectReferences), since it has to get the artifacts from the repository anyway to successfully run 'mvn eclipse:eclipse'?
On 1/4/07, Alan D. Salewski <[EMAIL PROTECTED]> wrote:
On Wed, Jan 03, 2007 at 07:18:17PM -0500, Trevor Torrez spake thus: > Is it the suggested / best practice to have a subproject in a multi project > setup to declare it's dependencies on the other subprojects in the > dependency section? Yes. > This leads to requiring some parts of the multi-project > to be installed to the local repository before other parts can be developed > (using the eclipse:eclipse goal fails if the dependency / subproject is not > installed). [...] That's correct. The reason is that maven-2.x is (by design) repository based; when maven needs a dependency, it looks for it in your local repos (regardless of whether it's another subproject within the project that is building, or something else). That's just how it's supposed to work. -Al -- :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: Alan D. Salewski Software Developer Health Market Science, Inc. :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
