You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cayenne.apache.org by Ahmed Mohombe <am...@yahoo.com> on 2007/07/30 23:20:53 UTC

MVN again - now on Dataviews :( !

Hi,

trying to build dataviews with Maven(as described in the readme) I'm getting the following error :( :

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Internal error in the plugin manager executing goal 
'org.objectstyle.woproject.maven2:maven-japplicatio
n-plugin:2.0.7:japplication': Unable to find the mojo 
'org.objectstyle.woproject.maven2:maven-japplication-plu
gin:2.0.7:japplication' in the plugin 'org.objectstyle.woproject.maven2:maven-japplication-plugin'
org/apache/tools/ant/BuildException
[INFO] ------------------------------------------------------------------------

Any idea how to fix this?

Thanks in advance,

Ahmed.
P.S. The detailed stacktrace (using mvn -e):
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Internal error in the plugin manager executing goal 
'org.objectstyle.woproject.maven2:maven-japplicatio
n-plugin:2.0.7:japplication': Unable to find the mojo 
'org.objectstyle.woproject.maven2:maven-japplication-plu
gin:2.0.7:japplication' in the plugin 'org.objectstyle.woproject.maven2:maven-japplication-plugin'
org/apache/tools/ant/BuildException
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager 
executing goal 'o
rg.objectstyle.woproject.maven2:maven-japplication-plugin:2.0.7:japplication': Unable to find the 
mojo 'org.ob
jectstyle.woproject.maven2:maven-japplication-plugin:2.0.7:japplication' in the plugin 
'org.objectstyle.woproj
ect.maven2:maven-japplication-plugin'
         at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:543)

         at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecut
or.java:480)
         at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
         at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleEx
ecutor.java:311)
         at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.ja
va:278)
         at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
         at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
         at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mojo 
'org.objectstyle.woproject.
maven2:maven-japplication-plugin:2.0.7:japplication' in the plugin 
'org.objectstyle.woproject.maven2:maven-jap
plication-plugin'
         at 
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:571)
         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:421)
         at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)

         ... 16 more
Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to 
lookup compo
nent 
'org.apache.maven.plugin.Mojoorg.objectstyle.woproject.maven2:maven-japplication-plugin:2.0.7:japplicatio
n', it could not be created
         at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335)
         at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
         at 
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:562)
         ... 18 more
Caused by: org.codehaus.plexus.component.factory.ComponentInstantiationException: Could not 
instanciate compon
ent: role: 'null', implementation: 'org.objectstyle.woproject.maven2.JApplicationMojo'
         at 
org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.
java:77)
         at 
org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.ja
va:62)
         at 
org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464
)
         at 
org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComp
onentManager.java:93)
         at 
org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentMana
ger.java:48)
         at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
         ... 20 more
Caused by: java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildException
         at java.lang.Class.getDeclaredConstructors0(Native Method)
         at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357)
         at java.lang.Class.getConstructor0(Class.java:2671)
         at java.lang.Class.newInstance0(Class.java:321)
         at java.lang.Class.newInstance(Class.java:303)
         at 
org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.ja
va:44)
         ... 24 more
[INFO] ------------------------------------------------------------------------

Re: unsuscribe

Posted by Andrus Adamchik <an...@objectstyle.org>.
I just manually unsubscribed Tobias, but for the future reference -  
users can unsubscribe themselves without bothering the list or the  
admins. Per http://cayenne.apache.org/mailing-lists.html

"To unsubscribe send empty email to user-unsubscribe@cayenne.apache.org"

Cheers,
Andrus




On Jul 31, 2007, at 12:12 PM, Tobias Marx wrote:

>
>
> -----Ursprüngliche Nachricht-----
> Von: Andrus Adamchik [mailto:andrus@objectstyle.org]
> Gesendet: Dienstag, 31. Juli 2007 11:10
> An: user@cayenne.apache.org
> Betreff: Re: MVN again - now on Dataviews :( !
>
> All code dependencies do have explicit versions in the parent pom
> (and maven actually requires version to be present). But Maven
> plugins are considered different beasts and versions are not
> required. If omitted, Maven will fetch the latest version. This
> caused us grief in the past already, so explicitly setting plugin
> versions as well is a good idea.
>
> Andrus
>
>
> On Jul 31, 2007, at 11:59 AM, Ahmed Mohombe wrote:
>
>>> I hardcoded version of japplication plugin to 2.0.5 - this is the
>>> last version that I personally tested. Try it now.
>> Thank you. Now it works :).
>>
>> If the trick of hardcoding versions does it, wouldn't it make more
>> sense to
>> add version for other dependencies as well? I mean generally with
>> mvn, not just for dataviews (in order to prevent future problems -
>> since one can't always test all the latest versions of dependent
>> libs) ?
>>
>> Thanks in advance,
>>
>> Ahmed.
>>
>>
>
>
>
>

unsuscribe

Posted by Tobias Marx <to...@fivecast.com>.

-----Ursprüngliche Nachricht-----
Von: Andrus Adamchik [mailto:andrus@objectstyle.org] 
Gesendet: Dienstag, 31. Juli 2007 11:10
An: user@cayenne.apache.org
Betreff: Re: MVN again - now on Dataviews :( !

All code dependencies do have explicit versions in the parent pom  
(and maven actually requires version to be present). But Maven  
plugins are considered different beasts and versions are not  
required. If omitted, Maven will fetch the latest version. This  
caused us grief in the past already, so explicitly setting plugin  
versions as well is a good idea.

Andrus


On Jul 31, 2007, at 11:59 AM, Ahmed Mohombe wrote:

>> I hardcoded version of japplication plugin to 2.0.5 - this is the  
>> last version that I personally tested. Try it now.
> Thank you. Now it works :).
>
> If the trick of hardcoding versions does it, wouldn't it make more  
> sense to
> add version for other dependencies as well? I mean generally with  
> mvn, not just for dataviews (in order to prevent future problems -  
> since one can't always test all the latest versions of dependent  
> libs) ?
>
> Thanks in advance,
>
> Ahmed.
>
>

Re: MVN again - now on Dataviews :( !

Posted by Andrus Adamchik <an...@objectstyle.org>.
All code dependencies do have explicit versions in the parent pom  
(and maven actually requires version to be present). But Maven  
plugins are considered different beasts and versions are not  
required. If omitted, Maven will fetch the latest version. This  
caused us grief in the past already, so explicitly setting plugin  
versions as well is a good idea.

Andrus


On Jul 31, 2007, at 11:59 AM, Ahmed Mohombe wrote:

>> I hardcoded version of japplication plugin to 2.0.5 - this is the  
>> last version that I personally tested. Try it now.
> Thank you. Now it works :).
>
> If the trick of hardcoding versions does it, wouldn't it make more  
> sense to
> add version for other dependencies as well? I mean generally with  
> mvn, not just for dataviews (in order to prevent future problems -  
> since one can't always test all the latest versions of dependent  
> libs) ?
>
> Thanks in advance,
>
> Ahmed.
>
>

Re: MVN again - now on Dataviews :( !

Posted by Ahmed Mohombe <am...@yahoo.com>.
> I hardcoded version of japplication plugin to 2.0.5 - this is the last 
> version that I personally tested. Try it now.
Thank you. Now it works :).

If the trick of hardcoding versions does it, wouldn't it make more sense to
add version for other dependencies as well? I mean generally with mvn, not just for dataviews (in 
order to prevent future problems - since one can't always test all the latest versions of dependent 
libs) ?

Thanks in advance,

Ahmed.

Re: MVN again - now on Dataviews :( !

Posted by Andrus Adamchik <an...@objectstyle.org>.
I hardcoded version of japplication plugin to 2.0.5 - this is the  
last version that I personally tested. Try it now.

Andrus



On Jul 31, 2007, at 12:20 AM, Ahmed Mohombe wrote:

> Hi,
>
> trying to build dataviews with Maven(as described in the readme)  
> I'm getting the following error :( :
>
> [INFO]  
> ---------------------------------------------------------------------- 
> --
> [ERROR] BUILD ERROR
> [INFO]  
> ---------------------------------------------------------------------- 
> --
> [INFO] Internal error in the plugin manager executing goal  
> 'org.objectstyle.woproject.maven2:maven-japplicatio
> n-plugin:2.0.7:japplication': Unable to find the mojo  
> 'org.objectstyle.woproject.maven2:maven-japplication-plu
> gin:2.0.7:japplication' in the plugin  
> 'org.objectstyle.woproject.maven2:maven-japplication-plugin'
> org/apache/tools/ant/BuildException
> [INFO]  
> ---------------------------------------------------------------------- 
> --
>
> Any idea how to fix this?
>
> Thanks in advance,
>
> Ahmed.
> P.S. The detailed stacktrace (using mvn -e):
> [INFO]  
> ---------------------------------------------------------------------- 
> --
> [ERROR] BUILD ERROR
> [INFO]  
> ---------------------------------------------------------------------- 
> --
> [INFO] Internal error in the plugin manager executing goal  
> 'org.objectstyle.woproject.maven2:maven-japplicatio
> n-plugin:2.0.7:japplication': Unable to find the mojo  
> 'org.objectstyle.woproject.maven2:maven-japplication-plu
> gin:2.0.7:japplication' in the plugin  
> 'org.objectstyle.woproject.maven2:maven-japplication-plugin'
> org/apache/tools/ant/BuildException
> [INFO]  
> ---------------------------------------------------------------------- 
> --
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Internal  
> error in the plugin manager executing goal 'o
> rg.objectstyle.woproject.maven2:maven-japplication-plugin: 
> 2.0.7:japplication': Unable to find the mojo 'org.ob
> jectstyle.woproject.maven2:maven-japplication-plugin: 
> 2.0.7:japplication' in the plugin 'org.objectstyle.woproj
> ect.maven2:maven-japplication-plugin'
>         at  
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals 
> (DefaultLifecycleExecutor.java:543)
>
>         at  
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif 
> ecycle(DefaultLifecycleExecut
> or.java:480)
>         at  
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal 
> (DefaultLifecycleExecutor.java:459)
>         at  
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand 
> leFailures(DefaultLifecycleEx
> ecutor.java:311)
>         at  
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment 
> s(DefaultLifecycleExecutor.ja
> va:278)
>         at  
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute 
> (DefaultLifecycleExecutor.java:143)
>         at org.apache.maven.DefaultMaven.doExecute 
> (DefaultMaven.java:334)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: 
> 125)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.codehaus.classworlds.Launcher.launchEnhanced 
> (Launcher.java:315)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>         at org.codehaus.classworlds.Launcher.mainWithExitCode 
> (Launcher.java:430)
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.PluginManagerException: Unable  
> to find the mojo 'org.objectstyle.woproject.
> maven2:maven-japplication-plugin:2.0.7:japplication' in the plugin  
> 'org.objectstyle.woproject.maven2:maven-jap
> plication-plugin'
>         at  
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo 
> (DefaultPluginManager.java:571)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo 
> (DefaultPluginManager.java:421)
>         at  
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals 
> (DefaultLifecycleExecutor.java:539)
>
>         ... 16 more
> Caused by:  
> org.codehaus.plexus.component.repository.exception.ComponentLookupExce 
> ption: Unable to lookup compo
> nent  
> 'org.apache.maven.plugin.Mojoorg.objectstyle.woproject.maven2:maven- 
> japplication-plugin:2.0.7:japplicatio
> n', it could not be created
>         at org.codehaus.plexus.DefaultPlexusContainer.lookup 
> (DefaultPlexusContainer.java:335)
>         at org.codehaus.plexus.DefaultPlexusContainer.lookup 
> (DefaultPlexusContainer.java:440)
>         at  
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo 
> (DefaultPluginManager.java:562)
>         ... 18 more
> Caused by:  
> org.codehaus.plexus.component.factory.ComponentInstantiationException: 
>  Could not instanciate compon
> ent: role: 'null', implementation:  
> 'org.objectstyle.woproject.maven2.JApplicationMojo'
>         at  
> org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeEx 
> ception(JavaComponentFactory.
> java:77)
>         at  
> org.codehaus.plexus.component.factory.java.JavaComponentFactory.newIns 
> tance(JavaComponentFactory.ja
> va:62)
>         at  
> org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance 
> (DefaultPlexusContainer.java:1464
> )
>         at  
> org.codehaus.plexus.component.manager.AbstractComponentManager.createC 
> omponentInstance(AbstractComp
> onentManager.java:93)
>         at  
> org.codehaus.plexus.component.manager.PerLookupComponentManager.getCom 
> ponent(PerLookupComponentMana
> ger.java:48)
>         at org.codehaus.plexus.DefaultPlexusContainer.lookup 
> (DefaultPlexusContainer.java:331)
>         ... 20 more
> Caused by: java.lang.NoClassDefFoundError: org/apache/tools/ant/ 
> BuildException
>         at java.lang.Class.getDeclaredConstructors0(Native Method)
>         at java.lang.Class.privateGetDeclaredConstructors 
> (Class.java:2357)
>         at java.lang.Class.getConstructor0(Class.java:2671)
>         at java.lang.Class.newInstance0(Class.java:321)
>         at java.lang.Class.newInstance(Class.java:303)
>         at  
> org.codehaus.plexus.component.factory.java.JavaComponentFactory.newIns 
> tance(JavaComponentFactory.ja
> va:44)
>         ... 24 more
> [INFO]  
> ---------------------------------------------------------------------- 
> --
>
>