XFire

JAXB Sample Compilation problem

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0
  • Fix Version/s: 1.1-beta-1
  • Component/s: JAXB 2.0
  • Labels:
    None
  • Number of attachments :
    1

Description

I am trying to compile the JAXB 2.0 sample provided with XFire 1.0 and am running into a problem that I can't seem to resolve. I have tried compiling with maven 2.0.1 and 2.0.2, then fell back to 1.0.2 just to make sure. But in any case, I keep encountering the following error that I have not been able to resolve; I have included the jaxb-xjc-2.0-ea3.jar into the ant classpath in every manner that i can think of, including modifying the maven.xml ant jaxb.classpath definition but to no avail. I am ready to tear my hair out over this. Any idea how to resolve this issue?

If this is not the appropriate place to seek help for this, my apologies in advance.

[INFO] [antrun:run

{execution: default}

]
[INFO] Executing tasks
[INFO] ----------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ----------------------------------------------------------------------------
[INFO] Error executing ant tasks

Embedded error: taskdef class com.sun.tools.xjc.XJCTask cannot be found
[INFO] ----------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ----------------------------------------------------------------------------
[INFO] Total time: 7 seconds
[INFO] Finished at: Tue Feb 28 11:43:44 PST 2006
[INFO] Final Memory: 4M/9M
[INFO] ----------------------------------------------------------------------------

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dan Diephouse added a comment -

Hi John, that is very bizarre. I think we're going to need to get a little bit more info to figure out whats going on. Can you run maven with the "-X" option and attach the stack trace to this issue? Thanks!

Show
Dan Diephouse added a comment - Hi John, that is very bizarre. I think we're going to need to get a little bit more info to figure out whats going on. Can you run maven with the "-X" option and attach the stack trace to this issue? Thanks!
Hide
Permalink
John Mulligan added a comment -

I also modified my "maven.xml" file to include the following definition for jaxb-path:

<ant:path id="jaxb.path">
<ant:path refid="maven.dependency.classpath" />
<ant:pathelement path="$

{maven.build.dest}

" />
<ant:pathelement path="$

{maven.test.dest}

" />
<ant:pathelement path="./lib/jaxb-xjc-2.0-ea3.jar"/>
</ant:path>

Show
John Mulligan added a comment - I also modified my "maven.xml" file to include the following definition for jaxb-path: <ant:path id="jaxb.path"> <ant:path refid="maven.dependency.classpath" /> <ant:pathelement path="$ {maven.build.dest} " /> <ant:pathelement path="$ {maven.test.dest} " /> <ant:pathelement path="./lib/jaxb-xjc-2.0-ea3.jar"/> </ant:path>
Hide
Permalink
Ulrich Deiters added a comment -

Hi!

I had the same error running (mvn test) the geoip-client example with maven 2.0.2
The classpathref maven.dependency.classpath seems to be corrupted.

(Write it out to stdout to take a look at it:
<property name="testpath" refid="maven.compile.classpath"/>
<echo>maven.compile.classpath: $

{testpath}

</echo>
)

I've changed the classpathref of the taskdef in pom.xml to the compile classpath

<taskdef name="wsgen" classname="org.codehaus.xfire.gen.WsGenTask"
classpathref="maven.compile.classpath">
</taskdef>

and it works!

This seems to be a feature (or bug?) of maven-antrun-plugin: http://jira.codehaus.org/browse/MANTRUN-38

Show
Ulrich Deiters added a comment - Hi! I had the same error running (mvn test) the geoip-client example with maven 2.0.2 The classpathref maven.dependency.classpath seems to be corrupted. (Write it out to stdout to take a look at it: <property name="testpath" refid="maven.compile.classpath"/> <echo>maven.compile.classpath: $ {testpath} </echo> ) I've changed the classpathref of the taskdef in pom.xml to the compile classpath <taskdef name="wsgen" classname="org.codehaus.xfire.gen.WsGenTask" classpathref="maven.compile.classpath"> </taskdef> and it works! This seems to be a feature (or bug?) of maven-antrun-plugin: http://jira.codehaus.org/browse/MANTRUN-38
Hide
Permalink
Dan Diephouse added a comment -

Thanks for the info!

Show
Dan Diephouse added a comment - Thanks for the info!
Hide
Permalink
Dan Diephouse added a comment -

I committed a fix to CVS, so marking this as fixed.

Show
Dan Diephouse added a comment - I committed a fix to CVS, so marking this as fixed.

People

  • Assignee:
    Dan Diephouse
    Reporter:
    John Mulligan
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: