Bugzilla – Full Text Bug Listing
| Summary: | [mojo] org.codehaus.mojo:jaxws-maven-plugin support | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Michael Glauche <michael> | ||||
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | aliaksei.lahachou, asaf.mesika, david.matejcek, developer, dordet.n, igor, jeroen.benckhuijsen, robert.munteanu, sdavids, sebastian.kempken, vladnc | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
m2e core development team is looking for help implementing support for various "not covered" maven plugins. If you are interested, wiki [1] provides pointers where to start and we'll be happy to answer questions on m2e-dev mailing list. To avoid duplicate effort, please assign this bugzilla item to yourself if you already work on corresponding m2e extension. [1] m2e extension development is documented in http://wiki.eclipse.org/M2E_Extension_Development Hmm, it seems for some reason I'm not able to vote for this bug. Anyway, I have a question, is this error message related to this bug: Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:jaxws-maven-plugin:1.12:wsimport ? Yes, the error message is related to this enhancement request, see http://wiki.eclipse.org/M2E_plugin_execution_not_covered for more details. How do you place a vote here? (In reply to comment #4) > How do you place a vote here? voting is not enabled for m2e. if you feel strongly enough about a bug, please submit a quality patch with adequate test coverage and m2e development usually gives patches priority over other work. otherwise you just have to wait for somebody else to do the work. in this particular case, "providing a quality patch" means developing a project configurator and making it available for installation from m2e discovery catalog. although we encourage EPL-ed configurators, we accept catalog entries that use other opensource or commercial licenses. Hello World! We created connector for jaxws-maven-plugin and we want to donate it to community. It supports wsimport goal (everything that we needed). You can grab the sources here: https://github.com/htfv/m2e-extras. We don't want to maintain or support or take any responsibility for this code. It would be great if someone takes this code and makes a proper release. We hope it helps. (In reply to comment #6) > Hello World! > > We created connector for jaxws-maven-plugin and we want to donate it to > community. It supports wsimport goal (everything that we needed). You can grab > the sources here: https://github.com/htfv/m2e-extras. > > We don't want to maintain or support or take any responsibility for this code. > It would be great if someone takes this code and makes a proper release. We hope > it helps. Hello back. I might be able to invest some time in testing/polishing if needed. It would be good though if you would clearly state the license of the code ( EPL would be preferred I think ). > Hello back.
>
> I might be able to invest some time in testing/polishing if needed. It would be
> good though if you would clearly state the license of the code ( EPL would be
> preferred I think ).
I put the source under the EPL license.
Same issue is also present for org.jvnet.jax-ws-commons:jaxws-maven-plugin:2.1:wsimport which is the successor of the codehaus project. Is this also taken into account to solve this bug. Also, the last comment is from august last year, any progress on this issue? Any progress? Does this require a blocker against the license jaxws-maven-plugin? I thought the M2E plug-ins even if they use non-EPL plugins as long as the plug-in itself is EPL and passes IP checks should be sufficient. I've seen other efforts https://code.google.com/p/jaxws-maven-connector/ (which I forked to https://github.com/trajano/jaxws-maven-connector to make it work with the current versions of Eclipse and Rational Application Developer) This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. I have forked the jaxws-maven-plugin to provide m2e support along with support for Maven 3.0-3.2 http://site.trajano.net/jaxws-maven-plugin/ This bug is still relevant, please reopen. @Sebastian are you aware of any immediate plans to work on this? I see little point in keeping this open given that nobody did anything about jaxws-maven-plugin in 3+ years. Besides, most likely jaxws-maven-plugin/m2e support can be implemented purely in jaxws-maven-plugin, without any eclipse or m2e specific code. It can be done, but the code changes have not been merged into the official version, right now it's just on my fork. So this defect I think should remain closed and a defect be open and followed up on jaxws-maven-plugin itself. |
Created attachment 198329 [details] small jaxws sample project Hi, the jaxws-maven-plugin does not work with m2eclipse 1.0.0 anymore. The plugin reads one ore more WSDL Files from local directory (src/wsdl/*.wsdl) or remote locations (via URL) and generates the webservice client files. In order to use them the target directory needs to be added as a source directory in eclipse. The updating seems a bit tricky, the plugin itself has a stale file, the best way would be only to run the plugin on the generate-sources task. Attached is a small test project with a sample wsdl. The java sources are by default generated to target/jaxws/wsimport