[ http://jira.codehaus.org/browse/MOJO-222?page=comments#action_58656 ]
Julien Dubois commented on MOJO-222: ------------------------------------ The "Corridor Software Developer" is right. My case is very specific : I'm also using XFire, which in turn uses stax, and which *does* in turn requires this version of XMLBeans. XFire probably uses stax in a different way than the xmlbeans-maven-plugin. So I cannot use the workaround in the "earlier comment", but my issue is very specific, and I've resolved it by using my own private repo. > xmlbeans-jsr173-api not available in any repository > --------------------------------------------------- > > Key: MOJO-222 > URL: http://jira.codehaus.org/browse/MOJO-222 > Project: Mojo > Type: Bug > Components: xmlbeans > Versions: 2.0 > Reporter: John Wells > Assignee: Corridor Software Developer > > > I am trying to use the xmlbeans-maven-plugin. Unfortunately, when running it > I get the following error: > [INFO] Failed to resolve artifact. > GroupId: xmlbeans > ArtifactId: xmlbeans-jsr173-api > Version: 2.0-dev > Reason: Unable to download the artifact from any repository > xmlbeans:xmlbeans-jsr173-api:2.0-dev:jar > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > CoreRepo (http://www-tux/wls/maven2/repository) > Sure enough, when you look at the repository you will see that this file is > indeed not there. The directory structure is there, but the jar files (and > supporting other files) are not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
