Doesn't look related...

Which version of Maven do you have? I recommend 2.0.9:

$ mvn -v
Maven version: 2.0.9
Java version: 1.5.0_16
OS name: "mac os x" version: "10.5.5" arch: "i386" Family: "unix"

Andrus


On Sep 30, 2008, at 5:04 PM, Michael Gentry wrote:

I don't know if this is related to the changes.  I did an svn update,
mvn clean, mvn install (OS X 10.4.11/Java 1.5) and got this error:

[INFO] Compiling 1 source file to
/Users/mgentry/Projects/Eclipse/Cayenne30/framework/maven-cayenne- plugin/target/classes [INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

/Users/mgentry/Projects/Eclipse/Cayenne30/framework/maven-cayenne- plugin/src/main/java/org/apache/cayenne/tools/ CayenneGeneratorMojo.java:[233,43]
Object() in java.lang.Object cannot be applied to
(org.apache.commons.logging.Log,java.lang.String,java.lang.String)

/Users/mgentry/Projects/Eclipse/Cayenne30/framework/maven-cayenne- plugin/src/main/java/org/apache/cayenne/tools/ CayenneGeneratorMojo.java:[242,33]
cannot find symbol
symbol  : method setLogger(org.apache.commons.logging.Log)
location: class org.apache.cayenne.gen.ClassGenerationAction



I last updated/built successfully sometime last week.

/dev/mrg


On Tue, Sep 30, 2008 at 8:50 AM, Andrus Adamchik <[EMAIL PROTECTED] > wrote:
I just committed maven changes needed to compile Cayenne with either Java 5 or 6. I would strongly recommend to everybody to do a full rebuild from root
of the checkout tree after an update. A few other points:

* We have a new empty module cayenne-jdk1.6-unpublished. As the name
suggests, it is for the code that will only run under Java 1.6
* You can build from root of the checkout with either Java 5 or 6. In the former case, Maven will exclude "cayenne-jdk1.6-unpublished" from the build and from resulting aggregated jars. Corollary to that - release managers
MUST USE JAVA 6 TO CREATE  RELEASE ARTIFACTS.
* It is up to the developers how to organize the modules in Eclipse. I am back to the two workspaces setup - one with default Java 5 JVM and another -
with Java 6.

Let me know if anything that I checked in breaks your local build.

Thanks,
Andrus



Reply via email to