You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Rich Dougherty (JIRA)" <ji...@codehaus.org> on 2008/10/10 04:31:51 UTC
[jira] Commented: (MECLIPSE-319) Make eclipse:rad work with
manifests without "Class-Path:"-entries
[ http://jira.codehaus.org/browse/MECLIPSE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150426#action_150426 ]
Rich Dougherty commented on MECLIPSE-319:
-----------------------------------------
I've come across this problem too - and actually made a near-identical patch. It would be great to get Mikko Koponen's patch into the next version.
> Make eclipse:rad work with manifests without "Class-Path:"-entries
> ------------------------------------------------------------------
>
> Key: MECLIPSE-319
> URL: http://jira.codehaus.org/browse/MECLIPSE-319
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: RAD support
> Affects Versions: 2.4
> Reporter: Mikko Koponen
> Priority: Minor
> Attachments: manifest-classpath-null-check.patch, rad-manifest-problem-log.txt
>
>
> So... We have a project with somewhat bad manifest files, and we'd like to use the rad goal.
> The plugin fails for existing manifests that don't have Class-Path entries, attached is an error log.
> The - also attached - patch fixes this.
--
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