Grokbase Groups Maven users May 2003
FAQ
Hi all,

I'm still having problems with classloaders in Maven when using ant
tasks. I am currently unable to use the ant task "style".

Anyone know what is wrong?

I have the following sample:
maven.xml:
<project xmlns:ant="jelly:ant">
<goal name="blah">

${systemScope.setProperty('javax.xml.transform.TransformerFactory','org.apache.xalan.processor.TransformerFactoryImpl')}
<ant:style in="${maven.build.dir}/TESTS-TestSuites.xml"
out="${maven.docs.dest}/junit-report-mail.html"
style="./overview-summary.xsl" processor="trax" />
</goal>
</project>

project.xml:
<project>
<dependencies>
<dependency>
<id>xalan</id>
<version>2.4.1</version>
<url>http://xml.apache.org/xalan-j/</url>
<properties>
<classloader>root.maven</classloader>
</properties>
</dependency>
</dependencies>
</project>

output:
__ __
\/ |__ Jakarta _ ___
\/| / _` \ V / -_) ' \ ~ intelligent projects ~
_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9-SNAPSHOT

[DEBUG] Adding reference: maven.dependency.classpath ->
/home/bporter/repository/xalan/jars/xalan-2.4.1.jar
[DEBUG] Adding reference: maven-classpath ->

BUILD FAILED
Provider org.apache.xalan.processor.TransformerFactoryImpl not found
com.werken.werkz.UnattainableGoalException: Unable to obtain goal [blah]
-- null:4:159: <ant:style> Provider
org.apache.xalan.processor.TransformerFactoryImpl not found
at com.werken.werkz.Goal.fire(Goal.java:646)
at com.werken.werkz.Goal.attain(Goal.java:575)
at
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
at org.apache.maven.cli.App.doMain(App.java:524)
at org.apache.maven.cli.App.main(App.java:1080)
at java.lang.reflect.Method.invoke(Native Method)
at com.werken.forehead.Forehead.run(Forehead.java:543)
at com.werken.forehead.Forehead.main(Forehead.java:573)
org.apache.commons.jelly.JellyTagException: null:4:159: <ant:style>
Provider org.apache.xalan.processor.TransformerFactoryImpl not found
at
org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:701)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:295)
at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
at com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
at com.werken.werkz.Goal.fire(Goal.java:639)
at com.werken.werkz.Goal.attain(Goal.java:575)
at
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
at org.apache.maven.cli.App.doMain(App.java:524)
at org.apache.maven.cli.App.main(App.java:1080)
at java.lang.reflect.Method.invoke(Native Method)
at com.werken.forehead.Forehead.run(Forehead.java:543)
at com.werken.forehead.Forehead.main(Forehead.java:573)
Root cause
javax.xml.transform.TransformerFactoryConfigurationError: Provider
org.apache.xalan.processor.TransformerFactoryImpl not found
at javax.xml.transform.TransformerFactory.newInstance(Unknown
Source)
at
org.apache.tools.ant.taskdefs.optional.TraXLiaison.(Native Method)
at java.lang.Class.newInstance(Class.java:232)
at
org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:371)
at
org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:545)
at
org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:195)
at org.apache.tools.ant.Task.perform(Task.java:319)
at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:231)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
at com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
at com.werken.werkz.Goal.fire(Goal.java:639)
at com.werken.werkz.Goal.attain(Goal.java:575)
at
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
at org.apache.maven.cli.App.doMain(App.java:524)
at org.apache.maven.cli.App.main(App.java:1080)
at java.lang.reflect.Method.invoke(Native Method)
at com.werken.forehead.Forehead.run(Forehead.java:543)
at com.werken.forehead.Forehead.main(Forehead.java:573)
Total time: 9 seconds


maven.log:
2003-05-16 09:29:39,491 INFO org.apache.maven.plugin.PluginManager -
Initializing Plugins!
2003-05-16 09:29:39,598 INFO org.apache.maven.plugin.PluginManager -
Processing Plugin: maven-deploy-plugin-1.1
2003-05-16 09:29:40,762 INFO org.apache.maven.plugin.PluginManager -
Processing Plugin: maven-plexus-plugin-0.2
2003-05-16 09:29:40,836 INFO org.apache.maven.plugin.PluginManager -
Processing Plugin: maven-castor-plugin-1.0
2003-05-16 09:29:40,867 INFO org.apache.maven.plugin.PluginManager -
Processing Plugin: maven-vdoclet-plugin-1.0
2003-05-16 09:29:40,900 INFO org.apache.maven.plugin.PluginManager -
Processing Plugin: maven-sea-plugin-1.0
2003-05-16 09:29:41,154 INFO org.apache.maven.plugin.PluginManager -
Finished initializing Plugins!
2003-05-16 09:29:45,829 ERROR org.apache.commons.jelly.tags.ant.AntTag -
Class com.werken.werkz.jelly.ProjectTag doesn't support the nested
"path" element.
2003-05-16 09:29:46,182 ERROR org.apache.commons.jelly.tags.ant.AntTag -
Class com.werken.werkz.jelly.GoalTag doesn't support the nested "style"
element.

Thanks,
Brett


--
Web Developer
f2 network ~ everything essential
02 8596 4437


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Search Discussions

  • Brett Porter at May 15, 2003 at 11:42 pm

    <properties>
    <classloader>root.maven</classloader>
    </properties>
    I've also tried with <classloader>root</classloader> and without the
    properties at all - but I expect it should be
    <classloader>root</classloader>

    Cheers,
    Brett


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Brett Porter at May 16, 2003 at 12:01 am
    I should also add that this works fine under JDK 1.4, but not 1.3.1. It
    is on Solaris, but I don't think its related to that, as it happens on
    Linux too.

    Is there a good way to get a list of what ant has in its classloader?

    Thanks,
    Brett

    Brett Porter wrote:
    <properties>
    <classloader>root.maven</classloader>
    </properties>

    I've also tried with <classloader>root</classloader> and without the
    properties at all - but I expect it should be
    <classloader>root</classloader>

    Cheers,
    Brett


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
    --
    Web Developer
    f2 network ~ everything essential
    02 8596 4437


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Dion at May 16, 2003 at 12:56 am
    The docbook plugin works this way, and it seems ok.....try maybe adding
    xmlapis to the root classloader....
    --
    dIon Gillard, Multitask Consulting
    Blog: http://www.freeroller.net/page/dion/Weblog
    Work: http://www.multitask.com.au


    Brett Porter <bporter@f2network.com.au> wrote on 16/05/2003 09:31:06 AM:
    Hi all,

    I'm still having problems with classloaders in Maven when using ant
    tasks. I am currently unable to use the ant task "style".

    Anyone know what is wrong?

    I have the following sample:
    maven.xml:
    <project xmlns:ant="jelly:ant">
    <goal name="blah">

    ${systemScope.setProperty('javax.xml.transform.
    TransformerFactory','org.apache.xalan.processor.TransformerFactoryImpl')}
    <ant:style in="${maven.build.dir}/TESTS-TestSuites.xml"
    out="${maven.docs.dest}/junit-report-mail.html"
    style="./overview-summary.xsl" processor="trax" />
    </goal>
    </project>

    project.xml:
    <project>
    <dependencies>
    <dependency>
    <id>xalan</id>
    <version>2.4.1</version>
    <url>http://xml.apache.org/xalan-j/</url>
    <properties>
    <classloader>root.maven</classloader>
    </properties>
    </dependency>
    </dependencies>
    </project>

    output:
    __ __
    \/ |__ Jakarta _ ___
    \/| / _` \ V / -_) ' \ ~ intelligent projects ~
    _| |_\__,_|\_/\___|_||_| v. 1.0-beta-9-SNAPSHOT

    [DEBUG] Adding reference: maven.dependency.classpath ->
    /home/bporter/repository/xalan/jars/xalan-2.4.1.jar
    [DEBUG] Adding reference: maven-classpath ->

    BUILD FAILED
    Provider org.apache.xalan.processor.TransformerFactoryImpl not found
    com.werken.werkz.UnattainableGoalException: Unable to obtain goal [blah]
    -- null:4:159: <ant:style> Provider
    org.apache.xalan.processor.TransformerFactoryImpl not found
    at com.werken.werkz.Goal.fire(Goal.java:646)
    at com.werken.werkz.Goal.attain(Goal.java:575)
    at
    org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394)
    at
    org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
    at org.apache.maven.cli.App.doMain(App.java:524)
    at org.apache.maven.cli.App.main(App.java:1080)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.werken.forehead.Forehead.run(Forehead.java:543)
    at com.werken.forehead.Forehead.main(Forehead.java:573)
    org.apache.commons.jelly.JellyTagException: null:4:159: <ant:style>
    Provider org.apache.xalan.processor.TransformerFactoryImpl not found
    at
    org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:701)
    at
    org.apache.commons.jelly.impl.TagScript.run(TagScript.java:295)
    at
    org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
    at
    org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
    at
    com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
    at com.werken.werkz.Goal.fire(Goal.java:639)
    at com.werken.werkz.Goal.attain(Goal.java:575)
    at
    org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394)
    at
    org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
    at org.apache.maven.cli.App.doMain(App.java:524)
    at org.apache.maven.cli.App.main(App.java:1080)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.werken.forehead.Forehead.run(Forehead.java:543)
    at com.werken.forehead.Forehead.main(Forehead.java:573)
    Root cause
    javax.xml.transform.TransformerFactoryConfigurationError: Provider
    org.apache.xalan.processor.TransformerFactoryImpl not found
    at javax.xml.transform.TransformerFactory.newInstance(Unknown
    Source)
    at
    org.apache.tools.ant.taskdefs.optional.TraXLiaison.<init>(TraXLiaison.java:117)
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:232)
    at
    org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:371)
    at
    org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:545)
    at
    org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:195)
    at org.apache.tools.ant.Task.perform(Task.java:319)
    at
    org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:231)
    at
    org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
    at
    org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
    at
    org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
    at
    com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
    at com.werken.werkz.Goal.fire(Goal.java:639)
    at com.werken.werkz.Goal.attain(Goal.java:575)
    at
    org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394)
    at
    org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
    at org.apache.maven.cli.App.doMain(App.java:524)
    at org.apache.maven.cli.App.main(App.java:1080)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.werken.forehead.Forehead.run(Forehead.java:543)
    at com.werken.forehead.Forehead.main(Forehead.java:573)
    Total time: 9 seconds


    maven.log:
    2003-05-16 09:29:39,491 INFO org.apache.maven.plugin.PluginManager -
    Initializing Plugins!
    2003-05-16 09:29:39,598 INFO org.apache.maven.plugin.PluginManager -
    Processing Plugin: maven-deploy-plugin-1.1
    2003-05-16 09:29:40,762 INFO org.apache.maven.plugin.PluginManager -
    Processing Plugin: maven-plexus-plugin-0.2
    2003-05-16 09:29:40,836 INFO org.apache.maven.plugin.PluginManager -
    Processing Plugin: maven-castor-plugin-1.0
    2003-05-16 09:29:40,867 INFO org.apache.maven.plugin.PluginManager -
    Processing Plugin: maven-vdoclet-plugin-1.0
    2003-05-16 09:29:40,900 INFO org.apache.maven.plugin.PluginManager -
    Processing Plugin: maven-sea-plugin-1.0
    2003-05-16 09:29:41,154 INFO org.apache.maven.plugin.PluginManager -
    Finished initializing Plugins!
    2003-05-16 09:29:45,829 ERROR org.apache.commons.jelly.tags.ant.AntTag -
    Class com.werken.werkz.jelly.ProjectTag doesn't support the nested
    "path" element.
    2003-05-16 09:29:46,182 ERROR org.apache.commons.jelly.tags.ant.AntTag -
    Class com.werken.werkz.jelly.GoalTag doesn't support the nested "style"
    element.

    Thanks,
    Brett


    --
    Web Developer
    f2 network ~ everything essential
    02 8596 4437


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Brett Porter at May 16, 2003 at 1:57 am
    That's where I got the example from.

    I tried with xml-apis and xercesImpl in the deps - didn't help. Makes
    sense, as both are in MAVEN_HOME/lib.

    Running docbook:transform does work.

    I've tried this under a clean install of -beta-8 and -beta-9 - both have
    the same problem. But switching to JDK 1.4 fixes it.

    How can I best find out what the classloaders in use actually are? Is
    there anything else wrong with my sample?

    Thanks,
    Brett

    dion@multitask.com.au wrote:
    The docbook plugin works this way, and it seems ok.....try maybe adding
    xmlapis to the root classloader....
    --
    dIon Gillard, Multitask Consulting
    Blog: http://www.freeroller.net/page/dion/Weblog
    Work: http://www.multitask.com.au


    Brett Porter <bporter@f2network.com.au> wrote on 16/05/2003 09:31:06 AM:

    Hi all,

    I'm still having problems with classloaders in Maven when using ant
    tasks. I am currently unable to use the ant task "style".

    Anyone know what is wrong?

    I have the following sample:
    maven.xml:
    <project xmlns:ant="jelly:ant">
    <goal name="blah">

    ${systemScope.setProperty('javax.xml.transform.
    TransformerFactory','org.apache.xalan.processor.TransformerFactoryImpl')}
    <ant:style in="${maven.build.dir}/TESTS-TestSuites.xml"
    out="${maven.docs.dest}/junit-report-mail.html"
    style="./overview-summary.xsl" processor="trax" />
    </goal>
    </project>

    project.xml:
    <project>
    <dependencies>
    <dependency>
    <id>xalan</id>
    <version>2.4.1</version>
    <url>http://xml.apache.org/xalan-j/</url>
    <properties>
    <classloader>root.maven</classloader>
    </properties>
    </dependency>
    </dependencies>
    </project>

    output:
    __ __
    \/ |__ Jakarta _ ___
    \/| / _` \ V / -_) ' \ ~ intelligent projects ~
    _| |_\__,_|\_/\___|_||_| v. 1.0-beta-9-SNAPSHOT

    [DEBUG] Adding reference: maven.dependency.classpath ->
    /home/bporter/repository/xalan/jars/xalan-2.4.1.jar
    [DEBUG] Adding reference: maven-classpath ->

    BUILD FAILED
    Provider org.apache.xalan.processor.TransformerFactoryImpl not found
    com.werken.werkz.UnattainableGoalException: Unable to obtain goal [blah]
    -- null:4:159: <ant:style> Provider
    org.apache.xalan.processor.TransformerFactoryImpl not found
    at com.werken.werkz.Goal.fire(Goal.java:646)
    at com.werken.werkz.Goal.attain(Goal.java:575)
    at
    org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394)
    at
    org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
    at org.apache.maven.cli.App.doMain(App.java:524)
    at org.apache.maven.cli.App.main(App.java:1080)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.werken.forehead.Forehead.run(Forehead.java:543)
    at com.werken.forehead.Forehead.main(Forehead.java:573)
    org.apache.commons.jelly.JellyTagException: null:4:159: <ant:style>
    Provider org.apache.xalan.processor.TransformerFactoryImpl not found
    at
    org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:701)
    at
    org.apache.commons.jelly.impl.TagScript.run(TagScript.java:295)
    at
    org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
    at
    org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
    at
    com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
    at com.werken.werkz.Goal.fire(Goal.java:639)
    at com.werken.werkz.Goal.attain(Goal.java:575)
    at
    org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394)
    at
    org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
    at org.apache.maven.cli.App.doMain(App.java:524)
    at org.apache.maven.cli.App.main(App.java:1080)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.werken.forehead.Forehead.run(Forehead.java:543)
    at com.werken.forehead.Forehead.main(Forehead.java:573)
    Root cause
    javax.xml.transform.TransformerFactoryConfigurationError: Provider
    org.apache.xalan.processor.TransformerFactoryImpl not found
    at javax.xml.transform.TransformerFactory.newInstance(Unknown
    Source)
    at
    org.apache.tools.ant.taskdefs.optional.TraXLiaison.<init>(TraXLiaison.java:117)
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:232)
    at
    org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:371)
    at
    org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:545)
    at
    org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:195)
    at org.apache.tools.ant.Task.perform(Task.java:319)
    at
    org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:231)
    at
    org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
    at
    org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
    at
    org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
    at
    com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
    at com.werken.werkz.Goal.fire(Goal.java:639)
    at com.werken.werkz.Goal.attain(Goal.java:575)
    at
    org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394)
    at
    org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
    at org.apache.maven.cli.App.doMain(App.java:524)
    at org.apache.maven.cli.App.main(App.java:1080)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.werken.forehead.Forehead.run(Forehead.java:543)
    at com.werken.forehead.Forehead.main(Forehead.java:573)
    Total time: 9 seconds


    maven.log:
    2003-05-16 09:29:39,491 INFO org.apache.maven.plugin.PluginManager -
    Initializing Plugins!
    2003-05-16 09:29:39,598 INFO org.apache.maven.plugin.PluginManager -
    Processing Plugin: maven-deploy-plugin-1.1
    2003-05-16 09:29:40,762 INFO org.apache.maven.plugin.PluginManager -
    Processing Plugin: maven-plexus-plugin-0.2
    2003-05-16 09:29:40,836 INFO org.apache.maven.plugin.PluginManager -
    Processing Plugin: maven-castor-plugin-1.0
    2003-05-16 09:29:40,867 INFO org.apache.maven.plugin.PluginManager -
    Processing Plugin: maven-vdoclet-plugin-1.0
    2003-05-16 09:29:40,900 INFO org.apache.maven.plugin.PluginManager -
    Processing Plugin: maven-sea-plugin-1.0
    2003-05-16 09:29:41,154 INFO org.apache.maven.plugin.PluginManager -
    Finished initializing Plugins!
    2003-05-16 09:29:45,829 ERROR org.apache.commons.jelly.tags.ant.AntTag -
    Class com.werken.werkz.jelly.ProjectTag doesn't support the nested
    "path" element.
    2003-05-16 09:29:46,182 ERROR org.apache.commons.jelly.tags.ant.AntTag -
    Class com.werken.werkz.jelly.GoalTag doesn't support the nested "style"
    element.

    Thanks,
    Brett


    --
    Web Developer
    f2 network ~ everything essential
    02 8596 4437


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
    --
    Web Developer
    f2 network ~ everything essential
    02 8596 4437


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Incze Lajos at May 16, 2003 at 2:07 am

    I have the following sample:
    maven.xml:
    <project xmlns:ant="jelly:ant">
    <goal name="blah">

    ${systemScope.setProperty('javax.xml.transform.
    TransformerFactory','org.apache.xalan.processor.TransformerFactoryImpl')}
    <ant:style in="${maven.build.dir}/TESTS-TestSuites.xml"
    out="${maven.docs.dest}/junit-report-mail.html"
    style="./overview-summary.xsl" processor="trax" />
    </goal>
    </project>

    project.xml:
    <project>
    <dependencies>
    <dependency>
    <id>xalan</id>
    <version>2.4.1</version>
    <url>http://xml.apache.org/xalan-j/</url>
    <properties>
    <classloader>root.maven</classloader>
    </properties>
    </dependency>
    </dependencies>
    </project>
    I'm using xalan the same way, but had not set the 'root.maven' property
    on the xalan dependency at all. I have:

    <dependency>
    <groupId>xalan</groupId>
    <artifactId>xalan</artifactId>
    <version>2.4.1</version>
    <url>http://xml.apache.org/xalan-j/</url>
    </dependency>

    and in my maven.xml (essentially, processor attr. not needed it's deprecated):

    <ant:xslt in="${source}" style="${style} out="${result}"/>

    incze

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Brett Porter at May 16, 2003 at 3:18 am
    This worked for me also under -beta-7, but not -beta-8 or 9. Are you
    using JDK 1.3, or 1.4? It works under 1.4.

    I've tried exactly like this, but to no avail :(

    - Brett
    I'm using xalan the same way, but had not set the 'root.maven' property
    on the xalan dependency at all. I have:

    <dependency>
    <groupId>xalan</groupId>
    <artifactId>xalan</artifactId>
    <version>2.4.1</version>
    <url>http://xml.apache.org/xalan-j/</url>
    </dependency>

    and in my maven.xml (essentially, processor attr. not needed it's deprecated):

    <ant:xslt in="${source}" style="${style} out="${result}"/>

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Incze Lajos at May 16, 2003 at 8:01 pm

    On Fri, May 16, 2003 at 01:18:24PM +1000, Brett Porter wrote:
    This worked for me also under -beta-7, but not -beta-8 or 9. Are you
    using JDK 1.3, or 1.4? It works under 1.4.

    I've tried exactly like this, but to no avail :(

    - Brett
    I'm using xalan the same way, but had not set the 'root.maven' property
    on the xalan dependency at all. I have:

    <dependency>
    <groupId>xalan</groupId>
    <artifactId>xalan</artifactId>
    <version>2.4.1</version>
    <url>http://xml.apache.org/xalan-j/</url>
    </dependency>

    and in my maven.xml (essentially, processor attr. not needed it's deprecated):

    <ant:xslt in="${source}" style="${style} out="${result}"/>
    I'm using jdk 1.4.1_02, and maven head under linux.

    incze

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Paulo Silveira at May 16, 2003 at 8:52 pm
    Hello all

    It would be very nice if we had a plugin repository, similar to the jars
    repository.
    Then maven could try to download a maven plugin if it does not find it.

    For example, maven-xdoclets plugins are used for many people, but if
    somebody else downloads maven for the first time, it will not be able to
    build a project that uses one of these non-standard plugins.

    thanks for listening
    ------------------------
    Paulo Silveira
    http://www.paulo.com.br/
    http://www.guj.com.br/




    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Dion at May 17, 2003 at 4:01 am
    The idea is that they both be the same repository. And your project could
    specify a dependency on a particular plugin, or you could manually
    download it using something like:

    maven -Dplugin=xdoclet-1.2 plugin:download
    --
    dIon Gillard, Multitask Consulting
    Blog: http://www.freeroller.net/page/dion/Weblog
    Work: http://www.multitask.com.au


    "Paulo Silveira" <paulo@paulo.com.br> wrote on 16/05/2003 05:52:30 PM:
    Hello all

    It would be very nice if we had a plugin repository, similar to the jars
    repository.
    Then maven could try to download a maven plugin if it does not find it.

    For example, maven-xdoclets plugins are used for many people, but if
    somebody else downloads maven for the first time, it will not be able to
    build a project that uses one of these non-standard plugins.

    thanks for listening
    ------------------------
    Paulo Silveira
    http://www.paulo.com.br/
    http://www.guj.com.br/




    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Bert van Brakel at May 17, 2003 at 4:07 am
    and sources and javadocs. So we have

    --
    -jars
    -plugins
    -srcs
    -javadocs
    I could generate the docs from the sources, but that requires getting
    the source and making sure it builds. It also makes it possible then to
    automatically link all the javadocs from various projects, so I can have
    one central point where I can browse the API. Currently I do this
    manually and it would be great if it could be automated. I'm fairly sure
    other would find it useful too.

    -Bert
    On Sat, 2003-05-17 at 08:52, Paulo Silveira wrote:
    Hello all

    It would be very nice if we had a plugin repository, similar to the jars
    repository.
    Then maven could try to download a maven plugin if it does not find it.

    For example, maven-xdoclets plugins are used for many people, but if
    somebody else downloads maven for the first time, it will not be able to
    build a project that uses one of these non-standard plugins.

    thanks for listening
    ------------------------
    Paulo Silveira
    http://www.paulo.com.br/
    http://www.guj.com.br/




    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
    --
    -Bert van Brakel



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Brett Porter at May 16, 2003 at 5:02 am
    To add to the woes... the following ant task works:

    public class MyTask extends Task {
    /**
    * Execute the custon task.
    * @throws BuildException if the task fails.
    */
    public void execute() throws BuildException {
    try {

    Class.forName("org.apache.xalan.processor.TransformerFactoryImpl").newInstance();
    }
    catch (Exception e) {
    e.printStackTrace();
    throw new BuildException("oops");
    }
    }
    }

    When I run it from with Maven 9. Anyone know how I can milk some more
    debug information out of ant running under Maven - similar to say the
    "-debug" switch in Ant?

    Is there a way to upgrade ant to 1.5.3 cleanly? They seem to have done
    some work on the TraXLiason class which might help.

    Cheers,
    Brett

    dion@multitask.com.au wrote:
    The docbook plugin works this way, and it seems ok.....try maybe adding
    xmlapis to the root classloader....
    --
    dIon Gillard, Multitask Consulting
    Blog: http://www.freeroller.net/page/dion/Weblog
    Work: http://www.multitask.com.au

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Dion at May 16, 2003 at 5:51 am
    Run maven -X and see what you get...
    --
    dIon Gillard, Multitask Consulting
    Blog: http://www.freeroller.net/page/dion/Weblog
    Work: http://www.multitask.com.au


    Brett Porter <bporter@f2network.com.au> wrote on 16/05/2003 03:02:36 PM:
    To add to the woes... the following ant task works:

    public class MyTask extends Task {
    /**
    * Execute the custon task.
    * @throws BuildException if the task fails.
    */
    public void execute() throws BuildException {
    try {

    Class.forName("org.apache.xalan.processor.TransformerFactoryImpl").
    newInstance();
    }
    catch (Exception e) {
    e.printStackTrace();
    throw new BuildException("oops");
    }
    }
    }

    When I run it from with Maven 9. Anyone know how I can milk some more
    debug information out of ant running under Maven - similar to say the
    "-debug" switch in Ant?

    Is there a way to upgrade ant to 1.5.3 cleanly? They seem to have done
    some work on the TraXLiason class which might help.

    Cheers,
    Brett

    dion@multitask.com.au wrote:
    The docbook plugin works this way, and it seems ok.....try maybe
    adding
    xmlapis to the root classloader....
    --
    dIon Gillard, Multitask Consulting
    Blog: http://www.freeroller.net/page/dion/Weblog
    Work: http://www.multitask.com.au

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Brett Porter at May 16, 2003 at 5:55 am
    The ant task worked.. which was what confused me.

    The original email included the -X output. Just a bunch of stack traces
    from TraXLiason saying the provider
    org.apache.xalan.processor.TransformerFactoryImpl can't be found.

    This has got me rather confused... I'm trying an upgrade to ant 1.5.3 at
    the moment.

    Cheers,
    Brett

    dion@multitask.com.au wrote:
    Run maven -X and see what you get...
    --
    dIon Gillard, Multitask Consulting
    Blog: http://www.freeroller.net/page/dion/Weblog
    Work: http://www.multitask.com.au

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Brett Porter at May 16, 2003 at 6:00 am
    success!

    replacing ant-1.5.1.jar and ant-optional-1.5.1.jar in the MAVEN_HOME/lib
    directory with the corresponding JARs from ant-1.5.3-1 just downloaded
    works perfectly.

    Can we make sure -beta-10 gets distributed with these?

    Cheers,
    Brett

    dion@multitask.com.au wrote:
    Run maven -X and see what you get...

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Dion at May 18, 2003 at 11:11 am
    Done.
    --
    dIon Gillard, Multitask Consulting
    Blog: http://www.freeroller.net/page/dion/Weblog
    Work: http://www.multitask.com.au


    Brett Porter <bporter@f2network.com.au> wrote on 16/05/2003 04:01:00 PM:
    success!

    replacing ant-1.5.1.jar and ant-optional-1.5.1.jar in the MAVEN_HOME/lib
    directory with the corresponding JARs from ant-1.5.3-1 just downloaded
    works perfectly.

    Can we make sure -beta-10 gets distributed with these?

    Cheers,
    Brett

    dion@multitask.com.au wrote:
    Run maven -X and see what you get...

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Brett Porter at May 18, 2003 at 10:38 pm
    In that case, would you mind closing MAVEN-433?

    Thanks,
    Brett

    dion@multitask.com.au wrote:
    Done.
    --
    dIon Gillard, Multitask Consulting
    Blog: http://www.freeroller.net/page/dion/Weblog
    Work: http://www.multitask.com.au


    Brett Porter <bporter@f2network.com.au> wrote on 16/05/2003 04:01:00 PM:

    success!

    replacing ant-1.5.1.jar and ant-optional-1.5.1.jar in the MAVEN_HOME/lib
    directory with the corresponding JARs from ant-1.5.3-1 just downloaded
    works perfectly.

    Can we make sure -beta-10 gets distributed with these?

    Cheers,
    Brett

    dion@multitask.com.au wrote:
    Run maven -X and see what you get...

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
    --
    Web Developer
    f2 network ~ everything essential
    02 8596 4437


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Dion at May 18, 2003 at 11:55 pm
    Done.
    --
    dIon Gillard, Multitask Consulting
    Blog: http://www.freeroller.net/page/dion/Weblog
    Work: http://www.multitask.com.au


    Brett Porter <bporter@f2network.com.au> wrote on 19/05/2003 08:38:16 AM:
    In that case, would you mind closing MAVEN-433?

    Thanks,
    Brett

    dion@multitask.com.au wrote:
    Done.
    --
    dIon Gillard, Multitask Consulting
    Blog: http://www.freeroller.net/page/dion/Weblog
    Work: http://www.multitask.com.au


    Brett Porter <bporter@f2network.com.au> wrote on 16/05/2003 04:01:00
    PM:
    success!

    replacing ant-1.5.1.jar and ant-optional-1.5.1.jar in the
    MAVEN_HOME/lib
    directory with the corresponding JARs from ant-1.5.3-1 just downloaded
    works perfectly.

    Can we make sure -beta-10 gets distributed with these?

    Cheers,
    Brett

    dion@multitask.com.au wrote:
    Run maven -X and see what you get...

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
    --
    Web Developer
    f2 network ~ everything essential
    02 8596 4437


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Aslak Hellesoy at May 16, 2003 at 8:25 am
    ----- Original Message -----
    From: Brett Porter <bporter@f2network.com.au>
    Date: Friday, May 16, 2003 7:02 am
    Subject: Re: more classloader woes
    To add to the woes... the following ant task works:

    public class MyTask extends Task {
    /**
    * Execute the custon task.
    * @throws BuildException if the task fails.
    */
    public void execute() throws BuildException {
    try {

    Class.forName
    ("org.apache.xalan.processor.TransformerFactoryImpl").newInstance();

    Have you tried getClass().getClassLoader().loadClass("jksdfokjsdf"); ?

    Aslak
    }
    catch (Exception e) {
    e.printStackTrace();
    throw new BuildException("oops");
    }
    }
    }

    When I run it from with Maven 9. Anyone know how I can milk some
    more
    debug information out of ant running under Maven - similar to say
    the
    "-debug" switch in Ant?

    Is there a way to upgrade ant to 1.5.3 cleanly? They seem to have
    done
    some work on the TraXLiason class which might help.

    Cheers,
    Brett

    dion@multitask.com.au wrote:
    The docbook plugin works this way, and it seems ok.....try
    maybe adding
    xmlapis to the root classloader....
    --
    dIon Gillard, Multitask Consulting
    Blog: http://www.freeroller.net/page/dion/Weblog
    Work: http://www.multitask.com.au

    -------------------------------------------------------------------
    --
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Adrian Sutton at May 16, 2003 at 2:06 pm
    Hi all,
    I've been using maven for a while now for stand alone projects with a
    lot of success, but I'm now starting a new project which requires
    multiple sub projects. I've got the reactor set up and working well
    etc, but am wondering what the best layout in CVS is.

    Essentially the project is extremely modularized which each sub project
    being a separate module that plugs in to the central runtime. Apart
    from all having a dependency on the central runtime each project is
    almost completely independent of all the other components and in the
    future there will be a wide range of new sub projects that get added in
    for a huge range of different purposes.

    My inclination is thus to put each sub project in a separate CVS module
    so that they are separate in CVS as they are in design. Also,
    different groups of people will be working on different modules with
    little or no communication with people on other modules (they all do
    come together to form one product with a heck of a lot of optional add
    ins in the end). All of the examples I've seen with reactor however,
    tend to have each sub project as a folder within the main project's CVS
    module (eg: jakarta-commons). Do people have thoughts on what the best
    way to arrange sub projects in terms of directory hierarchies and CVS?

    On a related note, I'm using Eclipse as my IDE which has the concept of
    projects but not of sub-projects. Running the reactor from the parent
    director when required either from in Eclipse or from the command line
    works fine, but have people got a better way of handling this case?
    Currently, my main project isn't known to Eclipse at all which doesn't
    seem optimal.

    Thanks in advance,

    Adrian Sutton.


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Bert van Brakel at May 17, 2003 at 4:36 am
    you may want to look at cvs options. Have a look at section C 'Reference
    manual for Administrative file'. You may find options in there todo what
    you want. You may be able to have a 'master' module which when checked
    out will automatically also checkout all the other modules. The master
    module may only contain the reactor script.

    Having a quick look at the docs indicates this may be possible, though I
    have only ever used the basic cvs features.

    Hope that helps.If it works wouldn't mind an email indicating how you
    did it as I may need this functionality down the track.

    Hope it helps,
    -Bert

    On Sat, 2003-05-17 at 02:00, Adrian Sutton wrote:
    Hi all,
    I've been using maven for a while now for stand alone projects with a
    lot of success, but I'm now starting a new project which requires
    multiple sub projects. I've got the reactor set up and working well
    etc, but am wondering what the best layout in CVS is.

    Essentially the project is extremely modularized which each sub project
    being a separate module that plugs in to the central runtime. Apart
    from all having a dependency on the central runtime each project is
    almost completely independent of all the other components and in the
    future there will be a wide range of new sub projects that get added in
    for a huge range of different purposes.

    My inclination is thus to put each sub project in a separate CVS module
    so that they are separate in CVS as they are in design. Also,
    different groups of people will be working on different modules with
    little or no communication with people on other modules (they all do
    come together to form one product with a heck of a lot of optional add
    ins in the end). All of the examples I've seen with reactor however,
    tend to have each sub project as a folder within the main project's CVS
    module (eg: jakarta-commons). Do people have thoughts on what the best
    way to arrange sub projects in terms of directory hierarchies and CVS?

    On a related note, I'm using Eclipse as my IDE which has the concept of
    projects but not of sub-projects. Running the reactor from the parent
    director when required either from in Eclipse or from the command line
    works fine, but have people got a better way of handling this case?
    Currently, my main project isn't known to Eclipse at all which doesn't
    seem optimal.

    Thanks in advance,

    Adrian Sutton.


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
    --
    -Bert van Brakel



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupusers @
categoriesmaven
postedMay 15, '03 at 11:31p
activeMay 18, '03 at 11:55p
posts21
users7
websitemaven.apache.org
irc#maven

People

Translate

site design / logo © 2019 Grokbase