[
http://jira.codehaus.org/browse/MECLIPSE-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Johns updated MECLIPSE-423:
-----------------------------------
Attachment: pom.xml
POM file for offending project. Note that this is by far the most complicated
POM we have for any of our projects. It's because it is for a WBI project
developed in IBM's WID. WID wants the directory structure to be just right,
and unlike Maven, it's not flexible on that at all. So we have to bend Maven
to the wishes of WID.
But I don't think you really need to duplicate my project. Just create a
MANIFEST that has no Class-Path element for _any_ project, and then run the
plugin.
> NullPointerException when existing Manifest.MF file has no Class-Path element
> -----------------------------------------------------------------------------
>
> Key: MECLIPSE-423
> URL: http://jira.codehaus.org/browse/MECLIPSE-423
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Michael Johns
> Priority: Minor
> Attachments: pom.xml
>
>
> A NullPointerException arises when running the rad goal against a project
> containing a manifest that has no Class-Path element. The exception is
> caught and the only error on the screen is "No
> <project-path>\META-INF\MANIFEST.MF file found". The problem is in the
> RadManifestWriter.orderClasspath() method. It needs to check newValue for
> null before trying to split it up.
> Here's the manifest I had that caused the problem:
> {code}
> Manifest-Version: 1.0
> Build-Jdk: 1.4.2
> Built-By: Michael Johns
> Created-By: Apache Maven
> {code}
> Notice that it has no Class-Path element.
--
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
