[ 
https://jira.codehaus.org/browse/JIBX-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=278919#comment-278919
 ] 

Klaus Claszen commented on JIBX-454:
------------------------------------

Hi Don,

the error still remains with the 1.2.4-SNAPSHOT

{code}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 9.107s
[INFO] Finished at: Wed Sep 14 09:38:09 CEST 2011
[INFO] Final Memory: 9M/495M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal 
org.jibx:jibx-maven-plugin:1.2.4-SNAPSHOT:schema-codegen 
(generate-java-code-from-schema)
 on project jibx-customization-test: Execution generate-java-code-from-schema 
of goal org.jibx:jibx-maven-plugin:1.2.4-S
NAPSHOT:schema-codegen failed: A required class was missing while executing 
org.jibx:jibx-maven-plugin:1.2.4-SNAPSHOT:sc
hema-codegen: org/eclipse/core/runtime/jobs/ISchedulingRule
{code}

I try this at work with the following environment:

Windows 7
Apache Maven 3.0.3
and Nexus 1.9.2 Repository Manager (with 
http://oss.sonatype.org/content/repositories/snapshots/ configured)

Surprisingly (for me) it works at home (plugin version 1.2.3) where I do not 
use a Repository Manager. So I assume it has to do somethig with the usage of 
Nexus. I checked the Nexus logs but can not find anything usable. And as I 
described, if I declare the missing plugin dependencies in my pom.xml it works 
- so I can download them via Nexus. I would give you more information - but I 
do not know what to check next.

Beside that you mentioned the usage of outdated code. If I can do any other 
configuration to achive my customization (without running through outdated 
code) I can also change my pom.xml. Any hints are appreciated!

Thanks for your efforts
Klaus



> 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

        

------------------------------------------------------------------------------
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerry&reg; mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry&reg; DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1 
_______________________________________________
jibx-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-devs

Reply via email to