[
https://jira.codehaus.org/browse/JIBX-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284651#comment-284651
]
Ever Olano commented on JIBX-416:
---------------------------------
Hi Don or anyone,
The status says it's fixed in 1.2.3 but I'm still getting the error. Any
ideas? I still see the eclipse dependencies in the pom's. I was wondering
about the need for those as well.
Thanks,
Ever
> Plugin dependency resolving fails
> ---------------------------------
>
> Key: JIBX-416
> URL: https://jira.codehaus.org/browse/JIBX-416
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
> Affects Versions: JiBX 1.2.2
> Reporter: Antti Koivisto
> Assignee: Don Corley
> Fix For: JiBX 1.2.3
>
> Attachments: maven-jibx-plugin-problematic-build-log-cleaned.txt.txt
>
>
> I'm having a really hard time using the maven jibx plugin. Initially I got
> this same build failure in W7 with Maven 3, but it went away.
> In our Bamboo environment that uses Maven 2, the problem persists:
> {code}
> Missing:
> ----------
> 1) org.eclipse.equinox:registry:jar:3.3.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.equinox
> -DartifactId=registry -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.equinox
> -DartifactId=registry -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse.equinox:registry:jar:3.3.1
> 2) org.eclipse.core:resources:jar:3.4.0
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core
> -DartifactId=resources -Dversion=3.4.0 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core
> -DartifactId=resources -Dversion=3.4.0 -Dpackaging=jar -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:resources:jar:3.4.0
> 3) org.eclipse.core:jobs:jar:3.3.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core -DartifactId=jobs
> -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core -DartifactId=jobs
> -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse.core:jobs:jar:3.3.1
> 4) org.eclipse.core:commands:jar:3.3.0
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core
> -DartifactId=commands -Dversion=3.3.0 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core -DartifactId=commands
> -Dversion=3.3.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse:text:jar:3.3.0-v20070606-0010
> 4) org.eclipse.core:commands:jar:3.3.0
> 5) org.eclipse:osgi:jar:3.3.2
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse -DartifactId=osgi
> -Dversion=3.3.2 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse -DartifactId=osgi
> -Dversion=3.3.2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse:osgi:jar:3.3.2
> ----------
> 5 required artifacts are missing.
> for artifact:
> org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> from the specified remote repositories:
> com.springsource.repository.bundles.release
> (http://maven.springframework.org/release),
> com.springsource.repository.bundles.external
> (http://maven.springframework.org/external),
> codehaus.snapshots (http://snapshots.repository.codehaus.org),
> central (through our artifactory),
> jibx.sf.net (http://jibx.sf.net/maven2),
> com.springsource.repository.bundles.milestone
> (http://maven.springframework.org/milestone),
> JBOSS (https://repository.jboss.org/nexus/content/groups/public/),
> maven2-repository.dev.java.net (http://download.java.net/maven/2),
> snapshots (through our artifactory)
> {code}
> I can't seem to find those dependencies anywhere so that I could add them to
> our artifactory.
> Any ideas?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
jibx-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-devs
