activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Murphree, Michael" <Michael.Murph...@compuware.com>
Subject RE: Build failed, looking for maven-jaxb2-plugin
Date Thu, 16 Nov 2006 15:39:53 GMT
Thank you.  That gets me a bit further along (I am behind a firewall),
but I still run into trouble in that same area.

Now I end up with the result below:

[INFO] Internal error in the plugin manager executing goal
'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.1:generate': Unable to find
the mojo 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.1:generate' in the
plugin 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin'

com/sun/tools/xjc/ErrorReceiver
[INFO]
------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error
in the plugin manager executing goal
'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.1:generate': Unable to find
the mojo 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.1:generate' in the
plugin 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin'
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:538)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:475)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:454)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:306)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:273)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:140)
	at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.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.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.1:generate'
in the plugin 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin'
	at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl
uginManager.java:533)
	at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:390)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:534)
	... 16 more
Caused by:
org.codehaus.plexus.component.repository.exception.ComponentLookupExcept
ion: Unable to lookup component
'org.apache.maven.plugin.Mojoorg.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0
.1:generate', it could not be created
	at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:335)
	at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:312)
	at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:440)
	at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl
uginManager.java:524)
	... 18 more
Caused by:
org.codehaus.plexus.component.factory.ComponentInstantiationException:
Could not instanciate component: role: 'null', implementation:
'org.jvnet.jaxb2.maven2.XJC2Mojo'
	at
org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeExce
ption(JavaComponentFactory.java:77)
	at
org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInsta
nce(JavaComponentFactory.java:62)
	at
org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(Defau
ltPlexusContainer.java:1464)
	at
org.codehaus.plexus.component.manager.AbstractComponentManager.createCom
ponentInstance(AbstractComponentManager.java:93)
	at
org.codehaus.plexus.component.manager.PerLookupComponentManager.getCompo
nent(PerLookupComponentManager.java:48)
	at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:331)
	... 21 more
Caused by: java.lang.NoClassDefFoundError:
com/sun/tools/xjc/ErrorReceiver
	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.newInsta
nce(JavaComponentFactory.java:44)
	... 25 more

I'm not too worried about this at the moment considering that the
snapshot distributions are up and running again.  I'm willing to keep
trying though, if it yields additional information for the group.  Is
there anything else you'd like me to poke into for this issue?  I can
try clearing my Maven repository again.  Is there further reading into
Maven that I should look at before continuing?

Regards,

Michael


-----Original Message-----
From: Mittler, Nathan [mailto:nathan.mittler@sensis.com] 
Sent: Thursday, November 16, 2006 7:35 AM
To: activemq-dev@geronimo.apache.org
Subject: RE: Build failed, looking for maven-jaxb2-plugin

So we have a solution to this ... Thanks to Tim Bish!

It comes down to a proxy issue for https.  We had to set the environment
variables "https.proxyHost" and "https.proxyPort".
The proxy configuration in the maven settings.xml only seems to work for
http, not https.

Once we defined those, it built just fine.

Hope this helps.

Nate

-----Original Message-----
From: Murphree, Michael [mailto:Michael.Murphree@compuware.com] 
Sent: Friday, November 10, 2006 11:53 AM
To: Mittler, Nathan
Cc: activemq-dev@geronimo.apache.org
Subject: RE: Build failed, looking for maven-jaxb2-plugin


Nate,

I've been having the same trouble as you:
https://issues.apache.org/activemq/browse/AMQ-1017. I have far less
experience with Maven, though.  I can get through most of the build but
I get stuck there with the same error.  I'm not sure what I'd actually
need to do to get my local Maven repository configured manually to get
past this, or if that's possible.

Regards,

Michael

-----Original Message-----
From: Mittler, Nathan [mailto:nathan.mittler@sensis.com] 
Sent: Friday, November 10, 2006 8:25 AM
To: activemq-dev@geronimo.apache.org
Subject: Build failed, looking for maven-jaxb2-plugin

A clean build of trunk (with mvn 2.0.4) is failing for me when building
the XMPP module, trying to download the maven-jaxb2-plugin:

https://maven2-repository.dev.java.net/nonav/repository/org/jvnet/jaxb2/
maven2/maven-jaxb2-plugin/0.1/maven-jaxb2-plugin-0.1.pom

The funny thing is that I can view the pom file through a web browser,
so I'm not sure what is giving Maven heartburn.  I've had my Maven proxy
settings set up for a while, so I'm confident that's not it.

A listing of the directory
https://maven2-repository.dev.java.net/nonav/repository/org/jvnet/jaxb2/
maven2/maven-jaxb2-plugin/0.1/ fails - I guess they have directory
listing disabled on the server.

Is anyone else having this problem ... And does anyone know how I can
get past it?

Thanks,
Nate

The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the
named addressee or an authorized designee, you may not copy or use it,
or disclose it to anyone else. If you received it in error please notify
us immediately and then destroy it. 


Mime
View raw message