[
https://issues.apache.org/jira/browse/CXF-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487158#comment-13487158
]
Glen Mazza commented on CXF-4606:
---------------------------------
Hopefully this would be a minor fix (others would know better than I), but
calling this a blocker is a bit much, and I suspect trying to fix this would
raise other problems in CXF and/or libraries outside of CXF's control.
Why not join the overwhelming majority of us who don't put spaces in our user
IDs, or failing that, reconfiguring your Maven repository to a non-default
spaceless location? If you keep spaces in your Maven repo location I think
you're going to get headaches in many other Mavenized projects anyway, no
matter what we do.
If I understand this bug report, you're saying that CXF and Maven should be
able to work with any file path that is deemed valid by any operating system
that supports Java, including directory paths that may have spaces, quotes,
colons, commas, etc., in them. Perhaps, but given the amount of effort that
might take at the expense of other functionality (i.e., opportunity cost), and
the user community that that would benefit (those who are contractually
required to have spaces in their Maven repo path, i.e., probably nobody), I'm
not sure it would be worth it. But again, hopefully it might be a simple fix.
> cxf-codegen-plugin doesn't works if Maven repository's path contain spaces
> --------------------------------------------------------------------------
>
> Key: CXF-4606
> URL: https://issues.apache.org/jira/browse/CXF-4606
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Affects Versions: 2.7.0
> Environment: Windows 7 74bit, Maven 2.2.1, jvm 1.7.0_01
> Reporter: Giuseppe Guarnieri
> Priority: Blocker
> Labels: maven
>
> I keep my Maven repository in its default location, C:/Users/Giuseppe
> Guarnieri/.m2/repository
> I've set up a simple CXF-enabled project for building a demo client, copying
> the configuration directly from cxf site. In particular, I've configured the
> plugin as follows:
> {code:xml}
> <plugin>
> <groupId>org.apache.cxf</groupId>
> <artifactId>cxf-codegen-plugin</artifactId>
> <version>${cxf.version}</version>
> <executions>
> <execution>
> <id>generate-sources</id>
> <phase>generate-sources</phase>
> <configuration>
> <sourceRoot>${project.build.directory}/generated/cxf</sourceRoot>
> <wsdlOptions>
> <wsdlOption>
>
> <wsdl>${basedir}/src/main/resources/wsdl/myservice.wsdl</wsdl>
> </wsdlOption>
> </wsdlOptions>
> </configuration>
> <goals>
> <goal>wsdl2java</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> {code}
> but when I run "mvn generate-sources", I get:
> {noformat}
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] org.apache.cxf.bus.extension.ExtensionException: Could not create
> object
> of extension class org.apache.cxf.catalog.OASISCatalogManager.
> Illegal character in opaque part at index 27: jar:file:/C:/Users/Giuseppe
> Guarni
> eri/.m2/repository/org/apache/cxf/cxf-tools-wsdlto-frontend-jaxws/2.7.1-SNAPSHOT
> /cxf-tools-wsdlto-frontend-jaxws-2.7.1-SNAPSHOT.jar!/META-INF/jax-ws-catalog.xml
> [INFO]
> ------------------------------------------------------------------------
> .....
> Caused by: java.lang.IllegalArgumentException: Illegal character in opaque
> part
> at index 27: jar:file:/C:/Users/Giuseppe
> Guarnieri/.m2/repository/org/apache/cxf
> /cxf-tools-wsdlto-frontend-jaxws/2.7.1-SNAPSHOT/cxf-tools-wsdlto-frontend-jaxws-
> 2.7.1-SNAPSHOT.jar!/META-INF/jax-ws-catalog.xml
> {noformat}
> I think the culprit is the space in "jar:file:/C:/Users/Giuseppe
> Guarnieri/..."
--
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
