[
https://issues.apache.org/jira/browse/CXF-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-4538.
------------------------------
Resolution: Not A Problem
Fix Version/s: Invalid
Assignee: Daniel Kulp
As per comments, this isn't a bug as the imported schemas should be resolved
relative to the wsdl.
> cxf-codegen-plugin wsdl2java fails when you have nested projects
> ----------------------------------------------------------------
>
> Key: CXF-4538
> URL: https://issues.apache.org/jira/browse/CXF-4538
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.6.2
> Environment: Linux
> Reporter: Andrew Burks
> Assignee: Daniel Kulp
> Priority: Critical
> Labels: build, maven
> Fix For: Invalid
>
> Attachments: ApacheTestProject.tar
>
>
> In my wsdl, I am importing and xsd from another maven project and I provide a
> relative path to the xsd. When executing mvn clean install on this
> sub-project, call it project A, the project builds as expected. After
> navigating to Project A's parent project and executing mvn clean install, I
> receive a java.io.FileNotFoundException because the relative path provided in
> the import of Project A's wsdl was relative to Project A. I can only assume
> that wsdl2java uses the "current build directory" when applying the
> schemaLocation attribute from an import.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
