The java.net repository pom for jsr173_api is here https://maven-repository.dev.java.net/repository/javax.xml.bind/poms/jsr173_ api-1.0.pom
and it has a <groupId>jaxb</groupId> that's why the JAXB 2.0 maven plugin uses the reference <groupId>jaxb</groupId> and not <groupId>javax.xml.bind</groupId>. Kohsuke Kawaguchi may want to look at the java.net repository and update the group ids based on the policy referral below. Thanks all. -----Original Message----- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Thursday, May 18, 2006 3:47 AM To: Maven Users List; [EMAIL PROTECTED] Subject: RE: Maven2 versus JAXB Please note, that the policy for the groupId is "javax.xml" and "com.sun.xml" only. See also http://www.mavenregistry.com/search/artifacts?hl=en&q=jsr173&btnG=Search+Reg istry ________________________________ From: Franz Fehringer Sent: Thursday, May 18, 2006 8:55 AM To: [EMAIL PROTECTED] Cc: Maven Users List Subject: Re: Maven2 versus JAXB Also, in the downloaded maven-jaxb-plugin-1.0.pom <dependency> <groupId>jaxb</groupId> <artifactId>jsr173_api</artifactId> <version>1.0</version> </dependency> should read <dependency> <groupId>javax.xml.bind</groupId> <artifactId>jsr173_api</artifactId> <version>1.0</version> </dependency> Is btw the ant dependency really needed? Greetings Franz Franz Fehringer schrieb: Hello Jonathan, I think the explanations on https://jaxb.dev.java.net/jaxb-maven2-plugin/ are still incorrect. <dependency> <groupId>jaxb</groupId> <artifactId>jaxb-api</artifactId> <version>2.0-SNAPSHOT</version> </dependency> should read <dependency> <groupId>javax.xml.bind</groupId> <artifactId>jaxb-api</artifactId> <version>2.0</version> </dependency> and <dependency> <groupId>jaxb</groupId> <artifactId>jaxb-impl</artifactId> <version>2.0-SNAPSHOT</version> </dependency> </dependencies> should read <dependency> <groupId>com.sun.xml.bind</groupId> <artifactId>jaxb-impl</artifactId> <version>2.0</version> </dependency> </dependencies> Greetings Franz Jonathan Johnson schrieb: Franz, Thank you for finding the dependency version and location problems in the recent JAXB Maven 2 plugin. The versions have all been updated and an updated plugin has been posted. The instructions for using the JAXB Maven 2 plugin are here http://jaxb.dev.java.net/jaxb-maven2-plugin/ - Jonathan -----Original Message----- From: Franz Fehringer [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 17, 2006 11:22 AM To: Maven Users List Cc: [EMAIL PROTECTED] Subject: Re: Maven2 versus JAXB Thanks. The 1.1 option has the slight problem that the referenced poms also still reference the 1.0.2 version, for example https://maven-repository.dev.java.net/repository/com .sun.xml.bind/poms/jaxb- impl-2.0.pom has <dependency> <groupId>javax.xml.bind</groupId> <artifactId>activation</artifactId> <version>1.0.2</version> </dependency> But for the moment i am stuck with nonworking https proxy support (only http works for me; i wrote another mail about this). Greetings Franz Alexandre Poitras schrieb: On 5/17/06, Franz Fehringer <[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]> wrote: Thanks, Now i get (legacy reenabled) D:\projekte\Maven2\iso-app>mvn -U install [INFO] Scanning for projects... [INFO] ------------------------------------ ------------------------------------- --- [INFO] Building Maven Quick Start Archetype [INFO] task-segment: [install] [INFO] ------------------------------------ ------------------------------------- --- [INFO] artifact org.apache.maven.plugins:maven-resources-plugin: checking for updates from central [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking for updates from central [INFO] artifact org.apache.maven.plugins:maven-surefire-plugin: checking for updates from central [INFO] artifact org.apache.maven.plugins:maven-jar-plugin: checking for updates from central [INFO] artifact org.apache.maven.plugins:maven-install-plugin: checking for updates from central [INFO] artifact com.sun.tools.xjc.maven2:maven-jaxb-plugin: checking for updates from central Downloading: https://maven-repository.dev.java.net/nonav/reposito ry/jaxb/poms/activation- 1.0.2.pom [INFO] ------------------------------------ ------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------ ------------------------------------ [INFO] Error building POM (may not be this project's POM). Same with mvn -U compile. There is no https://maven-repository.dev.java.net/nonav/reposito ry/jaxb/poms/activation- 1.0.2.pom but https://maven-repository.dev.java.net/repository/jav ax.activation/poms/activ ation-1.1.pom So it seems the downloadable plugin does not match the directory structure anymore?! Your problem is that before activation 1.1, the license forbidded to deploy it in a global repository. See http://maven.apache.org/guides/mini/guide-co ping-with-sun-jars.html for more info. So basically, you have two choices, either change the plugin .pom file to depend on the 1.1 release or install the 1.0.2 release manually in your local repository. It should do the trick. Btw. i do not understand "run 'mvn install' on the plugin pom". The plugin contains no pom.xml and without it i cannot run mvn? Ah forget it, I thought the plugin was coming with the source. Greetings Franz Alexandre Poitras schrieb: Your answer is in the download section of your link : Download This plugin will be added to the Maven 2 ibiblio repository and also to the java.net repository but we would like your feedback first. If you have praises or problems with this plugin please post your email by joining the mailing list for [EMAIL PROTECTED] by registering here https://jaxb.dev.java.net/servlets/ProjectMailingListList. In the meantime you can download the lastest plugin version from this link and expand the .zip contents into your local %HOMEPATH%/.m2/repository directory. So download it and run 'mvn install' on the plugin pom. Should work afterward. On 5/17/06, Franz Fehringer <[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]> wrote: Hello, I followed the instructions on https://jaxb.dev.java.net/jaxb-maven 2-plugin/ without success. On mvn -U compile i get ERROR] BUILD ERROR INFO] ------------------------------------ ------------------------------------ INFO] The plugin 'com.sun.tools.xjc.maven2:maven-jaxb-plugin' does not exist or no valid version could be found This is with Maven 2.0.4. There is neither com.sun.tools.xjc.maven2 nor maven-jaxb-plugin on https://maven-repository.dev.java.ne t/repository, but there are javax.xml.bind and maven-javanet-plugin. Could i use these in an appropriate way (how?)? My pom.xml is <project xmlns="http://maven.apache.org/POM/4.0.0"; <http://maven.apache.org/POM/4.0.0> xmlns:xsi="http://www.w3.org/2001/XM LSchema-instance" <http://www.w3.org/2001/XMLSchema-instance> xsi:schemaLocation="http://maven.a pache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0 .xsd" <http://maven.apache.org/POM/4.0.0http://maven.apache.org/maven-v4_0_0.xsd> > <modelVersion>4.0.0</modelVersion> <groupId>de.isogmbh.aoo</groupId> <artifactId>iso-app</artifactId> <packaging>jar</packaging> <version>1.0-SNAPSHOT</version> <name>Maven Quick Start Archetype</name> <url>http://maven.apache.org</url> <repositories> <repository> <id>java.net</id> <name>java.net Maven Repository</name> <url>https://maven-repository. dev.java.net/repository</url> <!-- layout>legacy</layout --> </repository> </repositories> <dependencies> <dependency> <groupId>jaxb</groupId> <artifactId>jaxb-api</artifact Id> <version>2.0</version> </dependency> <dependency> <groupId>jaxb</groupId> <artifactId>jaxb-impl</artifac tId> <version>2.0</version> </dependency> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>3.8.1</version> <scope>test</scope> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>com.sun.tools.xjc.m aven2</groupId> <artifactId>maven-jaxb-plugi n</artifactId> <executions> <execution> <goals> <goal>generate</goal> </goals> </execution> </executions> </plugin> <plugin> <groupId>org.apache.maven.pl ugins</groupId> <artifactId>maven-compiler-p lugin</artifactId> <configuration> <source>1.5</source> <target>1.5</target> </configuration> </plugin> </plugins> </build> </project> ------------------------------------ --------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ------------------------------------ --------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ------------------------------------ --------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -------------------------------------------- ------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ---------------------------------------------------- ----------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
