This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
use netbeans 7 with bundled maven3; create 2 maven projects, one web, other java; in the web project create simple default webservice, project/new-webservice; the ide wizard creates a default sample webservice; build the web service; deploy to glassfish v301; (builds and deploys fine for me) in the maven java project, choose project/new webservice-client; i chose project for the wsdl location -- and since its deployed, it successfully retrieves the wsdl -- but then fails to complete its build. attached are both project zips; in the mavenjaxwsclient2 zip there is the file jaxws-importLog.txt which is the log file of the ide completing the build after the ide wizard operation of projecct/new-webservice-client -- which contains the build errors.
Created attachment 108038 [details] the maven jaxws client project
Created attachment 108039 [details] the maven jaxws webservice project
I cannot reproduce it. In my case build was long but successful. Did you wait until all required dependencies are downloaded ? In my client project there is three deps : webservices-rt-1.4.jar activation.jar webservices-api-1.4.jar What is your deps list ? I've opened your attached client project and there is only one dep :webservices-api-1.4.jar. Probably you need to refresh your invalid maven folder : try to delete .m2 folder in your home. Then try again to create a client.
i have not (yet) tried a fresh .m2 -- mine currently is 4GB, and may try renaming it -- so a new one would be generated and doing experiments. just for info -- i have invested 20+ hours investigating on around 40 different maven2 projects this issue (jaxws); and i have been reading the maven book also. All of the projects that used jaxws and goals such as wsgen or wsimport had to have a modified pom.xml to build and run. i even tried nb691 and had same issues, and external maven - both 2.0.9, and 3.0; and command line mvn.bat vs netbeans driven. i did get all my (many) jaxws projects to build and run -- but i had to custom modify all the pom.xml files -- many of those were not created with netbeans, but came from various book examples -- Beginning JavaEE 6 by http://www.antoniogoncalves.org/xwiki/bin/view/Main/WebHome and others; i also tried creating brand new projects from the netbeans 7 samples -- the maven calculator service and client -- and they have the same issues -- and will not build without modifying pom.xml; the projects i attached to this report were brand new nb7 created projects, as described, and the pom.xml shows the dependencies that netbeans put into my pom.xml -- (my limited knowledge of maven -- how could this be different from you???) you asked ? Did you wait until all required dependencies are downloaded ? yes, did you look at the log file i provided of the maven build ??? it was named jaxws-importLog.txt and is contained in the client project that was attached to this project. i could attach the modified pom.xml i came up with that allowed the client project to build and run -- but it sounds like you are saying you are unable to duplicate this issue? -- so this might not be relevant ? did you create the projects from scratch like i did - and have not issues? and/or did you use the projects i attached to this project ?
ok -- i renamed my .m2 so another would get generated. now i can create a new maven jaxws service and client and they work. also can create the example maven calculator service and client and they work. what a bunch of wasted time i spent on this -- i had told maven to do an -U -- to refresh repository -- what else could i have done? how are you suppose to know its a .m2 issue verses some other issue. thanks
I'm not a maven expert. I just know that sometimes existing .m2 could be a problem ( may be versions collision ).