On Sat, 23 Sep 2017 11:13:04 +0200, Stefan Bodewig wrote:
On 2017-09-21, Gilles wrote:
On Thu, 21 Sep 2017 07:47:07 +0200, Stefan Bodewig wrote:
On 2017-09-20, Gilles wrote:
[...]
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).
mvn deploy -Ptest-deploy -Prelease
creates all signatures but doesn't actually perform the upload.
This
is
what I use.
What this command did not do is create the checksum and
signature for the _full_ distribution (the only _official_
one IIUC) made available here:
http://commons.apache.org/proper/commons-rng/download_rng.cgi
It does for me when using the command on compress, I've just
re-checked
(which caused the delay, sorry). And it does for rng as well, for the
tar.gzs at the module level when run from the root dir of rng.
I know but this creates separate archives (one per module).
Is "Compress" modular?
IIUC, the problem is that IIUC the parent POM is not
"module-ready", i.e. one has to create a "dist-all"
pseudo-module and figure out what to put in the POM
in order to collect the output of the "actual" modules.
Surely, this can be automated by a tool such as maven.
[I.e. upon detecting that the project is modular, an
additional "assembly" command would be executed (without
resorting to an extra directory).]
You seem to have chosen a different way with the dist-archive
directory.
No; I've followed advice from this ML and/or copied the
POM from another project; only to notice at voting time
that the ancillary files were not generated by maven.
This one is not part of the reactor in master and if I try to
run maven from inside the dist-archive folder it fails because mvn is
looking for a checkstyle.xml that isn't there.
Indeed, as noted above, this is a "special" module; only meant
for executing the "assembly" command.
I'm afraid I'm out of my
depth here.
If you manage to create the dist artifacts that you want with your
custom mvn project then you could certainly always fallback to
command
line tools in order to create the hashes and signatures.
That's what I did for RNG v1.0.
Nobody seems to know why this cannot (?) be automated with
maven; nor is it mentioned anywhere (?) that one will have
to generate the checksum and signature manually when
preparing the release of a modular component...
Regards,
Gilles
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
