You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Peter Rader (Jira)" <ji...@apache.org> on 2019/11/04 09:50:00 UTC
[jira] [Created] (MJAR-267) Propertize
addDefaultImplementationEntries and addDefaultSpecificationEntries
Peter Rader created MJAR-267:
--------------------------------
Summary: Propertize addDefaultImplementationEntries and addDefaultSpecificationEntries
Key: MJAR-267
URL: https://issues.apache.org/jira/browse/MJAR-267
Project: Maven JAR Plugin
Issue Type: Sub-task
Reporter: Peter Rader
The version-entries of MANIFEST.MF are important requirements to a couple of frameworks (eclipse, felix, liferay) and specifications (portlets, osgi) in order to load those modules.
At the moment this deal-breaking configuration of the project is essential in order to create an valid portlet / osgi-modul. Without having the boolean-values as properties we encounter two downsides:
# Only using an indispensable dirty mid-size overhead of overriding the MJAR's modul-configuration we can force MJAR to create this essential MANIFEST.MF-entries.
# We are unable to early fail the build on missing MANIFEST.MF-version-entries. Even more worse the build will generate invalid osgi/portlets quitting "successfully".
# A CI server like Hudson or Jenkins is not able to flange the MANIFEST.MF-version-entries hindsightly.
Suggestion:
Be able to direct the generation of version informations like this:
{quote}{{mvn clean install -Dmaven.addDefaultImplementationEntries=true -Dmaven.addDefaultSpecificationEntries=true}}
{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)