On Thu, 15 Dec 2022 at 10:52, Gilles Sadowski <gillese...@gmail.com> wrote:
>
> Le jeu. 15 déc. 2022 à 11:01, Gilles Sadowski <gillese...@gmail.com> a écrit :
> >
> > Le jeu. 15 déc. 2022 à 10:53, Gilles Sadowski <gillese...@gmail.com> a 
> > écrit :
> > >
> > > Hi.
> > >
> > > So using the insecure way of passing a password on the command-line,
> > > I'm one step further:  Which files to delete from Nexus (and how).
> > > Why can't we seem to avoid uploading unnecessary files there?
> > > Is the problem with Nexus or the release process or maven?
> > > Now that they are there, is there still no other way than to pick them
> > > up one at a time, click on "Delete" and then click for confirmation (that
> > > make it largely the most time consuming task of the process)?
> > >
> > > Please confirm that only the
> > >   *.jar
> > >   *.pom
> > >   *.cyclonedx.xml
> > >   *.cyclone.json
> > >   *.spdx.json
> > > files (and their associated fingerprint and checksum files) should remain.
> >
> > Also, there is no JAR file in the
> >   commons-math-examples
> > folder on Nexus; is it OK to delete it entirely?
>
> I guess not: It is the parent of modules that may have artefacts.
> Ditto for "examples-kmeans" (no JAR, but parent of "examples-kmeans-image"
> that has a JAR).
>
> It is cleaner to have a separate module for each "mini-application" (which a
> user can then easily run).
> However if we have to perform this "manual" deletion of spurious file for each
> release), it will be much less error-prone to put all the examples in the same
> module (and use the "subcommand" feature of "picocli").

For the other multi-module projects we decided not to upload artifacts
to nexus. These jars have no binary compatibility commitment.

They are included using an 'examples' profile when you build the site.
But they should not be in the release profile. The latest release of
statistics, geometry, rng and numbers did not upload the examples to
Nexus. They would be in the source distribution only.

Also note that you may wish to delete some modules from the release.
For example, is the new ga module ready? Given this is a beta release
then this removal may not be necessary as it is not a final cut.

Alex

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to