[ http://jira.codehaus.org/browse/MNG-2284?page=comments#action_68044 ]
Mike Perham commented on MNG-2284: ---------------------------------- Anyone have any comments on this? Is it a good idea to allow people to futz with their Class-Path? And if so, is it a good idea to hardcode the check for Class-Path in maven-archiver as the patch does? I'm not sure how I feel about this one... > Cannot specify additional classpath entries in manifest when using > addClasspath > ------------------------------------------------------------------------------- > > Key: MNG-2284 > URL: http://jira.codehaus.org/browse/MNG-2284 > Project: Maven 2 > Type: Bug > Components: maven-archiver > Versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4 > Environment: Maven 2.0.4, maven-jar-plugin 2.0 and 2.1-SNAPSHOT, JDK > 1.5.0_06, Windows XP > Reporter: Fredrik Vraalsen > Fix For: 2.0.5 > Attachments: MNG-archiver-classpath.patch > > > When using addClasspath, e.g. in the maven-jar-plugin, it is not possible to > add additional classpath entries using manifestEntries, as this generates an > illegal manifest file (contains two Class-Path entries). Please see > http://jira.codehaus.org/browse/MJAR-41 > I have been looking through the code, and it seems this might need to be > resolved in MavenArchiver? I've attached a simple fix that solves the > problem for me, but a more thorough solution might be needed of course. ;-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
