You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Sam Wilson (JIRA)" <ji...@apache.org> on 2009/09/02 17:21:32 UTC

[jira] Created: (AXIS2-4484) CLONE -[wsdl2code] Incorrect target directory for generated sources

CLONE -[wsdl2code]  Incorrect target directory for generated sources
--------------------------------------------------------------------

                 Key: AXIS2-4484
                 URL: https://issues.apache.org/jira/browse/AXIS2-4484
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: Tools
    Affects Versions: 1.1
         Environment: Solaris 10, Maven2 2.0.4, JDK 1.5_06
            Reporter: Sam Wilson
            Assignee: Amila Chinthaka Suriarachchi
            Priority: Minor


When generating sources from wsdl, even if the outputDirectory parameter is  specified (non-default) in the pom.xml, while the plugin will use the value specified, it will insert a "src" directory after the specified outputDirectory value and before the project package.  For example:

outputDirectory=src/main/java  // relative to pom.xml
and
package=org.sourceforge.xyz

the generated classes will go in:
src/main/java/src/org/sourceforge/xyz

Is there a way to eliminate that, so generated sources are exactly in the same directories as project source files?

Somewhat related, an ant build.xml file seems to be generated at the same time under src/main/java, is there an expectation that it will be used (given build with mvn2), if not, can its generation be suspended.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (AXIS2-4484) CLONE -[wsdl2code] Incorrect target directory for generated sources

Posted by "Sam Wilson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750482#action_12750482 ] 

Sam Wilson commented on AXIS2-4484:
-----------------------------------

I am reopening this issue because I believe the original was closed due to a misunderstanding of the issue.

No matter what value is specified for the outputDirectory the code is generated in a sub-directory named "src". What this means is that even if you specify the "outputDirectory" as "x/y/z", the code will actually come out in "x/y/z/src". 

By the documentation that's a defect, or just bad documentation. I think it's reasonable to say that one would expect the code to come out "x/y/z" in this case, so the documentation is likely correct and this is a simple defect.

> CLONE -[wsdl2code]  Incorrect target directory for generated sources
> --------------------------------------------------------------------
>
>                 Key: AXIS2-4484
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4484
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 1.1
>         Environment: Solaris 10, Maven2 2.0.4, JDK 1.5_06
>            Reporter: Sam Wilson
>            Assignee: Amila Chinthaka Suriarachchi
>            Priority: Minor
>
> When generating sources from wsdl, even if the outputDirectory parameter is  specified (non-default) in the pom.xml, while the plugin will use the value specified, it will insert a "src" directory after the specified outputDirectory value and before the project package.  For example:
> outputDirectory=src/main/java  // relative to pom.xml
> and
> package=org.sourceforge.xyz
> the generated classes will go in:
> src/main/java/src/org/sourceforge/xyz
> Is there a way to eliminate that, so generated sources are exactly in the same directories as project source files?
> Somewhat related, an ant build.xml file seems to be generated at the same time under src/main/java, is there an expectation that it will be used (given build with mvn2), if not, can its generation be suspended.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.