[
http://jira.codehaus.org/browse/MNBMODULE-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milos Kleint closed MNBMODULE-22.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.7
fixed, the throwing of exception is probably not necessary in this case. if the
manifest in jar is not found, it will recognize the jar as "non-netbeans
module" jar which is ok. all netbeans modules do have a manifest.
please test with your setup, thanks.
http://fisheye.codehaus.org/changelog/mojo/?cs=5618
> Exception in ExamineManifest
> ----------------------------
>
> Key: MNBMODULE-22
> URL: http://jira.codehaus.org/browse/MNBMODULE-22
> Project: Maven 2.x Netbeans Module Plugin
> Issue Type: Wish
> Affects Versions: 2.7
> Reporter: Roland Klein
> Assignee: Milos Kleint
> Fix For: 2.7
>
>
> Why is it necessary to throw an Exception, in the case there is no manifest
> in the jar file?
> As i understood the Java JAR File Specification correct, a JAR file doesn't
> need to have such a manifest file.
> So it is stated in the Introduction to this specification "..The META-INF
> directory, if it exists, is used to store package .....", so it is possible
> there is no manifest, like in the javax.transaction:jta:1.0.1B jar.
> Found in this repo
> http://download.java.net/maven/2/javax/transaction/jta/1.0.1B/
> As a workaround for my work i commented out the throwing of this exception,
> so my build works. But i don't know of any side effects.
> Roland
--
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
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
