|mvn goals fail, unless project compiled from Eclipse [message #566447]
||Tue, 15 July 2008 00:05
Originally posted by: rsabiq.vml.com|
I'm trying to figure out why compile-and-beyond mvn goals fail, unless
project is compiled from Eclipse. All the dependencies in the eclipse
project are managed by Q for Eclipse. Q for Eclipse is probably not the
culprit here, i just don't understand why Eclipse-based compilation
succeeds, while mvn-based compilation fails, even when running goals from
Q for Eclipse.
The first error is:
package org.apache.log4j does not exist
and there is a bunch more for other dependencies.
P.S. mvn goals also fail to download dependencies like log4j and junit jar
(only poms get downloaded). The jars only appear to get downloaded into
repo when Eclipse-based build is performed (again project dependencies are
configured by Q for Eclipse).
P.P.S. Also noticed that when Eclipse-based project build is executed,
target.classes folder is present in target/classes.
P.P.P.S. My file-system mvn version is 2.0.9, whereas Q appears to be
using 2.1, but not sure if this matters because goals fail to compile from
Q as well.
Powered by FUDForum
. Page generated in 0.02635 seconds