Yes, but we should figure out how we want to handle the dependency information report. If we include it in the build, publishing the site from trunk will add the dependency information report for the snapshot. we probably can configure it to reuse the commons.release.version property that we're using for the download page build.
2014-08-10 14:07 GMT+02:00 Gary Gregory <garydgreg...@gmail.com>: > How about pushing out commons-parent 35? > > Gary > > <div>-------- Original message --------</div><div>From: brit...@apache.org > </div><div>Date:08/10/2014 05:11 (GMT-05:00) </div><div>To: > comm...@commons.apache.org </div><div>Subject: svn commit: r1617074 - > /commons/proper/csv/trunk/pom.xml </div><div> > </div>Author: britter > Date: Sun Aug 10 09:11:58 2014 > New Revision: 1617074 > > URL: http://svn.apache.org/r1617074 > Log: > Override jacoco version from commons parent to make the build work with > java 8 > > Modified: > commons/proper/csv/trunk/pom.xml > > Modified: commons/proper/csv/trunk/pom.xml > URL: > http://svn.apache.org/viewvc/commons/proper/csv/trunk/pom.xml?rev=1617074&r1=1617073&r2=1617074&view=diff > > ============================================================================== > --- commons/proper/csv/trunk/pom.xml (original) > +++ commons/proper/csv/trunk/pom.xml Sun Aug 10 09:11:58 2014 > @@ -130,6 +130,10 @@ CSV files of various types. > > <checkstyle.version>2.12.1</checkstyle.version> > > > <checkstyle.header.file>${basedir}/LICENSE-header.txt</checkstyle.header.file> > + > + <!-- Override jacoco version from commons parent 34, since it doesn't > work with Java 8. > + Remove this after commons parent 35 has been released. --> > + <commons.jacoco.version>0.7.1.201405082137</commons.jacoco.version> > </properties> > > <build> > > > -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
