[MJAR-267] Propertize addDefaultImplementationEntries and addDefaultSpecificationEntries

[jira-importer]

Peter Rader opened MJAR-267 and commented

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 in an consistent way.

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 three downsides:

1. 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.
2. 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".
3. 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:

mvn clean install -Dmaven.addDefaultImplementationEntries=true -Dmaven.addDefaultSpecificationEntries=true

---

This issue is a sub-task of MJAR-57

[jira-importer]

Michael Osipov commented

Frankly, I absolutely do not understand the problem. You have both entry sets. Can you rephrase your problem?

[jira-importer]

Peter Rader commented

Do you understand the suggestion?

[jira-importer]

Michael Osipov commented

I do not understand its purpose because I do not understand the problem itself.

[jira-importer]

Karl Heinz Marbaise commented

First it would be helpful to make an example project which shows the behaviour what you might think is wrong or should be changed based on your point of view.
Furthermore please describe in detail what you have tried and how your build look like(example project is very important).