[
https://jira.codehaus.org/browse/JIBX-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=278585#comment-278585
]
Don Corley commented on JIBX-454:
---------------------------------
Klaus,
Thanks for reporting this error. I need a little help reproducing it so I can
find the problem.
I did a 'mvn -X install' on your test project and it built successfully on my
system.
One of our biggest headaches has been problems with eclipse dependencies. Since
eclipse stopped adding their artifacts to maven about four years ago we have
had a huge problem calling this outdated code, especially on systems that use
the newer equinox code.
Could you try to reproduce this bug using our current snapshot code.
Just change the jibx-version to 1.2.4-SNAPSHOT in your project and add these
lines to your POM:
<pluginRepositories>
<pluginRepository>
<id>sonatype-snapshots</id>
<url>http://oss.sonatype.org/content/repositories/snapshots/</url>
</pluginRepository>
</pluginRepositories>
If this works, please notify me.
If this doesn't work, could you give me a little more information about your
software environment?
O/S, maven version, etc.
Thanks,
Don
> ClassNotFoundException: org.eclipse.core.runtime.jobs.ISchedulingRule when
> running jibx-maven-plugin:1.2.3 (schema-codegen) with customizations
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JIBX-454
> URL: https://jira.codehaus.org/browse/JIBX-454
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
> Affects Versions: JiBX 1.2.3
> Reporter: Klaus Claszen
> Assignee: Don Corley
> Priority: Minor
> Attachments: jibx-customization-test.zip
>
>
> We are building sources from a wsdl file using the jibx-maven-plugin:1.2.3.
> The generated classes should implement Serializable, thus we added a
> customization to the plugin configuration.
> {code}
> <plugin>
> <groupId>org.jibx</groupId>
> <artifactId>jibx-maven-plugin</artifactId>
> <version>1.2.3</version>
> <executions>
> <execution>
> <id>generate-java-code-from-schema</id>
> <phase>generate-sources</phase>
> <goals>
> <goal>schema-codegen</goal>
> </goals>
> <configuration>
>
> <schemaLocation>src/main/resources/wsdl</schemaLocation>
> <customizations>
>
> <customization>src/main/config/custom-jibx-codegen.xml</customization>
> </customizations>
> <verbose>true</verbose>
>
> <targetDirectory>target/generated-jibx-sources</targetDirectory>
> </configuration>
> </execution>
> <execution>
> <id>compile-binding</id>
> <phase>process-classes</phase>
> <goals>
> <goal>bind</goal>
> </goals>
> <configuration>
>
> <schemaBindingDirectory>target/generated-jibx-sources</schemaBindingDirectory>
> <load>true</load>
> <validate>true</validate>
> <verify>true</verify>
> </configuration>
> </execution>
> </executions>
> </plugin>
> {code}
> Running this plugin (with -X flag) results in the following error
> {code}
> Caused by: java.lang.ClassNotFoundException:
> org.eclipse.core.runtime.jobs.ISchedulingRule
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
> ... 68 more
> {code}
> We found that - as a workaround - adding the following dependencies to the
> plugin section resolves the missing class.
> {code}
> <dependency>
> <groupId>org.eclipse.core</groupId>
> <artifactId>contenttype</artifactId>
> <version>[3.0.0,)</version>
> </dependency>
> <dependency>
> <groupId>org.eclipse.core</groupId>
> <artifactId>jobs</artifactId>
> <version>[3.0.0,)</version>
> </dependency>
> <dependency>
> <groupId>org.eclipse.equinox</groupId>
> <artifactId>preferences</artifactId>
> <version>[3.0.0,)</version>
> </dependency>
> <dependency>
> <groupId>org.apache.felix</groupId>
> <artifactId>org.osgi.compendium</artifactId>
> <version>[1.0.0,)</version>
> </dependency>
> {code}
> We first added
> {code}
> <dependency>
> <groupId>org.jibx</groupId>
> <artifactId>jibx-run</artifactId>
> <version>1.2.3</version>
> </dependency>
> <dependency>
> <groupId>org.jibx</groupId>
> <artifactId>jibx-extras</artifactId>
> <version>1.2.3</version>
> </dependency>
> {code}
> to our project dependencies but that did not solve the problem.
> The behaviour can be reproduced with the attached test project.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops? How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
_______________________________________________
jibx-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-devs
