On Wed, 20 Sep 2017 17:49:38 +0200, Stefan Bodewig wrote:
On 2017-09-20, Gilles wrote:
On Wed, 20 Sep 2017 07:33:55 -0600, Gary Gregory wrote:
How about dealing with the Automatic-Module-Name MANIFEST header in
the parent POM and releasing that POM first?
Is there a solution to this issue:
https://issues.apache.org/jira/browse/RNG-31
I'm afraid Gary and you are talking about completely different things
(and either of you as well as myself should have changed the subject
line ;-)
I did some 20 minutes ago. :-)
Unfortunately I cannot answer the question about signatures for
modular
builds, I'm not really a maven person. What I can say is that I never
invoke any "assembly" goal when I create a release, the signatures
are
created as a byproduct of running "deploy".
"deploy" will upload to the nexus server, and there is no
problem (signatures are generated automagically).
The problem is for the official distribution (on "dist"): a complete
archive is generated but not signed. :-/
[At least that was what "parent" was (not) doing when RNG v1.0.]
Gilles
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
