You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by Alan Raison <Al...@luminary.co.uk> on 2009/07/17 15:08:38 UTC
openjpa-persistence build problems?
Hi all
I've been trying to run the OpenJPA unit tests from trunk for ages now,
each time coming up with a different problem! My current problem is
compilation errors in openjpa-persistence. I have tried compiling (mvn
compile, after a mvn clean) with both jdk1.5.0_14 and jdk1.6.0_02 on
windows and I get lots of "cannot find symbol" messages in the
javax.persistence.criteria package, for example
C:\java\workspaces\eclipse\openJPA\trunk\openjpa-persistence\src\main\ja
va\org\a
pache\openjpa\persistence\criteria\NewInstanceSelection.java:[24,34]
cannot find
symbol
symbol : class CompoundSelection
location: package javax.persistence.criteria
I am building this on the command line. Eclipse isn't involved (yet).
Am I doing something wrong?
Thanks
Alan
RE: openjpa-persistence build problems?
Posted by Alan Raison <Al...@luminary.co.uk>.
Donald
Of course. I ran "mvn clean install" and it worked fine - the plain "compile" target must have picked up old build of the other modules.
Thanks
AlanĀ
-----Original Message-----
From: Donald Woods [mailto:dwoods@apache.org]
Sent: 17 July 2009 14:46
To: dev@openjpa.apache.org
Subject: Re: openjpa-persistence build problems?
I just ran a build on my Mac with JDK 1.6.0_13 without any problems.
Have you run "svn status" to make sure you don't have some old files
laying around in your source tree that need to be deleted?
Also, try "mvn clean install" to make sure the builds aren't using any
old artifacts in your local .m2 repo. You might need to remove your
existing .m2/repository/org/apache/openjpa directory and run a "svn up"
so your local source matches the latest nightly artifacts published to
the ASF snapshot repo.
-Donald
Alan Raison wrote:
> Hi all
>
>
>
> I've been trying to run the OpenJPA unit tests from trunk for ages now,
> each time coming up with a different problem! My current problem is
> compilation errors in openjpa-persistence. I have tried compiling (mvn
> compile, after a mvn clean) with both jdk1.5.0_14 and jdk1.6.0_02 on
> windows and I get lots of "cannot find symbol" messages in the
> javax.persistence.criteria package, for example
>
>
>
> C:\java\workspaces\eclipse\openJPA\trunk\openjpa-persistence\src\main\ja
> va\org\a
>
> pache\openjpa\persistence\criteria\NewInstanceSelection.java:[24,34]
> cannot find
>
> symbol
>
> symbol : class CompoundSelection
>
> location: package javax.persistence.criteria
>
>
>
> I am building this on the command line. Eclipse isn't involved (yet).
>
>
>
> Am I doing something wrong?
>
>
>
> Thanks
>
>
>
> Alan
>
>
Re: openjpa-persistence build problems?
Posted by Donald Woods <dw...@apache.org>.
I just ran a build on my Mac with JDK 1.6.0_13 without any problems.
Have you run "svn status" to make sure you don't have some old files
laying around in your source tree that need to be deleted?
Also, try "mvn clean install" to make sure the builds aren't using any
old artifacts in your local .m2 repo. You might need to remove your
existing .m2/repository/org/apache/openjpa directory and run a "svn up"
so your local source matches the latest nightly artifacts published to
the ASF snapshot repo.
-Donald
Alan Raison wrote:
> Hi all
>
>
>
> I've been trying to run the OpenJPA unit tests from trunk for ages now,
> each time coming up with a different problem! My current problem is
> compilation errors in openjpa-persistence. I have tried compiling (mvn
> compile, after a mvn clean) with both jdk1.5.0_14 and jdk1.6.0_02 on
> windows and I get lots of "cannot find symbol" messages in the
> javax.persistence.criteria package, for example
>
>
>
> C:\java\workspaces\eclipse\openJPA\trunk\openjpa-persistence\src\main\ja
> va\org\a
>
> pache\openjpa\persistence\criteria\NewInstanceSelection.java:[24,34]
> cannot find
>
> symbol
>
> symbol : class CompoundSelection
>
> location: package javax.persistence.criteria
>
>
>
> I am building this on the command line. Eclipse isn't involved (yet).
>
>
>
> Am I doing something wrong?
>
>
>
> Thanks
>
>
>
> Alan
>
>