[jbosstools-issues] [JBoss JIRA] (JBIDE-18352) Include a working JAX-WS configurator in the m2e catalog

Xavier Coulon (JIRA) issues at jboss.org
Tue Sep 23 07:58:03 EDT 2014


     [ https://issues.jboss.org/browse/JBIDE-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xavier Coulon updated JBIDE-18352:
----------------------------------
    Description: 
there are compilation/build errors when importing projects using the jaxws maven plugin (see javaee7-samples case on JBDS-2847), because the project is not properly configured during the import. Generated code from the project's WSDL would be missing. 
The known work-around is to invoke maven from command-line to have the code generated.

Having a fine-tuned, working m2e configurator (ie, tuned for incremental builds and not triggering a full interface generation when some unrelated file is edited) would fix the problem.

  was:
there are compilation/build errors when importing projects using the jaxws maven plugin (see javaee7-samples case on JBDS-2847), because the project is not properly configured during the import.

Having a fine-tuned, working m2e configurator (ie, tuned for incremental builds and not triggering a full interface generation when some unrelated file is edited) would fix the problem.



> Include a working JAX-WS configurator in the m2e catalog
> --------------------------------------------------------
>
>                 Key: JBIDE-18352
>                 URL: https://issues.jboss.org/browse/JBIDE-18352
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: maven, upstream
>    Affects Versions: 4.2.0.Beta3
>            Reporter: Xavier Coulon
>            Assignee: Fred Bricon
>             Fix For: 4.3.x
>
>
> there are compilation/build errors when importing projects using the jaxws maven plugin (see javaee7-samples case on JBDS-2847), because the project is not properly configured during the import. Generated code from the project's WSDL would be missing. 
> The known work-around is to invoke maven from command-line to have the code generated.
> Having a fine-tuned, working m2e configurator (ie, tuned for incremental builds and not triggering a full interface generation when some unrelated file is edited) would fix the problem.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


More information about the jbosstools-issues mailing list