You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "maomaode (JIRA)" <ji...@apache.org> on 2007/11/16 06:51:43 UTC

[jira] Resolved: (CXF-1212) wsdl2java mojo dependency clash with testDependencies - no workaround available - new config option needed

     [ https://issues.apache.org/jira/browse/CXF-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

maomaode resolved CXF-1212.
---------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.4

> wsdl2java mojo dependency clash with testDependencies - no workaround available - new config option needed
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-1212
>                 URL: https://issues.apache.org/jira/browse/CXF-1212
>             Project: CXF
>          Issue Type: Bug
>          Components: Build system
>    Affects Versions: 2.0.3
>            Reporter: Gary Tully
>            Assignee: maomaode
>             Fix For: 2.0.4
>
>         Attachments: useConpileClasspath.patch
>
>
> I have a scenarion where the tests require a saxon dependency which causes wsdl2java to bomb when accessing a binding customisation file using the -b option.
> Because the wesl2java mojo always uses the test artifacts I can't have saxon missing for wsdl2java and present for the test run.
> I think wsdl2java should allow an option to specify that teh compile artifacts/dependencies are used. In this way, a subset can be provided for the compile run where wsdl2java is used and the additional dependency can be specified in the test scope.

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