+0, non-binding I found a few minor issues with the plugin site that I filed tickets for, to be fixed later.
However, I was thinking if we should seize the opportunity to remove some user properties here as we did for the 3.0.0 release of the jar plugin. Typically the resources plugin is always used in the build lifecycle, and the user should then configure everything in the pom to have reproducable builds. WDYT? /Anders On Fri, May 6, 2016 at 1:46 AM, Karl Heinz Marbaise <[email protected]> wrote: > Hi, > > We solved 20 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317827&version=12331252 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOURCES%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1266/ > > https://repository.apache.org/content/repositories/maven-1266/org/apache/maven/plugins/maven-resources-plugin/3.0.0/maven-resources-plugin-3.0.0-source-release.zip > > Source release checksum(s): > maven-resources-plugin-3.0.0-source-release.zip sha1: > ff31c3c00161841a02a757ac8584750acbbfcf58 > > Staging site: > http://maven.apache.org/plugins-archives/maven-resources-plugin-LATEST/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > Kind regards > Karl Heinz Marbaise > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
