Just FYI, the site does builds but logs errors with Maven 3.3.3, I think
this might be a known issue. This means some reports do not get created. I
do not think there is anything we can do except make a not of which Maven
versions we know work. Maven 3.2.5 works fine for example.

With Maven 3.3.3:

[WARN] An issue has occurred with maven-checkstyle-plugin:2.15:checkstyle,
skipping LinkageError
org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V,
please report an issue to Maven dev team.
java.lang.NoSuchMethodError:
org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
        at
org.apache.commons.logging.impl.SLF4JLocationAwareLog.trace(SLF4JLocationAwareLog.java:99)
        at
org.apache.commons.beanutils.BeanUtilsBean.copyProperty(BeanUtilsBean.java:443)
        at
com.puppycrawl.tools.checkstyle.api.AutomaticBean.configure(AutomaticBean.java:149)
        at
org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:219)
        at
org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:473)
        at
org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:155)
        at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255)
        at
org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:224)
        at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:311)
        at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:129)
        at
org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:182)
        at
org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:141)
        at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
        at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
        at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
        at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Gary

On Sun, May 3, 2015 at 10:21 AM, Gary Gregory <garydgreg...@gmail.com>
wrote:

> The new class DefaultParser does not use generics to define the options
> List, that is suspicious. Looking closer, the list can hold a mix of
> OptionGroup and String instances. Really? Looking at Options I see the list
> defined as List<Object>. This avoids compiler warnings but is nasty. This
> is probably what we have inherited from this very old code base. We should
> at least perpetuate this to DefaultParser's List as a List<Object>.
>
> I switched a couple of years ago to using annotation based CLI processing
> with JCommander. I'd like to come back to Commons for CLI, but not I do not
> see that happening until a very different CLI2 emerges.
>
> This is not the thread for discussing a CLI2 of course... ;-)
>
> Gary
>
> On Sun, May 3, 2015 at 8:18 AM, Benedikt Ritter <brit...@apache.org>
> wrote:
>
>> Hi,
>>
>> We have fixed quite a few bugs and added some significant enhancements
>> since CLI 1.2 was released and the Groovy Project is asking for a new
>> release, so I would like to release CLI 1.3. The most notable change is
>> the
>> introduction of a new API for creating Option instances.
>>
>> CLI 1.3 RC1 is available for review here:
>>   https://dist.apache.org/repos/dist/dev/commons/cli/ (svn revision 8797)
>>
>> Maven artifacts are here:
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1090/
>>
>> Details of changes since 1.2 are in the release notes:
>>   https://dist.apache.org/repos/dist/dev/commons/cli/RELEASE-NOTES.txt
>>   http://people.apache.org/~britter/cli-1.3-RC1/changes-report.html
>>
>> I have tested this with JDK 6, 7 and 8 using maven 3.
>>
>> The tag is here:
>>   http://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.3-RC1/
>> (svn
>> revision 1677410)
>>
>> Site:
>>   http://people.apache.org/~britter/cli-1.3-RC1/
>>   (note some *relative* links are broken and the 1.2 directories are not
>> yet created - these will be OK once the site is deployed)
>>
>> Clirr Report (compared to 1.2):
>>   http://people.apache.org/~britter/cli-1.3-RC1/clirr-report.html
>>
>> RAT Report:
>>   http://people.apache.org/~britter/cli-1.3-RC1/rat-report.html
>>
>> KEYS:
>>   https://www.apache.org/dist/commons/KEYS
>>
>> Please review the release candidate and vote. This vote will close no
>> sooner that 72 hours from now, i.e. after 06-May 2015, 17:30 CEST.
>>
>> [ ] +1 Release these artifacts
>> [ ] +0 OK, but...
>> [ ] -0 OK, but really should fix...
>> [ ] -1 I oppose this release because...
>>
>> Thanks!
>> Benedikt
>>
>>
>> --
>> http://people.apache.org/~britter/
>> http://www.systemoutprintln.de/
>> http://twitter.com/BenediktRitter
>> http://github.com/britter
>>
>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Reply via email to