+1
My checks:
- builds with JKD7 and JDK5
- builds with Windows 7
- Rat check is clean
- sha1 is de491abe498134e92ca50570ad5d78e6afe15bf4
congrats with an issueless project (for now) :)
The m-javadoc-p version is 2.9, which doesn't contain the fix for
CVE-2013-1571[1]
However, the manifest files says Build-Jdk: 1.7.0_45
So the javadoc reports are using the fix of the JDK itself, so that should
be fine as well.
Robert
[1] http://jira.codehaus.org/browse/MJAVADOC-370
Op Sat, 09 Nov 2013 09:10:47 +0100 schreef Tony Chemit
<[email protected]>:
Hi,
We solved 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18134&styleName=Text&projectId=11761
There are no more issues left in JIRA :)
Staging repo:
https://repository.apache.org/content/repositories/maven-109/
https://repository.apache.org/content/repositories/maven-109/org/apache/maven/shared/maven-jarsigner/1.1/maven-jarsigner-1.1-source-release.zip
Staging site (svnpubsub in progress):
http://maven.apache.org/shared-archives/maven-jarsigner-1.1
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
My +1
tony.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
