Success? I think so but I'm doing some final tests and validation. What I did
was this.
1- In my parent pom, I created a pluginmanagement section:
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.codehaus.mojo.jspc</groupId>
<artifactId>jspc-maven-plugin</artifactId>
<version>2.0-alpha-2</version>
<executions>
<execution>
<configuration>
<includeInProject>true</includeInProject>
</configuration>
<goals>
<goal>compile</goal>
</goals>
</execution>
</executions>
<!-- Use the Tomcat 5 JSP compiler -->
<dependencies>
<dependency>
<groupId>org.codehaus.mojo.jspc</groupId>
<artifactId>jspc-compiler-tomcat5</artifactId>
<version>2.0-alpha-2</version>
</dependency>
<!-- the following 2 dependencies are needed all of a sudden
because with out them, the jspc fails -->
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>1.4.1</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>jcl104-over-slf4j</artifactId>
<version>1.4.1</version>
</dependency>
</dependencies>
</plugin>
</plugins>
</pluginManagement>
2- Then in each pom where I wanted this plugin to run:
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo.jspc</groupId>
<artifactId>jspc-maven-plugin</artifactId>
</plugin>
This works when I run the build from anywhere in my pom hierarchy and is
actually a more efficient solution I think instead of having the plugin
specifics duplicated 3 times.
Thoughts on this solution? It seems to work.
I have not yet determined why it "suddenly" broke only other than to speculate
that a different version was brought in by some new dependency. I haven't run
effective pom yet.
Thanks for the tip on the dependencies!
Randy
-----Original Message-----
From: Grégory Joseph [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2008 11:49 AM
To: user@mojo.codehaus.org
Subject: Re: [mojo-user] jspc-maven-plugin suddenly failing
2008/9/11 Randy Eckhoff <[EMAIL PROTECTED]>:
> Thanks for the tip. We are getting close. When I add the logging dependencies
> to the pom, it works when I run the build from that pom's directory. But when
> I go up to the pom's parent pom's directory and run a build there, it fails.
> I tried moving the logger dependencies up to the parent pom and that didn't
> work. I don't want to move the complete plugin to the parent pom because
> there are modules that don't have jsps and don't require it.
As Jason mentioned, you should configure the version of the main plugin too.
As to the reactor build, there have been a couple of issues which were already
opened with alpha-1 and are still opened for alpha-2
http://jira.codehaus.org/browse/MJSPC-4
http://jira.codehaus.org/browse/MJSPC-21
http://jira.codehaus.org/browse/MJSPC-31
One of the patches in MJSPC-4 fixes this in my case.
-g
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
