I think the problem is that it was originally uploaded with the wrong groupId and was redeployed to fix the error. The correct one is org.jvnet.jaxb1.maven2. In fact, it looks like the documentation was updated with the latest release to reflect the correct groupId also. It can be found at:
https://maven-jaxb1-plugin.dev.java.net/ Specifically, look at: https://maven-jaxb1-plugin.dev.java.net/nonav/plugin-docs/usage.html Hopefully, this is what you were looking for. On 12/18/06, Melo, Alexandre (Alexandre) <[EMAIL PROTECTED]> wrote:
Hi Gregory, As I've checked, today again, there is no jaxb-xjc and plugin-jaxb-maven to jaxb version 1.0, only to the jaxb 2.0. On the repo we can see the following: tools/ 35 5 months maven2_publisher Removed old version of jaxb1 plugin. It wasn't correct. Regards, Alexandre -----Original Message----- From: Gregory Kick [mailto:[EMAIL PROTECTED] Sent: Monday, December 18, 2006 3:41 PM To: Maven Users List Subject: Re: pom dependences on the antrun plugin Hey guys, I wish that I'd seen this thread earlier... The jaxb guys have actually worked pretty hard to get good maven support for both jaxb 1 and 2. The only problem is that most of the artifacts are at the repos at dev.java.net. (We're working on getting them synched). Anyway, check out the plugins listed on jaxb.dev.java.net. There's one for jaxb 1 and 2 and instructions on which repo to list. It doesn't fix your ant problem but hopefully will help. On 12/18/06, Melo, Alexandre (Alexandre) <[EMAIL PROTECTED]> wrote: > Hi Dave, look to my peace of pom.xml and the file with the mvn command. > I have already tried put the jaxb-xjc.jar on the ANT_HOME\lib > directory.. But nothing. > > <build> > <plugins> > <plugin> > > <artifactId>maven-antrun-plugin</artifactId> > <version>1.1</version> > <executions> > <execution> > > <id>generate-sources</id> > > <phase>generate-sources</phase> > <configuration> > <tasks> > > <property name="src.loc" value="./src" /> > > <property name="classpath-maven2" value="maven.dependency.classpath" > /> > > <target > name="x"> > > <xjc > > schema="${src.loc}/main/resources/TestScript.xsd" > > target="src/main/java/" > > package="com.avaya.automation.testscripts" /> > > </target> > > <taskdef > name = "xjc" classname="com.sun.tools.xjc.XJCTask" classpath refid=/> > > <!-- > another way, but calling the build.xml > > <ant antfile="${basedir}/build.xml" > > inheritRefs="true"> > > <target name="x" /> > > </ant> > --> > </tasks> > </configuration> > <goals> > <goal>run</goal> > </goals> > </execution> > </executions> > </plugin> > </plugins> > </build> > > -----Original Message----- > From: Dave Syer [mailto:[EMAIL PROTECTED] > Sent: Monday, December 18, 2006 10:07 AM > To: [email protected] > Subject: RE: pom dependences on the antrun plugin > > > > > Melo, Alexandre (Alexandre) wrote: > > > > No, I think the order is ok, if I inverte the order, look what is > > happen.. > > > > Hmm. That's funny because I use this pattern quite a lot and I have > had issues, but they always went away when the taskdef was nested > (this is because otherwise Ant will try to create the target before > the task is defined, if they are at the same level). Is your task > definitely on the classpath with the reference you used? > > -- > View this message in context: > http://www.nabble.com/pom-dependences-on-the-antrun-plugin-tf2822307s1 > 77 > .html#a7928402 > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- Gregory Kick [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]
-- Gregory Kick [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
