javacc plugin or one of its dependencies breaks the site plugin on maven 2.0.1
------------------------------------------------------------------------------

         Key: MOJO-243
         URL: http://jira.codehaus.org/browse/MOJO-243
     Project: Mojo
        Type: Bug

  Components: javacc  
    Versions: 2.0.1    
 Environment: os x 10.4.4, javacc plugin 6.0-snapshot, maven 2.0.1
    Reporter: Greg Kick
    Priority: Critical
 Attachments: buildError.txt

when the javacc plugin is enabled with
<build>
                <extensions>
                        <extension>
                                <groupId>org.codehaus.mojo</groupId>
                                <artifactId>javacc-maven-plugin</artifactId>
                                <version>0.6.1-SNAPSHOT</version>
                        </extension>
                </extensions>
                <plugins>
                        <plugin>
                                <groupId>org.codehaus.mojo</groupId>
                                <artifactId>javacc-maven-plugin</artifactId>
                                <version>0.6.1-SNAPSHOT</version>
                                <configuration>
                                        <multi>true</multi>
                                        <visitor>true</visitor>
                                        <buildNodeFiles>false</buildNodeFiles>
                                </configuration>
                        </plugin>
                </plugins>
        </build>
        <repositories>
                <repository>
                        <id>Maven Snapshots</id>
                        <url>http://snapshots.maven.codehaus.org/maven2/</url>
                        <snapshots>
                                <enabled>true</enabled>
                        </snapshots>
                        <releases>
                                <enabled>false</enabled>
                        </releases>
                </repository>
        </repositories>
builds fail for the site plugin.  the output is attached.  the first run is 
with the above pom fragment commented out, and the second run is with it 
uncommented.  the third run has the stack trace.  this was performed on a clean 
repository, hence all the downloads.  there is no site-specific configuration 
in the pom.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to