I started a jdk15 workspace and imported everything. 325 errors.
Closing cayenne-regression-profiler dropped it down to 129. I don't
think this code is currently maintained, is it?
Closing cayenne-tutorial, cayenne-rop-client-tutorial,
cayenne-rop-server-tutorial dropped it to 116. Looks like these are
missing jar files.
The remaining errors all deal with EJBQL, specifically in
cayenne-jdk1.4-unpublished/target/generated-sources in a default
package.
Looks like an svn update is going to deal with this. Trying a root
mvn clean install. Nope, made it worse -- now at 124 errors.
Strangely enough, the "mvn -Dmaven.test.skip=true install" only took 7
minutes this time instead of 17.
On 2/27/07, Mike Kienenberger <mkienen..mail.com> wrote:
> Looks like M2_REPO in Ecilpse also has to be defined. Probably
> something like this, although the exact location will vary. In
> Eclipse 3.1, it's done by going to windows -> preferences -> java ->
> build path -> classpath variables, then clicking New and entering the
> following values:
>
> Name: M2_REPO
> Path: C:/m2/repository
>
> On 2/27/07, Mike Kienenberger <mkienen..mail.com> wrote:
> > Using Eclipse with Mavenized Cayenne - http://cayenne.apache.org/eclipse.html
> >
> > Unfortunately this page needs some details.
> >
> > ==========================
> > # Get code from Subversion and build it from command line to seed the
> > local repository.
> > # Create two workspaces - one for JDK 1.4 and one for 1.5 code.
> > ==========================
> >
> > I'm guessing from my MyFaces maven experience that the checkout
> > directory must be external to the workspaces created. There should
> > probably be more explicit instructions on how to import the projects,
> > and I suspect that "mvn eclipse:eclipse" has to be executed
> > beforehand. You might be able to crib notes from
> > http://wiki.apache.org/myfaces/Eclipse_IDE (The first paragraph now
> > seems out of place with the original document, so you'll want to sort
> > through it).
> >
> > ==========================
> > # Most Maven modules that contain source code include Eclipse project
> > files, so they can be imported in a corresponding workspace, depending
> > on the required JDK compliance level. You don't have to import all
> > modules, only those that you are planning to work on, as the projects
> > do not have Eclipse-level dependencies on each other (dependencies are
> > resolved via Maven).
> > ==========================
> >
> > It's also unclear which modules should be imported into which workspace.
> >
>
This archive was generated by hypermail 2.0.0 : Wed Feb 28 2007 - 00:07:59 EST