[
https://jira.codehaus.org/browse/MNBMODULE-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Glick closed MNBMODULE-145.
---------------------------------
Resolution: Not A Bug
If you use a nonstandard file name, then you must define
{{sourceManifestFile}}, even if it works by accident on Windows without doing
this.
> Manifest generation fails under Unix if netbeans specific manifest file is
> named using capital letters
> ------------------------------------------------------------------------------------------------------
>
> Key: MNBMODULE-145
> URL: https://jira.codehaus.org/browse/MNBMODULE-145
> Project: Maven NetBeans Module Plugin
> Issue Type: Bug
> Affects Versions: 3.5
> Environment: Suse Linux
> Reporter: Michael Küttner
> Assignee: Jesse Glick
> Priority: Minor
>
> In my project all netbeans specific manifest files are named using capital
> letters (e.g. "${basedir}/src/main/nbm/MANIFEST.MF").
> The project builds successfully under Windows and Linux, but under Linux the
> resulting Netbeans application fails to start because of missing module
> dependencies in the manifest file of generated modules.
> The default value of the sourceManifestFile property in
> NetbeansManifestUpdateMojo points to ${basedir}/src/main/nbm/manifest.mf".
> This works under Window but not under Linux (because of case sensitive file
> system).
> The check in NetbeansManifestUpdateMojo at line 255 fails.
> A workaround is to rename all manifest files or explicitly set the
> sourceManifestFile property.
--
This message is automatically generated by JIRA.
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
