Bugs item #1123251, was opened at 2005-02-15 17:35
Message generated for change (Comment added) made by kriede
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1123251&group_id=48863
Category: maven
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Kurt Riede (kriede)
Summary: maven plugin can't find xalan
Initial Comment:
I'm able to run xsddoc from the command line with a
script like like:
#!/bin/sh
java -Xmx500m -classpath
~/.maven/repository/xsddoc/jars/xsddoc-0.6.jar:~/.maven/repository/xalan/jars/xalan-2.6.0.jar
net.sf.xframe.xsddoc.Main -v -t MyTitle -b
Bottomline -o test
~/chelck-bps1/MarketData/pps/src/xsd/mrfv3.xsd
And it produces the desired report. Yet when I run it
with maven I noticed that xalan doesn't get included in
the classpath when xsddoc is invoked. Here's the
important part of the output from 'maven site -X'
[java] [DEBUG] Execute:Java13CommandLauncher: Executing
'/apps/local/jdk1.5.0/jre/bin/java' with arguments:
'-Xmx500m'
'-classpath'
'/home/chelck/.maven/repository/xsddoc/jars/xsddoc-0.6.jar'
'net.sf.xframe.xsddoc.Main'
'-v'
'-t'
'mrfv3.xsd'
'-o'
'/home/chelck/chelck-bps1/MarketData/pps/target/docs/xsddocs/mrfv3.xsd'
'/home/chelck/chelck-bps1/MarketData/pps/src/xsd/mrfv3.xsd'
It is my understanding that the reason xalan is missing
from the classpath is because it was not listed as a
dependency in the plugin's property.xml file. A
plugin's runtime dependencies are treated the same way
as build time dependencies and need to be specified in
the plugin's project.xml. Can this be fixed or is there
a workaround?
Also I noticed that when I run my script and I do not
include the -b switch I get the error "The value of
param bottom must be a valid Java Object" and nothing
gets produced.
----------------------------------------------------------------------
>Comment By: Kurt Riede (kriede)
Date: 2005-02-25 14:46
Message:
Logged In: YES
user_id=484961
fixed with oncoming release 0.7
----------------------------------------------------------------------
Comment By: Kurt Riede (kriede)
Date: 2005-02-25 14:03
Message:
Logged In: YES
user_id=484961
After deeper analysing of the problem, I found the following
issude report that addresses exaclty this problem:
http://issues.apache.org/jira/browse/JCR-46
So placing the xalan.jat file in the lib/endoresed folder is a
known work-around for this problem, but not a good one. I will
now follow the other suggestion with true dependencies and
setting the system property as described.
Unfortunately we will lose compatibility with with JDK 1.5
because of the new XSLTC transformer until apache has a
better solution fopr this problem.
Regards
Kurt
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2005-02-24 17:20
Message:
Logged In: NO
Yes, you are right!
I checked my configuration and found out, that I have XalanJ
in the lib/endorsed folder of my maven installation, so I didn't
need the dependency.
So for now, you can also drop Xalan (e.g. xalan-2.4.1.jar) into
that folder.
I will fix this in the next release.
Regards
Kurt
PS: Sorry for the delay of my answer. I was on a busy project
and xframe is solely unpayed private work
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1123251&group_id=48863
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
|