Hi, what is the status? Was it moved already? I cannot find it in the central repositor nor in the dev.java.net repository.
Regards, Markus dan tran wrote: > > yes, Jaxws lead pinged me this morning and I think this plugin should > belong > to the right expert group. > But I forget to ping maven dev first. Here is the conversation: > > ============================================ > > Ok. So do you want to start a project on java.net for wsimport/wsgen > maven plugin? I will be more than happy to help you guys move ahead. > See: https://jax-ws-commons.dev.java.net/ has instructions to host a > jaxws commons project. > > Let me know what you think. > > thanks, > > -vivek. > > > > > Dan Tran wrote: >> >> >> On 2/6/07, *Vivek Pandey* <[EMAIL PROTECTED] >> <mailto:[EMAIL PROTECTED]>> wrote: >> >> Dan, >> >> >> Yeah, bring to source to java.net <http://java.net> > >> >> Dan Tran wrote: >> > I would love to see this plugin find its parent back at java.net >> <http://java.net> >> > <http://java.net>. Feel free bring her home. >> You mean host jaxws-maven-plugin at java.net <http://java.net> > >> maven repository? >> > >> > Currently all examples will not work due to jar conficts. See >> > >> > http://jira.codehaus.org/browse/MEV-498 >> jaxws-api-2.1.jar is basically JAXWS 2.1 API - JAXWS 2.1 RI >> implements >> this api and hence the version number in both of them. >> JAXWS-api-2.0.jar >> corresponds to JAX-WS 2.0 API. Hope it clarifies confusion about >> the API >> jars versioning. >> >> >> However the main problem is as long as repo1.maven.com >> <http://repo1.maven.com> keeps hosting the bad jaxws-api-2.1. No one > >> can take advantage of this plugin since maven always goes there first. >> >> >> >> thanks, >> >> -vivek. >> > >> > -D >> > >> > >> > On 2/6/07, *Vivek Pandey* < [EMAIL PROTECTED] >> <mailto:[EMAIL PROTECTED]> > - Show quoted text - >> > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote: >> > >> > Hello, >> > >> > We have released JAX-WS RI 2.1 and there are some wsimport tool >> > changes >> > -B switch is added. For details see[1]. >> > >> > Anyway I tried using is as shown in Usage. However mvn >> install failed >> > for fromwsdl sample as it could not find the jax-ws-maven in >> maven >> > repository. Is this plugin posted on some repository? >> > >> > I get this error while running the sample: >> > -------------------------- >> > [INFO] >> > >> > ---------------------------------------------------------------------------- >> >> > >> > Downloading: >> > >> > http://repo1.maven.org/maven2/org/codehaus/mojo/jaxws-maven-plugin/1.0/jaxws-maven >> < > http://repo1.maven.org/maven2/org/codehaus/mojo/jaxws-maven-plugin/1.0/jaxws-maven >> >> > >> > -plugin-1.0.pom >> > [INFO] >> > >> > ------------------------------------------------------------------------ >> > [ERROR] BUILD ERROR >> > [INFO] >> > >> > ------------------------------------------------------------------------ >> >> > [INFO] Error building POM (may not be this project's POM). >> > >> > Project ID: org.codehaus.mojo:jaxws-maven-plugin >> > >> > Reason: Error getting POM for ' >> org.codehaus.mojo:jaxws-maven-plugin ' >> > from the repository: Error >> > transferring file >> > org.codehaus.mojo:jaxws-maven-plugin:pom:1.0 >> > >> > from the specified remote repositories: >> > central ( http://repo1.maven.org/maven2), > > > > On 2/6/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: >> >> Does anyone there want it? >> >> jason. >> >> On 6 Feb 07, at 7:52 PM 6 Feb 07, Dan Tran wrote: >> >> > >> > Any objections? >> > >> > I think it is logically belonged there. >> > >> > -D >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > -- View this message in context: http://www.nabble.com/Moving-jaxws-maven-plugin-to-https%3A--jax-ws-commons.dev.java.net--tf3184218.html#a9256559 Sent from the mojo - dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
