Benjamin Bentmann wrote: > Stephane Nicoll wrote: > >> I am trying to stage the ear plugin v 2.4. So far so good but I have >> the following error when I try to generate the site (with -Preporting) >> >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] BUILD ERROR >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Error during page generation >> >> Embedded error: Error rendering Maven report: Failed during checkstyle >> configuration >> Unable to instantiate JavadocPackageCheck > > The configuration for the maven-checkstyle-plugin fetches the rules > directly from SVN and apparently the changes made to maven_checks.xml > for MCHECKSTYLE-105 are not compatible with Checkstyle 4. Until we have
That's me, trying to push out a Checkstyle 5 compatible Maven Checkstyle Plugin. We really shouldn't use trunk in our parent pom, but rather a specific Subversion revision. Otherwise we don't get reproducible builds. > fixed the parent POM, all our releases will suffer from this. A > workaround is to add > > <profiles> > <profile> > <id>reporting</id> > <reporting> > <plugins> > <plugin> > <artifactId>maven-checkstyle-plugin</artifactId> > <configuration> > <configLocation>config/maven_checks.xml</configLocation> > </configuration> > </plugin> > </plugins> > </reporting> > </profile> > </profiles> > > to the plugin POM, making the plugin load the rules from its own JAR. > >> Can I proceed with the release vote with the stage site without >> reports or should we need to fix this first? > > As long as the essential bits of the site (usage, goals, examples) are > eventually deployed, that's fine with me. > > > Benjamin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
