How did you add the artifact to your local repo and what version of Maven
are you using?

/Anders


On Wed, Sep 18, 2013 at 2:55 PM, Gerhards, Matthias <
matthias.gerha...@dvka.de> wrote:

> ** **
>
> ** **
>
> Hi Anders,****
>
> thanks for the good answer on the jaxb upgrade problem. The solution in
> http://jira.codehaus.org/browse/MJAXB-61 works fine for the version
> upgrade to 2.x.x. I’ve tested that, to be sure, that every thing is
> running. But in my extended case (using jaxb-facets from
> https://github.com/whummer/jaxb-facets) there’s still a maven problem. ***
> *
>
> ** **
>
> My pom now looks like this:****
>
> ** **
>
> <plugin>****
>
> <groupId>org.codehaus.mojo</groupId>****
>
>             <artifactId>jaxb2-*maven*-*plugin*</artifactId>****
>
>             <version>1.5</version>****
>
>             <dependencies>****
>
>                   <dependency>****
>
>                         <groupId>com.sun.xml.bind</groupId>****
>
>                         <artifactId>*jaxb*-*xjc*</artifactId>****
>
>                         <version>2.2.6</version>****
>
>                   </dependency>****
>
>                   <dependency>****
>
>                         <groupId>com.sun.xml.bind</groupId>****
>
>                         <artifactId>*jaxb*-*impl*</artifactId>****
>
>                         <version>2.2.6-facets-1.0.9</version>
>                     ****
>
>                   </dependency>****
>
>             </dependencies>****
>
>             <executions>****
>
>                   <execution>****
>
> …****
>
> ** **
>
> Note that „<version>2.2.6-facets-1.0.9</version>“ is the forked
> implementation of jaxb facets. Should be api compatible to jaxb-impl 2.2.6.
> ****
>
> ** **
>
> ** **
>
> Using this, I am getting the following error:****
>
> --------------------------------------------------------****
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:jaxb2-maven-plugin:1.5:schemagen (default) on project
> model: Execution default of goal
> org.codehaus.mojo:jaxb2-maven-plugin:1.5:schemagen failed: Plugin
> org.codehaus.mojo:jaxb2-maven-plugin:1.5 or one of its dependencies could
> not be resolved: Failure to find
> com.sun.xml.bind:jaxb-impl:jar:2.2.6-facets-1.0.9 in
> http://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:jaxb2-maven-plugin:1.5:schemagen (default) on
> project model: Execution default of goal
> org.codehaus.mojo:jaxb2-maven-plugin:1.5:schemagen failed: Plugin
> org.codehaus.mojo:jaxb2-maven-plugin:1.5 or one of its dependencies could
> not be resolved: Failure to find
> com.sun.xml.bind:jaxb-impl:jar:2.2.6-facets-1.0.9 in
> http://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced  ****
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
> ****
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> ****
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> ****
>
> …..****
>
> ** **
>
> *I know, that does not seem to be a problem of the plugin, but a maven
> problem. But the jars are present in local repository and there should be
> no reason to fetch them from the remote repository anyhow. By the way:
> proxy settings are fine. Any idea?*
>
> * *
>
> * *
>
> *Kind regards*
>
> * *
>
> Matthias Gerhards ****
>
> ** **
>
> ** **
>  ------------------------------
>
> *Von:* anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] *Im
> Auftrag von *Anders Hammar
> *Gesendet:* Mittwoch, 18. September 2013 12:14
> *An:* Mojo Users List
> *Betreff:* Re: [mojo-user] force jaxb2-maven-plugin schemagen to use any
> other jaxb version than 2.1?****
>
> ** **
>
> You could possibly do this by overriding the deps for the plugin. Se
> example here:****
>
> http://jira.codehaus.org/browse/MJAXB-61****
>
> ** **
>
> For this example to work you need to use the same groupId and artifactId
> as the orifinal deps. Only change version. IIRC you cannot exclude any
> existing deps.****
>
> ** **
>
> /Anders****
>
> ** **
>
> On Wed, Sep 18, 2013 at 10:10 AM, Gerhards, Matthias <
> matthias.gerha...@dvka.de> wrote:****
>
> H al,****
>
> can I convince jaxb2-maven-plugin on java 6 to use any other jaxb version
> than 2.1 e.g. using the endorsed strategy? In my case I would like to
> replace jaxb 2.1 by a forked version called jaxb-facets that includes
> extended features for schema generation with schemagen. I’ve tried to
> manage that stuff now for two days and forehead is sour from all the head
> banging ;-)****
>
>  ****
>
> Regards****
>
> Matthias Gerhards****
>
> Externer Mitarbeiter
> *GKV-Spitzenverband**
> Deutsche Verbindungsstelle
> Krankenversicherung - Ausland (DVKA)
> Postfach 20 04 64*
> *D-53134 Bonn* ****
>
> Telefon +49 228 9530 -661
> Telefax  +49 228 9530-9
> E-Mail     matthias.gerhards*@dvka.de <matthias.gerha...@dvka.de>
> *Internet   *www.dvka.de*****
>
>  ****
>
> ** **
>

Reply via email to