Hello.

Le mer. 14 déc. 2022 à 16:23, Alex Herbert <alex.d.herb...@gmail.com> a écrit :
>
> On Wed, 14 Dec 2022 at 13:31, Gilles Sadowski <gillese...@gmail.com> wrote:
> >
> > Le mer. 14 déc. 2022 à 09:09, Alex Herbert <alex.d.herb...@gmail.com> a 
> > écrit :
> > >
> > > On Wed, 14 Dec 2022 at 00:49, Gilles Sadowski <gillese...@gmail.com> 
> > > wrote:
> > > >
> > > > Hello.
> > > >
> > > > Next problem:
> > > > $ JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64 mvn -Duser.name=erans
> > > > clean deploy -Prelease
> > > > [...]
> > > >
> >
> > It is quite unexpected that a part of that command works without
> > providing the password (i.e. mvn uses the info in "~/.m2/settings.xml",
> > I guess), while another needs it to appear in clear-text on the command
> > line.  Is that the case?
>
> That is how I get it to work because my svn client will not cache my
> password for my username. So I have to provide it to the commons
> release plugin.

I was at step (11) of the CM "release howto" (not updated for a long
time, of course); in [RNG] the equivalent step is still referred to as
---CUT---
(11) Create and transfer the artifacts to the Nexus server (a.k.a. "deploy").
---CUT---
And I hadn't read further yet (hence the confusion with my vague memories
of upload to "nexus" and upload to "dist" server were independent), where
step (12) is replaced by additional functionality behind the scene (performed
by the "commons-release-plugin").

>
> As Gary stated, svn is used by the release plugin to copy the dist
> archives to (in this case):
>
> svn co https://dist.apache.org/repos/dist/dev/commons/math --depth immediates
>
> Since the directory exists the error must be when the release plugin
> is trying to remove all the items inside that directory and it does
> not have svn commit permissions to do so.

Thanks for confirming.
However, for the gain in simplicity, did we lose in security, by being
forced to provide the password (in clear-text), whereas the "svn" client
would handle the password securely (no echo).
Could this be caused by the "commons-release-plugin" assuming that
the "user.password" _must_ be defined (and passing an empty value
instead of letting "svn" prompt it from the user)?

Regards,
Gilles

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

Reply via email to