can't run maven-cayenne-plugin

[Bryan Lewis <jb...@gmail.com>]

I upgraded the cayenne version from 3.0RC1 to 3.0 in my application's
pom.xml.  All went well except the maven-cayenne-plugin (m2eclipse
auto-executing cgen) throws:

Build errors for model;
org.apache.maven.lifecycle.LifecycleExecutionException:
Failed to execute goal org.apache.cayenne.plugins:maven-cayenne-plugin:3.0:
cgen (cgen) on project model:
Execution cgen of goal
org.apache.cayenne.plugins:maven-cayenne-plugin:3.0:cgen failed:
Unable to load the mojo 'cgen' in the plugin
'org.apache.cayenne.plugins:maven-cayenne-plugin:3.0'.
A required class is missing: org/apache/commons/logging/Log
-----------------------------------------------------
realm =    plugin>org.apache.cayenne.plugins:maven-cayenne-plugin:3.0
strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
urls[0] =
file:/C:/t/m2/org/apache/cayenne/plugins/maven-cayenne-plugin/3.0/maven-cayenne-plugin-3.0.jar
urls[1] =
file:/C:/t/m2/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar
urls[2] =
file:/C:/t/m2/org/apache/maven/maven-plugin-tools-api/2.0.5/maven-plugin-tools-api-2.0.5.jar
urls[3] =
file:/C:/t/m2/org/apache/cayenne/cayenne-server/3.0/cayenne-server-3.0.jar
urls[4] =
file:/C:/t/m2/org/apache/cayenne/cayenne-tools/3.0/cayenne-tools-3.0.jar
urls[5] = file:/C:/t/m2/foundrylogic/vpp/vpp/2.2.1/vpp-2.2.1.jar


This is very odd because it was working fine with 3.0RC1.  And it still does
if I revert the version on only the maven-cayenne-plugin.  (So I have a
work-around.)

I've tried telling m2eclipse to update its dependencies and project
configuration, thinking it was some local config confusion.  I've tried
adding org.apache.commons.logging explicitly to my pom, although it wasn't
needed before.

Re: can't run maven-cayenne-plugin

[Andrus Adamchik <an...@objectstyle.org>]

Today I tried to upgrade my project on Mac to 3.0 final from RC2. So I  
changed Cayenne version in the pom, did a command line build, then  
refreshed from Eclipse. Things seem to be working.

Any other Windows users are seeing this issue?

Not that its of any consolation, but I had random problems with  
m2eclipse calling cgen since like ever. Usually I'd beat m2eclipse  
into submission by clicking various "update this" or "update that"  
Maven menus, and then it works for a couple of months straight.

Andrus


On May 16, 2010, at 11:41 PM, Bryan Lewis wrote:
> I upgraded the cayenne version from 3.0RC1 to 3.0 in my application's
> pom.xml.  All went well except the maven-cayenne-plugin (m2eclipse
> auto-executing cgen) throws:
>
> Build errors for model;
> org.apache.maven.lifecycle.LifecycleExecutionException:
> Failed to execute goal org.apache.cayenne.plugins:maven-cayenne- 
> plugin:3.0:
> cgen (cgen) on project model:
> Execution cgen of goal
> org.apache.cayenne.plugins:maven-cayenne-plugin:3.0:cgen failed:
> Unable to load the mojo 'cgen' in the plugin
> 'org.apache.cayenne.plugins:maven-cayenne-plugin:3.0'.
> A required class is missing: org/apache/commons/logging/Log
> -----------------------------------------------------
> realm =    plugin>org.apache.cayenne.plugins:maven-cayenne-plugin:3.0
> strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> urls[0] =
> file:/C:/t/m2/org/apache/cayenne/plugins/maven-cayenne-plugin/3.0/ 
> maven-cayenne-plugin-3.0.jar
> urls[1] =
> file:/C:/t/m2/org/codehaus/plexus/plexus-utils/1.5.1/plexus- 
> utils-1.5.1.jar
> urls[2] =
> file:/C:/t/m2/org/apache/maven/maven-plugin-tools-api/2.0.5/maven- 
> plugin-tools-api-2.0.5.jar
> urls[3] =
> file:/C:/t/m2/org/apache/cayenne/cayenne-server/3.0/cayenne- 
> server-3.0.jar
> urls[4] =
> file:/C:/t/m2/org/apache/cayenne/cayenne-tools/3.0/cayenne- 
> tools-3.0.jar
> urls[5] = file:/C:/t/m2/foundrylogic/vpp/vpp/2.2.1/vpp-2.2.1.jar
>
>
> This is very odd because it was working fine with 3.0RC1.  And it  
> still does
> if I revert the version on only the maven-cayenne-plugin.  (So I  
> have a
> work-around.)
>
> I've tried telling m2eclipse to update its dependencies and project
> configuration, thinking it was some local config confusion.  I've  
> tried
> adding org.apache.commons.logging explicitly to my pom, although it  
> wasn't
> needed before.