[ xframe-Bugs-1165772 ] xsddoc maven plugin fails with Java 1.5

Bugs item #1165772, was opened at 2005-03-18 16:53
Message generated for change (Comment added) made by prunge
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1165772&group_id=48863

Category: maven
Group: None
Status: Deleted
Resolution: None
Priority: 5
Submitted By: Peter Runge (prunge)
Assigned to: Kurt Riede (kriede)
Summary: xsddoc maven plugin fails with Java 1.5

Initial Comment:
Attempting to run the xsddoc maven plugin with JDK 
1.5.0_02, using Maven 1.02.  The plugin runs, but results in 
the generated report indicating the xsddoc run failed.  
Clicking the log links on the report page indicate the 
following stack trace:

xsddoc failed with exception: Provider 
org.apache.xalan.processor.TransformerFactoryImpl not 
found
javax.xml.transform.TransformerFactoryConfigurationError: 
Provider 
org.apache.xalan.processor.TransformerFactoryImpl not 
found
        at 
javax.xml.transform.TransformerFactory.newInstance
(Unknown Source)
        at 
net.sf.xframe.xsddoc.Processor.initTransformers
(Processor.java:537)
        at net.sf.xframe.xsddoc.Processor.execute
(Processor.java:450)
        at net.sf.xframe.xsddoc.Processor.run
(Processor.java:475)
...

This seems to not just be a problem with the plugin as 
indicated by the following Maven bug:
http://jira.codehaus.org/browse/MAVEN-156

Since xalan is indeed a dependency of the xsddoc plugin, it 
is possibly a class loading issue with Maven.

A workaround would be to allow a project property to be set 
to override the default transformer.  In the maven-xsddoc-
plugin:report goal in plugin.jelly, the 
systemScope.setProperty line could be changed to read 
from a plugin property, which defaults to the current value.  
This would allow Java 1.5 people (or people who want to 
use other transformers) to use the xsddoc Maven plugin.


----------------------------------------------------------------------

>Comment By: Peter Runge (prunge)
Date: 2005-03-21 09:35

Message:
Logged In: YES 
user_id=416534

Hi Kurt,

using JDK 1.5:
After running the xsddoc:generate goal on my project, the output 
of maven does not indicate an error, it creates the 
target/docs/xsddocs directory and generates some files.  
The .xsd directories are created but are empty.  The txt files 
contain a bit of header text and then the stack trace.

using JDK 1.4 with the maven plugin works perfectly.

I also tried running the xsddoc batch file from the bin directory 
not using Maven at all.  This worked perfectly with JDK 1.5.


----------------------------------------------------------------------

Comment By: Kurt Riede (kriede)
Date: 2005-03-21 04:53

Message:
Logged In: YES 
user_id=484961

Hi Peter,
might you please briefly summarize your expirience with JDK 
1.5? Did you encounter any differences or problems? What 
about XalanJ? Anything special to do different than with JDK 
1.4?

Regards
Kurt

----------------------------------------------------------------------

Comment By: Peter Runge (prunge)
Date: 2005-03-18 17:05

Message:
Logged In: YES 
user_id=416534

(using plugin version 0.7)

Sorry, should have read '[ 1123251 ] maven plugin can't find 
xalan' before submitting this bug.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1165772&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