On 22 May 2017 at 00:32, Benedikt Ritter <brit...@apache.org> wrote:
> This is not as straight forward as I thought. Simply adding
>
> <Automatic-Module-Name>${commons.automatic-module-name}</Automatic-Module-Name>
>
> Does not work, since this will add an empty entry to the resulting manifest
> file, if a component does not specify the commons.automatic-module-name
> property.
I must have misunderstood the docs:
https://maven.apache.org/shared/maven-archiver/examples/manifestEntries.html
which implied to me that a missing property would cause the manifest
entry to be omitted.
> Then I thought we have to add it to a profile. But how do we activate the
> profile? Profile activation can only be made based on system properties, not
> on build properties.
>
> Does anybody have an idea how to add this to commons parent?
Nope
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
