There looks like an easy fix for MAVEN-1434.
On Fri, 3 Sep 2004 08:36:08 +0200, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> Ok, that's done.
> It's MAVEN-1434.
>
> I'll correct the plugin to make them work with the 1.0 branch.
> I think that I use some Jelly functions bugged in maven 1.0 but not in 1.1.
>
> Arnaud
>
>
>
> On Fri, 3 Sep 2004 08:51:56 +091800, Brett Porter <[EMAIL PROTECTED]> wrote:
> > Can you file a bug in JIRA gainst 1.1?
> >
> > I wouldn't recommend testing your plugins against 1.1/HEAD at the moment. Test
> > against 1.0 release or 1.0.1 (the MAVEN-1_0-BRANCH).
> >
> > Once they work there, then you can test them against HEAD.
> >
> > - Brett
> >
> >
> >
> > Quoting Arnaud HERITIER <[EMAIL PROTECTED]>:
> >
> > > I have the same error if I try to build maven (ant -f
> > > build-bootstrap.xml) with the JDK 1.3
> > > java version "1.3.1_11"
> > > Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_11-b02)
> > > Java HotSpot(TM) Client VM (build 1.3.1_11-b02, mixed mode)
> > >
> > >
> > >
> > > On Thu, 2 Sep 2004 18:06:19 +0200, Arnaud HERITIER <[EMAIL PROTECTED]>
> > > wrote:
> > > > But I have a problem if I launch plugin:test with a jdk 1.3 :
> > > >
> > > > Now loading uncached plugins
> > > > Finished initializing Plugins!
> > > > Using userBuildPropertiesFile: C:\Documents and
> > > > Settings\aheritier\build.properties
> > > > Using projectPropertiesFile:
> > > > C:\Work\Opensources\maven-plugins\javadoc\project.properties
> > > > Using projectBuildPropertiesFile:
> > > > C:\Work\Opensources\maven-plugins\javadoc\build.properties
> > > > Using userBuildPropertiesFile: C:\Documents and
> > > > Settings\aheritier\build.properties
> > > > Using projectPropertiesFile:
> > > > C:\Work\Opensources\maven-plugins\plugin-parent\project.properties
> > > > Using projectBuildPropertiesFile:
> > > > C:\Work\Opensources\maven-plugins\plugin-parent\build.properties
> > > > Unexpected error evaluating expression
> > > > java.lang.ClassCastException:
> > > >
> > >
> > org.apache.commons.jelly.expression.jexl.JexlExpressionFactory$ExpressionSupportLocal
> > > > at
> > > org.apache.maven.MavenUtils.integrateMapInContext(MavenUtils.java:819)
> > > > at
> > > org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:239)
> > > > at org.apache.maven.MavenUtils.getProject(MavenUtils.java:143)
> > > > at org.apache.maven.MavenUtils.getProject(MavenUtils.java:122)
> > > > at
> > > org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235)
> > > > at org.apache.maven.MavenSession.initialize(MavenSession.java:175)
> > > > at org.apache.maven.cli.App.doMain(App.java:473)
> > > > at org.apache.maven.cli.App.main(App.java:1215)
> > > > at java.lang.reflect.Method.invoke(Native Method)
> > > > at com.werken.forehead.Forehead.run(Forehead.java:551)
> > > > at com.werken.forehead.Forehead.main(Forehead.java:581)
> > > > Unexpected error evaluating expression
> > > > java.lang.ClassCastException:
> > > >
> > >
> > org.apache.commons.jelly.expression.jexl.JexlExpressionFactory$ExpressionSupportLocal
> > > > at
> > > org.apache.maven.MavenUtils.integrateMapInContext(MavenUtils.java:819)
> > > > at
> > > org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:239)
> > > > at org.apache.maven.MavenUtils.getProject(MavenUtils.java:143)
> > > > at org.apache.maven.MavenUtils.getProject(MavenUtils.java:122)
> > > > at
> > > org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235)
> > > > at org.apache.maven.MavenSession.initialize(MavenSession.java:175)
> > > > at org.apache.maven.cli.App.doMain(App.java:473)
> > > > at org.apache.maven.cli.App.main(App.java:1215)
> > > > at java.lang.reflect.Method.invoke(Native Method)
> > > > at com.werken.forehead.Forehead.run(Forehead.java:551)
> > > > at com.werken.forehead.Forehead.main(Forehead.java:581)
> > > > Unexpected error evaluating expression
> > > > java.lang.ClassCastException:
> > > >
> > >
> > org.apache.commons.jelly.expression.jexl.JexlExpressionFactory$ExpressionSupportLocal
> > > > at
> > > org.apache.maven.MavenUtils.integrateMapInContext(MavenUtils.java:819)
> > > > at
> > > org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:239)
> > > > at org.apache.maven.MavenUtils.getProject(MavenUtils.java:143)
> > > > at org.apache.maven.MavenUtils.getProject(MavenUtils.java:122)
> > > > at
> > > org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235)
> > > > at org.apache.maven.MavenSession.initialize(MavenSession.java:175)
> > > > at org.apache.maven.cli.App.doMain(App.java:473)
> > > > at org.apache.maven.cli.App.main(App.java:1215)
> > > > at java.lang.reflect.Method.invoke(Native Method)
> > > > at com.werken.forehead.Forehead.run(Forehead.java:551)
> > > > at com.werken.forehead.Forehead.main(Forehead.java:581)
> > > > Verifying dependencies for maven:maven-javadoc-plugin
> > > > [DEBUG] Adding reference: maven.dependency.classpath ->
> > > > C:\Work\Config\maven\repository\commons-lang\jars\commons-lang-2.0.jar
> > > > running script null
> > > > File...... null
> > > > Element... j:if
> > > > Line...... 33
> > > > Column.... 34
> > > > java.lang.NoSuchMethodError
> > > >
> > > > Is there a known issue with Jelly and jdk 1.3 ?
> > > >
> > > > Arnaud
> > > >
> > > >
> > > >
> > > >
> > > > On Thu, 2 Sep 2004 18:01:09 +0200, Arnaud HERITIER <[EMAIL PROTECTED]>
> > > wrote:
> > > > > I found what happens and why I have a difference between home and work.
> > > > > At work I didn't update maven core from several days.
> > > > > I did it and from now javadoc tests work.
> > > > > These dependencies were updated in maven core :
> > > > > - commons-jelly-20040821.000223.jar
> > > > > - commons-jexl-20040821.000101.jar
> > > > >
> > > > > If you can try to update your core.
> > > > >
> > > > > Arnaud
> > > > >
> > > > >
> > > > >
> > > > > On Thu, 2 Sep 2004 17:35:21 +0200, Arnaud HERITIER <[EMAIL PROTECTED]>
> > > wrote:
> > > > > > I just reproduced it at work.
> > > > > > The problem must be due to tests :
> > > > > > <j:if test="${not empty(pom.build.sourceModifications)}">
> > > > > > and
> > > > > > <j:if test="${empty(pom.build.sourceModifications)}">
> > > > > >
> > > > > > I modified it to recently but it worked :-(
> > > > > >
> > > > > > I'll do some tests to see what happens !
> > > > > >
> > > > > > Arnaud.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Thu, 2 Sep 2004 09:57:51 -0300, Felipe Leme <[EMAIL PROTECTED]>
> > > wrote:
> > > > > > > On Thu, 2 Sep 2004 14:20:57 +0200, "Emmanuel Venisse"
> > > <[EMAIL PROTECTED]> wrote:
> > > > > > >
> > > > > > > > It fails too for me with jdk1.4. The problem is due to the copy tag
> > > in
> > > > > > > > javadoc:init because the project doen't have a source directory
> > > definition
> > > > > > > > in the project.xml (and source files)
> > > > > > >
> > > > > > > I think the plugin should handle this situation better, i.e., check
> > > for the existence of such POM tag and fail with a proper message (rather than
> > > propagate the issue to the ant call).
> > > > > > >
> > > > > > > I can work on that fix (and a new testcase) later at home.
> > > > > > >
> > > > > > > Felipe
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
http://www.multitask.com.au/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
