On Mon, Oct 20, 2014 at 1:45 PM, Ralph Goers <[email protected]> wrote:
> Before starting the release build I do “mvn -P apache-release clean > install”. This builds the distribution. I verify that all the parts are > there (we were missing jul and iostreams in this release). I don’t look at > the license or notice files any more since they are just copied from what > is in SVN. > > I then build the site and navigate to each of the components and look at > the rat report on the web site. This is very tedious but the only way I > know of to properly perform the check. I also glance at the checkstyle > reports and note that I must be the only one whoever looks at them given > the number of errors reported. > WRT RAT, we can fix the build post 2.1 to get RAT to run from the CLI. The parent POM needs at least one exclude or a fixed file. WRT checkstyle, yeah, it's the kind of thing that gets worse and worse unless you make CS fail as part of the build. I think that's what we do over at HttpComponents. Once you get the code clean up once, you turn on fail on error, and it's easier from there... Gary > Ralph > > On Oct 20, 2014, at 10:07 AM, Gary Gregory <[email protected]> wrote: > > +1 > > Downloaded src zip and worked through BUILDING.txt with: > > Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; > 2014-08-11T16:58:10-04:00) > Maven home: C:\Java\apache-maven-3.2.3 > Java version: 1.7.0_71, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.7.0_71\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > > AND Maven 3.0.5 since building the site with 3.2.3 gives some internal > error. > > MD5 OK, ASC OK, RAT reports OK, API Clirr report OK. > > All RAT reports OK based on the site. > > I could not run the RAT report from the command line though. There is no > mention of running the RAT check or the Clirr check for the API module from > the command line. > > Through trial and error, I got Maven to pick up the right version of RAT > with: > > mvn apache-rat:check -P rat > > which gave me: > > [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check > (default-cli) on project log4j: Too many files with unapproved license: 1 > See RAT report in: C:\temp\rc\apache-log4j-2.1-src\target\rat.txt -> [Help > 1] > > because: > > Unapproved licenses: > > src/ide/eclipse/4.3.2/organize-imports.importorder > > So I am not sure how one is supposed to check for RAT compliance without > clicking 100 times on the site and doing a lot of typing by going in each > module to run the RAT check. > > Gary > > > > > On Mon, Oct 20, 2014 at 12:49 AM, Ralph Goers <[email protected]> > wrote: > >> This is a vote to release Log4j 2.1, the next version of the Log4j 2 >> project. >> >> Please download, test, and cast your votes. >> [] +1, release the artifacts >> [] -1, don't release because... >> >> The vote will remain open for 72 hours (or more if required). All >> votes are welcome, but only Logging PMC votes are “officially” counted. As >> always, at least 3 +1 votes are required. >> >> Changes in this release: >> >> New features: >> o LOG4J2-868: Add ShutdownCallbackRegistry interface for customizable >> shutdown callback handling. This is particularly >> useful for application servers that wish to integrate with Log4j >> 2. >> o LOG4J2-589: Supported filtering on custom log levels in configuration. >> o LOG4J2-856: Documentation: add sections on the JUL Adapter, IO Streams >> and NoSQL Appenders to the Maven and Ivy page. >> o LOG4J2-848: Add a Java lookup to provide nicely formatted runtime >> version information. >> o LOG4J2-809: Move reflection utility class to API's private utility >> classes. >> o LOG4J2-833: Documentation: added Runtime Dependencies link to left >> nav-bar on site. >> o LOG4J2-816: Documentation: added section on XInclude to user manual >> Configuration page. >> o LOG4J2-547: Add the Log4j IOStreams component. >> o LOG4J2-431: Added Memory-Mapped File Appender. Thanks to Claude Mamo. >> o LOG4J2-827: Support use of TypeConverter classes through the standard >> Plugin system. >> o LOG4J2-825: Add simple validation constraint annotations for the >> Plugin system. >> o LOG4J2-428: Implement a GELF layout. Thanks to Mark Paluch. >> o LOG4J2-608: Add java.util.logging implementation based on log4j-api. >> See log4j-jul documentation for more details. >> o LOG4J2-793: Add support for custom SLF4J Markers in log4j-slf4j-impl >> module. >> o LOG4J2-771: Add lookup for application main arguments. >> o LOG4J2-787: Add lookup for JVM arguments. >> >> Fixed Bugs: >> o LOG4J2-676: Some typo fixes and enhancements for the site. Thanks to >> Stefan Bodewig. >> o LOG4J2-866: Documentation: fixed missing closing parenthesis in code >> example. Thanks to Gerard Weatherby. >> o LOG4J2-862: Fixed classloader issue that prevented Log4j from finding >> the implementation when used in a custom Ant task. Thanks to Michael >> Sutherland. >> o LOG4J2-861: Documentation: fix broken links on left navigation >> Extending Log4j Configuration sub-menu. >> o LOG4J2-797: Documentation: clarified why log4j-core is a compile time >> dependency in Maven and Ivy page. Thanks to Andreas Rytina. >> o LOG4J2-855: Documentation: fix broken links on Appenders manual page. >> o LOG4J2-807: Prevent NPE when configuration with AsyncLogger/AsyncRoot >> is reloaded. >> o LOG4J2-678: Documentation: fixed minor issues with Log4j2 web >> site/documentation. Thanks to Matt Sicker. >> o LOG4J2-843: Migrate JpaHyperSqlAppenderTest JUnit performance test to >> log4j-perf. >> o LOG4J2-842: Migrate JpaH2AppenderTest JUnit performance test to >> log4j-perf. >> o LOG4J2-841: Migrate JdbcHyperSqlAppenderTest JUnit performance test to >> log4j-perf. >> o LOG4J2-840: Migrate JdbcH2AppenderTest JUnit performance test to >> log4j-perf. >> o LOG4J2-830: Respect external interrupt signal to allow application >> shutdown after joining AsyncAppender thread. >> o LOG4J2-813: MarkerManager Log4jMarker.hasParents() returns opposite of >> correct result. Thanks to David Erichsen, Brandon Barry. >> o LOG4J2-785: Documentation: fixed capitalization inconsistency in user >> manual example config. >> o LOG4J2-829: Fixed issue in RollingFile filePattern: backslashes are >> path separators, not escape characters. >> o LOG4J2-832: ThrowableProxy fails if a class in logged stack trace >> throws java.lang.Error from initializer Thanks to Seth Leger. >> o LOG4J2-745: Avoid ConverterKey plugin clashes by using a more >> predictable plugin loading infrastructure. >> Plugins have been segmented into three parts: class path, >> user-specified packages, and OSGi bundles. Thanks to Scott Harrington. >> o LOG4J2-798: Fixed plugin scanning redundancy causing massive slowdowns >> in certain environments. Thanks to Scott Harrington. >> o LOG4J2-753: Reduced CachedClock thread contention. >> o LOG4J2-819: Fixed memory leak in Tomcat 6 caused by clock background >> threads unintentionally >> started by Tomcat after web application stop. Thanks to Gary >> Gregory. >> o LOG4J2-391: FlumePersistentManager now handles LockConflictExceptions >> in Berkeley Db when sending a batch. Thanks to Kamal Bahadur. >> o LOG4J2-782: Remove invalid Oracle Maven repository. >> o LOG4J2-796: Fixed issue where log4j-to-slf4j did not work correctly >> with SLF4J Simple Logger. >> o LOG4J2-811: SimpleLogger throws ArrayIndexOutOfBoundsException for an >> empty array. Thanks to Yogesh Rao. >> o LOG4J2-663: Fix OSGi Import-Package problem with the JMS API. Thanks >> to Florian Brunner. >> o LOG4J2-783: PatternLayout should use platform character encoding by >> default, not UTF-8. Thanks to Minglei Lee. >> >> Changes: >> o LOG4J2-845: Add 2.1.0 to compatible versions in Log4j API ProviderUtil >> and update Log4jAPIVersion to 2.1.0 in >> core META-INF/log4j-provider.properties. >> o LOG4J2-844: Update JMH to 1.1 from 0.7.2. >> o LOG4J2-831: Documentation: updated FAQ "which jars" diagrams for JUL >> bridge and 2.1 version. >> o LOG4J2-780: Update Spring Framework to 3.2.11.RELEASE from >> 3.2.8.RELEASE. >> o LOG4J2-815: Unify the two JMS appenders into a single appender. >> Configurations written for 2.0 will still work in 2.1+. >> o LOG4J2-790: Update Jackson to 2.4.2 from 2.4.1 (for XML and JSON >> processing). >> o LOG4J2-766: Incomplete documentation for JSONLayout. Thanks to Bruno >> P. Kinoshita. >> o LOG4J2-800: All life cycle implementations should be serializable. >> This is still work in progress. >> o LOG4J2-801: org.apache.logging.log4j.core.Logger should be >> serializable. >> This is still work in progress. >> o LOG4J2-810: Update javax.mail to 1.5.2 from 1.5.0. >> o LOG4J2-822: Update org.eclipse.persistence.jpa to 2.5.2 from 2.5.1. >> o LOG4J2-867: FlumeAppender: maxDelay not in seconds, but milliseconds. >> Add time scale to some settings, for example maxDelayMillis >> instead of maxDelay. >> The old names are aliased for compatibility. >> >> Tag: >> https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;a=tree;hb=d2d77db8e0fddae4fc4fa0f968ceea70f74c3af4 >> >> Web Site: http://people.apache.org/~rgoers/log4j2/ >> >> Artifacts: >> https://repository.apache.org/content/repositories/orgapachelogging-1011/ >> >> You may download all the artifacts by executing: >> >> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate >> https://repository.apache.org/content/repositories/orgapachelogging-1011/org/apache/logging/log4j/ >> Ralph >> > > > > -- > E-Mail: [email protected] | [email protected] > 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: [email protected] | [email protected] 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
