SurefireBooter can initialize classloader with badly formed URLs
Key: MSUREFIRE-148
URL: http://jira.codehaus.org/browse/MSUREFIRE-148
Project: Maven 2.x Surefire Plugin
Type: Bug
Reporter: Jeremy
[ http://jira.codehaus.org/browse/MSUREFIRE-148?page=all ]
Jeremy Boynes updated MSUREFIRE-148:
Attachment: urlEncode.patch
Patch for encoding the URL under 1.3
I don't have that version to hand but I believe it will build/run in that
environment.
T
Invalid signature on installed or deployed POM
--
Key: MGPG-4
URL: http://jira.codehaus.org/browse/MGPG-4
Project: Maven 2.x GPG Plugin
Issue Type: Bug
Reporter: Jeremy Boynes
The sig
[
http://jira.codehaus.org/browse/MGPG-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Boynes closed MGPG-4.
Resolution: Fixed
This does not occur when using Maven 2.0.5, it does with 2.0.4
> Invalid signature on installed or
Add LICENCE and NOTICE files to the jar
---
Key: MJAR-42
URL: http://jira.codehaus.org/browse/MJAR-42
Project: Maven 2.x Jar Plugin
Type: Improvement
Versions: 2.1
Reporter: Jeremy Boynes
Attachments: mvn-jar-patch.tx