jaxws-maven-plugin not picked up for generating sources

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>

[fbricon]

Ok so, m2e, the underlying Maven integration project, doesn’t know if the jaxws maven plugin is safe to run during the workspace build. The problem is visible when running in Eclipse, where you might be able to install an m2e-jaxws plugin, but is somewhat hidden in jdt.ls/vscode-java.

Anyways, one way to workaround this issue is to let m2e run the plugin during its project configuration phase. One way to do that is to add a processing instruction in the pom.xml like <?m2e execute onConfiguration?> in :

<plugin>
                <groupId>org.jvnet.jax-ws-commons</groupId>
                <artifactId>jaxws-maven-plugin</artifactId>
                <version>2.3</version>
                <executions>
                    <execution>
                        <?m2e execute onConfiguration?>
                        <goals>
                            <goal>wsimport</goal>
                        </goals>

You then need to let vscode update the project configuration:

Or you can execute the “Update project configuration” command manually:

[khe817]

I have the same problem as @kanchev : Even though the maven plugin jaxws-maven-plugin is defined in pom.xml; after VSCode starts up, the java language server does not generate files into target/generated-sources/ nor target/classes/.

I have to run $ mvn package manually to make the maven plugin jaxws-maven-plugin generate files into target/generated-sources/.

After running $ mvn package, the language server also does not recognize imports from target/generated-sources/ because it keep regenerating target/classes/ folder and deleting all the class files created by $ mvn package from target/generated-sources/ .