We have 3 issues: - Updating the commons-parent to effectively require Java 7 so we can run Clirr or an equivalent tool
- Should we still be using Clirr since it is not maintained? http://clirr.sourceforge.net/ shows "Last published: 27 September 2005 | Doc for 0.6". With BeanUtils 1.9.3, we used JApiCmp: https://commons.apache.org/proper/commons-beanutils/japicmp.html - Should we use the Animal Sniffer plugin for all components to build with a more recent Java version than the one the component requires and still check that the code does not use new Java APIs? Gary On Sep 26, 2016 4:03 AM, "Stian Soiland-Reyes" <[email protected]> wrote: > On 23 September 2016 at 19:49, Gary Gregory <[email protected]> > wrote: > > There is no Clirr report but 'mvn clirr:check' runs OK. > > In BeanUtils I used jacoco as clirr-maven-plugin:2.7 fails in JDK8: > > [INFO] Generating "Clirr" report --- > clirr-maven-plugin:2.7:clirr > [INFO] Comparing to version: 1.9.2 > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on > project commons-beanutils: Execution default-site of goal > org.apache.maven.plugins:maven-site-plugin:3.4:site failed: Invalid > byte tag in constant pool: 18 -> [Help 1] > > > Since then clirr-maven-plugin 2.8 has just been released; which uses > Commons BCEL 6.0 and seems to work. > > > Shall we update commons.clirr.version in Commons Parent? It now > requires Java 1.7 which I think is OK for mvn site. > > See also: > > http://central.maven.org/maven2/org/codehaus/mojo/clirr- > maven-plugin/2.8/clirr-maven-plugin-2.8.pom > https://github.com/mojohaus/clirr-maven-plugin/releases/tag/ > clirr-maven-plugin-2.8 > > > -- > Stian Soiland-Reyes > http://orcid.org/0000-0001-9842-9718 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
