Hiyas, I started have a problem with my XJC plugin recently Also note that I'm running this test mainly on Windows 7, but I zipped up this project and moved it to my CentOS VM and it gives me the exact same error. I have tried java -cp jaxb-api If you are interested in details: The following is my current script: Asked 4 years, 8 months ago.
| Uploader: | Akinonos |
| Date Added: | 2 July 2014 |
| File Size: | 67.12 Mb |
| Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
| Downloads: | 86039 |
| Price: | Free* [*Free Regsitration Required] |
Index of /helio_taverna/helio_repository/com/sun/xml/bind/jaxb-impl/
Sign up using Facebook. I tried putting the jars for those two plugins into the xjc classpath, but when I run the XJC task, I get the following:. If it matters, my Maven configuration for the xjc plugin looks something like this: Improving the question-asking experience.
By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service.
Subscribe to RSS
Failed to read schema document 'xjc. You could construct the same test by downloading all of those artifacts to your Gradle or Maven cache and copying them into a simple folder structure. XJCFacade -verbose -extension -Xxew -d src xsd.
After some experimentation, this is what worked for me: Is jaxb-impl-2.1.8.iar something about the way m2e invokes the external maven instance that could cause this?
I have tried java -cp jaxb-api In order to summarize the solution for this, I'm trying to characterize the classpath required to "reference" XJC as opposed to "running" XJC. So the correct command line is:.
I also ended up with a similar solution, almost exactly in fact. Actually you can workaround like this solution found after source code inspection: Actually, all maven plugins like jaxb2-maven-plugin or maven-jaxb2-plugin … know about this feature and form XJC argments correctly. Karr Jan 29 '15 at Karr Jan 16 '15 at 5: XmlElementWrapperPlugin not a subtypeso the problem is clearly reproducible. Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information.
If you are interested in details: For instance, the main XJC jars are needed to "reference" XJC, but the extension jars need to be in the "running" classpath.
XJCFacade -verbose -extension -d src xsd and indeed that fails with Exception in thread "main" java. Note that I have removed jaxb-api Any idea what's going on here? This is the version of maven used by m2e during workspace build, so maybe this can explain the different output you get.
Stack Overflow works best with JavaScript enabled. Email Required, but never shown. Keith -- Keith Barlow. XJCFacade -verbose -extension -d src xsd. We do use a customized version of the XJC plugin, however the problem only happens when invoking the plugin through M2E in eclipse.
Index of /groups/proxy/com/sun/xml/bind/jaxb-impl/2.1.8
For java8 add -Djavax. The current build uses a couple of extensions, one of which is a copy of the "element wrapper" plugin, and the jaxb-impl-2.1.8.jar is the "jaxb-fluent-api". Asked 4 years, 8 months ago. Also, my output shows the following warnings, I am not sure if they may be relevant:
Comments
Post a Comment