Hi Jörg,
is it possible for you to do a clean and then regenerate the jars for
the dependent JDO projects? This is just to make sure that the jars in
your local maven repository (such as jdo2-enhancer-SNAPSHOT.jar) are
up-to-date. You could run 'maven tck20.clean' from the trunk directory.
This cleans the subprojects api20, core20, enhancer20, and tck20. Then
you could call 'maven tck20.build' which builds the 4 JDO subprojects.
Please note, that a 'maven build' in tck20 takes some time, because it
first compiles, then installs the schema and runs the tck.
Hope this helps.
Regards Michael
Hi,
probably it's just me not seeing the obvious (or my inexperience using
maven), but at the moment I keep on getting compile errors with tck20
that I can't get rid of. I can get it all to compile correctly in
Eclipse, so I guess it's not really a problem in the sourcecode. Eclipse
tells me that the missing AugmentationTest class is in the enhancer20
project, which does build correctly using maven, storing its .jar in the
maven repository (org.apache.jdo/jars/jdo2-enhancer-SNAPSHOT.jar).
$ maven -o
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
You are working offline so the build will continue, but
jdo2-api-SNAPSHOT.jar may be out of date!
You are working offline so the build will continue, but
jpox-SNAPSHOT.jar may be out of date!
You are working offline so the build will continue, but
jpox-enhancer-SNAPSHOT.jar may be out of date!
You are working offline so the build will continue, but
jpox-c3p0-SNAPSHOT.jar may be out of date!
You are working offline so the build will continue, but
jpox-dbcp-SNAPSHOT.jar may be out of date!
build:start:
default:
java:prepare-filesystem:
java:compile:
[echo] Compiling to
/u02/jfrantzius/data/sgw2_workspace/apache_db_jdo/jdo/trunk/tck20/target/classes
[javac] Compiling 616 source files to
/u02/jfrantzius/data/sgw2_workspace/apache_db_jdo/jdo/trunk/tck20/target/classes
/u02/jfrantzius/data/sgw2_workspace/apache_db_jdo/jdo/trunk/tck20/src/java/org/apache/jdo/tck/enhancement/FieldAccessModified.java:23:
package org.apache.jdo.impl.enhancer.util does not exist
import org.apache.jdo.impl.enhancer.util.AnnotationTest;
^
/u02/jfrantzius/data/sgw2_workspace/apache_db_jdo/jdo/trunk/tck20/src/java/org/apache/jdo/tck/enhancement/ImplementsPersistenceCapable.java:23:
package org.apache.jdo.impl.enhancer.util does not exist
import org.apache.jdo.impl.enhancer.util.AugmentationTest;
^
/u02/jfrantzius/data/sgw2_workspace/apache_db_jdo/jdo/trunk/tck20/src/java/org/apache/jdo/tck/enhancement/FieldAccessModified.java:77:
cannot resolve symbol
symbol : class AnnotationTest
location: class org.apache.jdo.tck.enhancement.FieldAccessModified
final AnnotationTest test = new AnnotationTest(out, out);
^
/u02/jfrantzius/data/sgw2_workspace/apache_db_jdo/jdo/trunk/tck20/src/java/org/apache/jdo/tck/enhancement/FieldAccessModified.java:77:
cannot resolve symbol
symbol : class AnnotationTest
location: class org.apache.jdo.tck.enhancement.FieldAccessModified
final AnnotationTest test = new AnnotationTest(out, out);
^
/u02/jfrantzius/data/sgw2_workspace/apache_db_jdo/jdo/trunk/tck20/src/java/org/apache/jdo/tck/enhancement/ImplementsPersistenceCapable.java:70:
cannot resolve symbol
symbol : class AugmentationTest
location: class
org.apache.jdo.tck.enhancement.ImplementsPersistenceCapable
final AugmentationTest test = new AugmentationTest(out, out);
^
/u02/jfrantzius/data/sgw2_workspace/apache_db_jdo/jdo/trunk/tck20/src/java/org/apache/jdo/tck/enhancement/ImplementsPersistenceCapable.java:70:
cannot resolve symbol
symbol : class AugmentationTest
location: class
org.apache.jdo.tck.enhancement.ImplementsPersistenceCapable
final AugmentationTest test = new AugmentationTest(out, out);
^
6 errors
BUILD FAILED
File......
/u02/jfrantzius/.maven/cache/maven-java-plugin-1.5/plugin.jelly
Element... ant:javac
Line...... 63
Column.... 48
Compile failed; see the compiler error output for details.
Total time: 6 seconds
Finished at: Mon Apr 24 14:39:10 CEST 2006
Also I have no clue what the problem is with "plugin.jelly". I let it
regenerate the "plugin cache", but to no avail.
Thanks for any hints,
Jörg
--
Michael Bouschen [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED] http://www.tech.spree.de/
Tel.:++49/30/235 520-33 Buelowstr. 66
Fax.:++49/30/2175 2012 D-10783 Berlin
