[jira] Updated: (MAVEN-156) classpath or jelly:xml issue with XSLT transformations
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 18 Sep 2003 3:12 AM
Changes:
Fix Version changed to 1.1
Fix Version changed from 1.0-final
-
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-156page=history
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-156
Here is an overview of the issue:
-
Key: MAVEN-156
Summary: classpath or jelly:xml issue with XSLT transformations
Type: Bug
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
jelly-integ
Fix Fors:
1.1
Versions:
1.0-beta-7
Assignee:
Reporter: tim stephenson
Created: Thu, 21 Nov 2002 5:28 PM
Updated: Thu, 18 Sep 2003 3:12 AM
Environment: win2k, 1.4.1-b21, maven b7 and also winxp, jdk 1.3.1-01, maven b6
Description:
see also my mail to the user list titled 'Style task / x:transform problem'
It seems there is a general problem with XSLT launched from maven. My own transforms
in the maven.xml and that in the docbook plugin behave the same. Behaviour is that
instead of transforming as expected the transform command is printed to console. Some
processing has occurred (eg var substitution). For example the following:
style in=project.xml
out=${meta.dir}/orion-application.xml
style=${code.templates.dir}/orion-application.xsl/
prints this to the console:
style in=project.xml out=META-INF/orion-application.xml
style=c:/projects/jdf3/utils/templates/codegen/orion-application.xsl/style
but no transform.
The same thing results when using x:transform. Other jelly:xml commands such as
x:parse and so on work fine
Using a java command to fork a VM and launch a Xalan Process command, taking control
of the classpath works ok so I am using this a workaround.
Hopefully it will be obvious to someone that better understands the way maven loads
its classes!
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-156) classpath or jelly:xml issue with XSLT transformations
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Sun, 3 Aug 2003 11:36 PM
Changes:
timeoriginalestimate changed from 0
timeestimate changed from 0 minutes
Fix Version changed to 1.0-final
-
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-156page=history
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-156
Here is an overview of the issue:
-
Key: MAVEN-156
Summary: classpath or jelly:xml issue with XSLT transformations
Type: Bug
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
jelly-integ
Fix Fors:
1.0-final
Versions:
1.0-beta-7
Assignee:
Reporter: tim stephenson
Created: Thu, 21 Nov 2002 5:28 PM
Updated: Sun, 3 Aug 2003 11:36 PM
Environment: win2k, 1.4.1-b21, maven b7 and also winxp, jdk 1.3.1-01, maven b6
Description:
see also my mail to the user list titled 'Style task / x:transform problem'
It seems there is a general problem with XSLT launched from maven. My own transforms
in the maven.xml and that in the docbook plugin behave the same. Behaviour is that
instead of transforming as expected the transform command is printed to console. Some
processing has occurred (eg var substitution). For example the following:
style in=project.xml
out=${meta.dir}/orion-application.xml
style=${code.templates.dir}/orion-application.xsl/
prints this to the console:
style in=project.xml out=META-INF/orion-application.xml
style=c:/projects/jdf3/utils/templates/codegen/orion-application.xsl/style
but no transform.
The same thing results when using x:transform. Other jelly:xml commands such as
x:parse and so on work fine
Using a java command to fork a VM and launch a Xalan Process command, taking control
of the classpath works ok so I am using this a workaround.
Hopefully it will be obvious to someone that better understands the way maven loads
its classes!
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
