Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » IAM (Eclipse Integration for Apache Maven) » Problem using maven-jibx-plugin
Problem using maven-jibx-plugin [message #498815] Wed, 18 November 2009 17:28 Go to next message
Brice is currently offline Brice
Messages: 4
Registered: November 2009
Junior Member
Hello, I have problem executing a compile with the maven-jibx-plugin


The build section contains this declaration :

<plugin>
	<groupId>org.jibx</groupId>
	<artifactId>maven-jibx-plugin</artifactId>
	<version>1.1.5</version>
	<executions>
		<execution>
			<phase>compile</phase>
			<goals>
				<goal>bind</goal>
			</goals>
		</execution>
	</executions>
	<configuration>
		<includes>
			<include>binding*.xml</include>
		</includes>
		<verbose>true</verbose>
	</configuration>
</plugin>


The event log isn't really helpfull, setting the filter at "debug" isn't either, i just end up with these events !

18:05:22 CET	Starting	Starting phaseExecution process-resources
18:05:22 CET	Starting	Starting mojoExecution resources:resources
18:05:22 CET	info	Using default encoding to copy filtered resources. 
18:05:22 CET	Finished	Finished mojoExecution resources:resources
18:05:22 CET	Finished	Finished phaseExecution process-resources
18:05:22 CET	Starting	Starting phaseExecution compile
18:05:23 CET	Starting	Starting mojoExecution compiler:compile
18:05:23 CET	info	Nothing to compile - all classes are up to date 
18:05:23 CET	Finished	Finished mojoExecution compiler:compile
18:05:23 CET	Finished	Finished phaseExecution compile
18:05:23 CET	Starting	Starting phaseExecution process-classes
18:05:24 CET	Starting	Starting mojoExecution jibx:bind
18:05:24 CET	info	Running JiBX binding compiler (single-module mode) on 2 binding file(s) 
18:05:25 CET	Error	An error occurred in phase mojoExecution with the exception org.apache.maven.plugin.MojoExecutionException: Binding binding-menu.xml is unusable because of validation errors
18:05:25 CET	Error	An error occurred in phase projectExecution with the exception org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.jibx:maven-jibx-plugin:1.1.5:bind': Mojo execution failed.
18:05:25 CET	Error	An error occurred in phase mavenExecution with the exception org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.jibx:maven-jibx-plugin:1.1.5:bind': Mojo execution failed.
18:05:25 CET	Error	An error occurred in phase reactorExecution with the exception org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.jibx:maven-jibx-plugin:1.1.5:bind': Mojo execution failed.



Doing a mvn clean package in the commadn line (Maven 2.0.10) is just working. I also tried to set the phase to process-classes, without success.

After some time I read on this JiBx usergroup ( http://old.nabble.com/Binding-binding.xml-is-unusable-becaus e-of-validation-errors-td14892163.html) the error "Binding binding-menu.xml is unusable because of validation errors" might be due to the path Jibx is looking for the classes.

Maybe the plugin cannot found the classes as they might not yet be generated by the eclipse compiler.

Is IAM taking care of the maven phases inside Eclipse?


Thx in advance for any help

----
For eventual readers, i found a workaround :
1. I set the maven-plugin-phase to process-classes
2. Eclipse does the compiling job (with the debug info)
3. In the command line, I execute "mvn process-classes" (Doing so in Eclipse with Execute Goal raises the above mentioned error)
4. In Eclipse it's now possible to run the application in debug mode!

It's far from perfect but it is working. Don't yet know if it's going to be accepted by the staff.
Re: Problem using maven-jibx-plugin [message #498887 is a reply to message #498815] Thu, 19 November 2009 00:31 Go to previous messageGo to next message
Carlos Sanchez is currently offline Carlos Sanchez
Messages: 114
Registered: July 2009
Senior Member
can you try with the command line version of maven from
http://q4e.googlecode.com/files/apache-maven-2.1-659802-Q4E- bin.zip

we use a different Maven version than the 2.0.10 you use in the command
line and we need to find out whether the problem is in the IAM Eclipse
plugin code or in the version of Maven we use.

for a detailed explanation, please see
http://code.google.com/p/q4e/wiki/ReportingBugs

thanks

On 11/18/09 9:28 AM, brice.dutheil+eclipse@gmail.com wrote:
> Hello, I have problem executing a compile with the maven-jibx-plugin
>
>
> The build section contains this declaration :
>
> <plugin>
> <groupId>org.jibx</groupId>
> <artifactId>maven-jibx-plugin</artifactId>
> <version>1.1.5</version>
> <executions>
> <execution>
> <phase>compile</phase>
> <goals>
> <goal>bind</goal>
> </goals>
> </execution>
> </executions>
> <configuration>
> <includes>
> <include>binding*.xml</include>
> </includes>
> <verbose>true</verbose>
> </configuration>
> </plugin>
>
> The event log isn't really helpfull, setting the filter at "debug" isn't
> either, i just end up with these events !
>
> 18:05:22 CET Starting Starting phaseExecution process-resources
> 18:05:22 CET Starting Starting mojoExecution resources:resources
> 18:05:22 CET info Using default encoding to copy filtered resources.
> 18:05:22 CET Finished Finished mojoExecution resources:resources
> 18:05:22 CET Finished Finished phaseExecution process-resources
> 18:05:22 CET Starting Starting phaseExecution compile
> 18:05:23 CET Starting Starting mojoExecution compiler:compile
> 18:05:23 CET info Nothing to compile - all classes are up to date
> 18:05:23 CET Finished Finished mojoExecution compiler:compile
> 18:05:23 CET Finished Finished phaseExecution compile
> 18:05:23 CET Starting Starting phaseExecution process-classes
> 18:05:24 CET Starting Starting mojoExecution jibx:bind
> 18:05:24 CET info Running JiBX binding compiler (single-module mode) on
> 2 binding file(s) 18:05:25 CET Error An error occurred in phase
> mojoExecution with the exception
> org.apache.maven.plugin.MojoExecutionException: Binding binding-menu.xml
> is unusable because of validation errors
> 18:05:25 CET Error An error occurred in phase projectExecution with the
> exception org.apache.maven.lifecycle.LifecycleExecutionException:
> Internal error in the plugin manager executing goal
> 'org.jibx:maven-jibx-plugin:1.1.5:bind': Mojo execution failed.
> 18:05:25 CET Error An error occurred in phase mavenExecution with the
> exception org.apache.maven.lifecycle.LifecycleExecutionException:
> Internal error in the plugin manager executing goal
> 'org.jibx:maven-jibx-plugin:1.1.5:bind': Mojo execution failed.
> 18:05:25 CET Error An error occurred in phase reactorExecution with the
> exception org.apache.maven.lifecycle.LifecycleExecutionException:
> Internal error in the plugin manager executing goal
> 'org.jibx:maven-jibx-plugin:1.1.5:bind': Mojo execution failed.
>
>
> Doing a mvn clean package in the commadn line (Maven 2.0.10) is just
> working. I also tried to set the phase to process-classes, without success.
>
> After some time I read on this JiBx usergroup
> ( http://old.nabble.com/Binding-binding.xml-is-unusable-becaus e-of-validation-errors-td14892163.html)
> the error "Binding binding-menu.xml is unusable because of validation
> errors" might be due to the path Jibx is looking for the classes.
>
> Maybe the plugin cannot found the classes as they might not yet be
> generated by the eclipse compiler.
>
> Is IAM taking care of the maven phases inside Eclipse?
>
>
> Thx in advance for any help
>
> ----
> For eventual readers, i found a workaround : 1. I set the
> maven-plugin-phase to process-classes
> 2. Eclipse does the compiling job (with the debug info)
> 3. In the command line, I execute "mvn process-classes" (Doing so in
> Eclipse with Execute Goal raises the above mentioned error)
> 4. In Eclipse it's now possible to run the application in debug mode!
>
> It's far from perfect but it is working. Don't yet know if it's going to
> be accepted by the staff.
Re: Problem using maven-jibx-plugin [message #498969 is a reply to message #498887] Thu, 19 November 2009 11:41 Go to previous messageGo to next message
Brice is currently offline Brice
Messages: 4
Registered: November 2009
Junior Member
Actually I have problems running this command line version :

C:\devhome\working_directory\10.0\ProjectAdmin-Build\ProjectAdmin>set M2_HOME=c:\devhome\app\apache-maven-2.1-SNAPSHOT

C:\devhome\working_directory\10.0\ProjectAdmin-Build\ProjectAdmin>set PATH=c:\devhome\app\apache-maven-2.1-SNAPSHOT\bin;%P
ATH%

C:\devhome\working_directory\10.0_BP\ProjectAdmin-Build\ProjectAdmin>mvn clean process-classes
[INFO] Scanning for projects...
[INFO] Attempting to resolve a version for plugin: org.codehaus.mojo:cobertura-maven-plugin using meta-version: LATEST
[INFO] Using version: 2.3 of plugin: org.codehaus.mojo:cobertura-maven-plugin
[INFO] ------------------------------------------------------------------------
[INFO] Building ProjectAdmin
[INFO]
[INFO] Id: com.vsct.wdi:ProjectAdmin:war:10.0-SNAPSHOT
[INFO] task-segment: [clean, process-classes]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting file set: C:\devhome\working_directory\10.0\ProjectAdmin-Build\ProjectAdmin\src\main\webapp\WEB-INF\classes (included: [**], excluded: [])
[INFO] [clean:clean]
[INFO] [cobertura:clean]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
---------------------------------------------------
constituent[0]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/aspectjrt-1.5.3.jar
constituent[1]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/commons-cli-1.0.jar
constituent[2]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/commons-logging-api-1.1.jar
constituent[3]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/doxia-sink-api-1.0-alpha-9.jar
constituent[4]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/jsch-0.1.27.jar
constituent[5]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/jtidy-4aug2000r7-dev.jar
constituent[6]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/log4j-1.2.12.jar
constituent[7]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-artifact-3.0-alpha-1.jar
constituent[8]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-core-2.1-SNAPSHOT.jar
constituent[9]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-embedder-2.1-SNAPSHOT.jar
constituent[10]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-lifecycle-2.1-SNAPSHOT.jar
constituent[11]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-model-2.1-SNAPSHOT.jar
constituent[12]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-plugin-api-2.1-SNAPSHOT.jar
constituent[13]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-profile-2.1-SNAPSHOT.jar
constituent[14]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-project-2.1-SNAPSHOT.jar
constituent[15]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-reporting-api-2.1-SNAPSHOT.jar
constituent[16]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-toolchain-2.1-SNAPSHOT.jar
constituent[17]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-workspace-2.1-SNAPSHOT.jar
constituent[18]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/plexus-container-default-1.0-alpha-47.jar
constituent[19]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/plexus-interactivity-api-1.0-alpha-6.jar
constituent[20]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/plexus-interpolation-1.0.jar
constituent[21]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/plexus-utils-1.5.1.jar
constituent[22]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/wagon-file-1.0-beta-2.jar
constituent[23]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/wagon-http-lightweight-1.0-beta-2.jar
constituent[24]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/wagon-http-shared-1.0-beta-2.jar
constituent[25]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/wagon-provider-api-1.0-beta-2.jar
constituent[26]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-1.0-beta-2.jar
constituent[27]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-common-1.0-beta-2.jar
constituent[28]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-external-1.0-beta-2.jar
constituent[29]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/xbean-reflect-3.4.jar
---------------------------------------------------
java.lang.NullPointerException
        at org.apache.maven.project.artifact.MavenMetadataSource$ProjectRelocation.access$0(MavenMetadataSource.java:573)
        at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedArtifact(MavenMetadataSource.java:105)
        at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:513)
        at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:554)
        at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:554)
        at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:554)
        at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:554)
        at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:554)
        at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:132)
        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:347)
        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:321)
        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:289)
        at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1455)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:522)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
        at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
        at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
        at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
        at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
        at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod)
        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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:31)


However for information I also tried maven 2.2.1, and it is working fine.
Re: Problem using maven-jibx-plugin [message #571377 is a reply to message #498887] Thu, 19 November 2009 11:41 Go to previous message
Brice is currently offline Brice
Messages: 4
Registered: November 2009
Junior Member
Actually I have problems running this command line version :

C:\devhome\working_directory\10.0\ProjectAdmin-Build\Project Admin >set M2_HOME=c:\devhome\app\apache-maven-2.1-SNAPSHOT

C:\devhome\working_directory\10.0\ProjectAdmin-Build\Project Admin >set PATH=c:\devhome\app\apache-maven-2.1-SNAPSHOT\bin;%P
ATH%

C:\devhome\working_directory\10.0_BP\ProjectAdmin-Build\Proj ectAdmin >mvn clean process-classes
[INFO] Scanning for projects...
[INFO] Attempting to resolve a version for plugin: org.codehaus.mojo:cobertura-maven-plugin using meta-version: LATEST
[INFO] Using version: 2.3 of plugin: org.codehaus.mojo:cobertura-maven-plugin
[INFO] ------------------------------------------------------------ ------------
[INFO] Building ProjectAdmin
[INFO]
[INFO] Id: com.vsct.wdi:ProjectAdmin:war:10.0-SNAPSHOT
[INFO] task-segment: [clean, process-classes]
[INFO] ------------------------------------------------------------ ------------
[INFO] [clean:clean]
[INFO] Deleting file set: C:\devhome\working_directory\10.0\ProjectAdmin-Build\Project Admin\src\main\webapp\WEB-INF\classes (included: [**], excluded: [])
[INFO] [clean:clean]
[INFO] [cobertura:clean]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
---------------------------------------------------
constituent[0]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/aspectjrt -1.5.3.jar
constituent[1]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/commons-c li-1.0.jar
constituent[2]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/commons-l ogging-api-1.1.jar
constituent[3]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/doxia-sin k-api-1.0-alpha-9.jar
constituent[4]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/jsch-0.1. 27.jar
constituent[5]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/jtidy-4au g2000r7-dev.jar
constituent[6]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/log4j-1.2 .12.jar
constituent[7]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-art ifact-3.0-alpha-1.jar
constituent[8]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-cor e-2.1-SNAPSHOT.jar
constituent[9]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-emb edder-2.1-SNAPSHOT.jar
constituent[10]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-lif ecycle-2.1-SNAPSHOT.jar
constituent[11]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-mod el-2.1-SNAPSHOT.jar
constituent[12]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-plu gin-api-2.1-SNAPSHOT.jar
constituent[13]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-pro file-2.1-SNAPSHOT.jar
constituent[14]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-pro ject-2.1-SNAPSHOT.jar
constituent[15]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-rep orting-api-2.1-SNAPSHOT.jar
constituent[16]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-too lchain-2.1-SNAPSHOT.jar
constituent[17]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/maven-wor kspace-2.1-SNAPSHOT.jar
constituent[18]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/plexus-co ntainer-default-1.0-alpha-47.jar
constituent[19]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/plexus-in teractivity-api-1.0-alpha-6.jar
constituent[20]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/plexus-in terpolation-1.0.jar
constituent[21]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/plexus-ut ils-1.5.1.jar
constituent[22]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/wagon-fil e-1.0-beta-2.jar
constituent[23]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/wagon-htt p-lightweight-1.0-beta-2.jar
constituent[24]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/wagon-htt p-shared-1.0-beta-2.jar
constituent[25]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/wagon-pro vider-api-1.0-beta-2.jar
constituent[26]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh -1.0-beta-2.jar
constituent[27]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh -common-1.0-beta-2.jar
constituent[28]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh -external-1.0-beta-2.jar
constituent[29]: file:/c:/devhome/app/apache-maven-2.1-SNAPSHOT/lib/xbean-ref lect-3.4.jar
---------------------------------------------------
java.lang.NullPointerException
at org.apache.maven.project.artifact.MavenMetadataSource$Projec tRelocation.access$0(MavenMetadataSource.java:573)
at org.apache.maven.project.artifact.MavenMetadataSource.retrie veRelocatedArtifact(MavenMetadataSource.java:105)
at org.apache.maven.artifact.resolver.DefaultArtifactCollector. recurse(DefaultArtifactCollector.java:513)
at org.apache.maven.artifact.resolver.DefaultArtifactCollector. recurse(DefaultArtifactCollector.java:554)
at org.apache.maven.artifact.resolver.DefaultArtifactCollector. recurse(DefaultArtifactCollector.java:554)
at org.apache.maven.artifact.resolver.DefaultArtifactCollector. recurse(DefaultArtifactCollector.java:554)
at org.apache.maven.artifact.resolver.DefaultArtifactCollector. recurse(DefaultArtifactCollector.java:554)
at org.apache.maven.artifact.resolver.DefaultArtifactCollector. recurse(DefaultArtifactCollector.java:554)
at org.apache.maven.artifact.resolver.DefaultArtifactCollector. collect(DefaultArtifactCollector.java:132)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.r esolveTransitively(DefaultArtifactResolver.java:347)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.r esolveTransitively(DefaultArtifactResolver.java:321)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.r esolveTransitively(DefaultArtifactResolver.java:289)
at org.apache.maven.plugin.DefaultPluginManager.resolveTransiti veDependencies(DefaultPluginManager.java:1455)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(Def aultPluginManager.java:522)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeG oalAndHandleFailures(DefaultLifecycleExecutor.java:498)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeT askSegmentForProject(DefaultLifecycleExecutor.java:265)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeT askSegments(DefaultLifecycleExecutor.java:191)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java:149)
at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMav en.java:223)
at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(Def aultMaven.java:304)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2( MavenEmbedder.java:904)
at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$ advice(MavenEmbedder.java:304)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedde r.java:1)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnha nced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Lau ncher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithEx itCode(Launcher.java:408)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launc her.java:351)
at org.codehaus.classworlds.Launcher.main(Launcher.java:31)

However for information I also tried maven 2.2.1, and it is working fine.
Previous Topic:Problem using maven-jibx-plugin
Next Topic:validate not called to find dependencies
Goto Forum:
  


Current Time: Tue Oct 21 15:21:44 GMT 2014

Powered by FUDForum. Page generated in 0.08736 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software