redhat-developer / redhat-developer/vscode-java

jaxws-maven-plugin not picked up for generating sources

Open
#566 10 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug codegen Maven
Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
11

Description

We have a project which generates java classes from a .wsdl file. Our jenkins server successfully compiles the project from scratch but our Eclipse IDE configuration requires extra maven lifecycle mapping plugin com.coderplus.m2e.jaxws.

VS Code seems not to be picking up the plugin to generate the wsimport sources.

Environment
  • Operating System: Windows
  • JDK version: JDK 8
  • Visual Studio Code version: 1.24.1
  • Java extension version: 0.26
Steps To Reproduce
  1. Open maven project with jaxws-maven-plugin configured
  2. Wait until java language server finishes
  3. Expect target/generated-sources/ folder
Current Result

${project.build.directory}/generated-sources/wsimport is not created

Expected Result

wsimport sources are generated

Additional Informations
<plugin>
  <groupId>org.jvnet.jax-ws-commons</groupId>
  <artifactId>jaxws-maven-plugin</artifactId>
  <version>2.3</version>
  <executions>
    <execution>
      <id>wsimport-external-services</id>
        <goals>
          <goal>wsimport</goal>
        </goals>
    </execution>
  </executions>
  <configuration>
    <wsdlDirectory>src/main/resources/com/a/b/c/soap</wsdlDirectory>
      <wsdlFiles>
        <wsdlFile>External_Service.wsdl</wsdlFile>
      </wsdlFiles>
      <implDestDir>${project.build.directory}/generated-sources/wsimport</implDestDir>
      <packageName>com.a.b.c.soap</packageName>
      <xjcArgs>
        <xjcArg>-mark-generated</xjcArg>
      </xjcArgs>
      <keep>true</keep>
      <genJWS>false</genJWS>

      <!-- Needed when JDK_Version >= 8 -->
      <vmArgs>
        <vmArg>-Djavax.xml.accessExternalSchema=all</vmArg>
      </vmArgs>
  </configuration>
</plugin>

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by opening a Maven project configured with org.jvnet.jax-ws-commons:jaxws-maven-plugin and waiting for the Java language server to finish. Trace the Maven project import and lifecycle handling for the wsimport goal, using the target/generated-sources/wsimport path as the expected output. Done means the WSDL generates sources in that directory in VS Code without extra Eclipse-only mapping.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, typescript
Domain
build-system, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.