jaxws-maven-plugin generates handler folder in the root of the parent project

[glassfishrobot]

Running mvn compile causes a folder structure containing the handler.xml files to be generated int the root of the parent project.

**Child pom.xml**<plugin>
    <groupId>org.jvnet.jax-ws-commons</groupId>
    <artifactId>jaxws-maven-plugin</artifactId>
    <version>2.2</version>
    <executions>
        <execution>
            <id>wsimport-somethingservice</id>
            <goals>
                <goal>wsimport</goal>
            </goals>
            <configuration>
                <verbose>true</verbose>
                <target>2.1</target>
                <wsdlDirectory>${basedir}/src/main/wsdl/</wsdlDirectory>
                <bindingDirectory>${basedir}/src/main/wsdl/binding</bindingDirectory>
            </configuration>
        </execution>
    </executions>
</plugin>

Note the first two files and their containing folders which are generated by the plugin: 

**folder structure**jaxws-maven-plugin-bug-parent
  com/something/SomethingService_handler.xml
  com/something/SomethingServicePortType_handler.xml{color}
  jaxws-maven-plugin-bug-child/...
  pom.xml

I've also attached a very minimal example. This bug is not reproducible with version 2.1 of jaxws-maven-plugin

Environment

Tested with both maven 2.2.1 and 3.0.3

Affected Versions

[2.2]

[glassfishrobot]

Reported by danmana

[glassfishrobot]

gpeche said: I am suffering the same problem with 2.2:

• Handler files are generated on the directory on which you run the mvn command, so if you mvn install from the parent directory, it will put handler files in parent/my/package/structure. If you mvn install from the child directory, it will put it in child/my/package/structure (both wrong, they should be generated in child/target/classes/my/package/structure or similar)

• If you use false, it will work ok, but then wsimport will not honor your $ {project.build.jdk.version}

  , instead it will compile using the JDK version which you used to launch mvn itself. Then you might get a "Unsupported major.minor version error" if the JDK you use to launch mvn is greater than the one your project is going to run on.ç

• Not reproducible with 2.1

Using Maven 3.0.3 here.

[glassfishrobot]

kleinew said: Probably relevant part from AbstractJaxwsMojogetCommonArgs(), introduced in commit 968:

if (xnocompile && isDefaultOut(getDestDir())) {
            destDir = null;//new File(project.getBuild().getDirectory(), "dummy-ws");
       }

[glassfishrobot]

@lukasj said: http://java.net/projects/jax-ws-commons/sources/svn/revision/1006

[glassfishrobot]

@lukasj said: closing issues after 2.2.1 release

[glassfishrobot]

File: jaxws-maven-plugin-bug-parent.zip Attached By: danmana

[glassfishrobot]

This issue was imported from java.net JIRA JAX_WS_COMMONS-87

[glassfishrobot]

Marked as fixed on Saturday, February 23rd 2013, 4:44:24 pm