You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by Guillaume Nodet <gn...@apache.org> on 2024/06/19 19:55:16 UTC
Missing source files for SSHD 2.13.0 release
During the release, I experienced a problem when trying to close the
staging repository. One of the signature was wrong and nexus did not want
to close the repository. I ended up bypassing the usual release process
(mvn release:perform) and did a manual deploy. Unfortunately, I forgot to
build the source jars, so none of the jar has an associated source jar in
maven central.
The problem should have been fixed by my last commit [1]. I don't think
there's a way to deploy just the source jars, so should I cut a 2.13.1
release ?
Cheers,
Guillaume Nodet
[1]
https://github.com/apache/mina-sshd/commit/50d1d9fd2f4d21a22f8eb978a2e4f47c1349e5bb
Re: Missing source files for SSHD 2.13.0 release
Posted by Guillaume Nodet <gn...@apache.org>.
Le jeu. 20 juin 2024 à 17:54, Emmanuel Lécharny <el...@gmail.com> a
écrit :
> Can't you just cancel the 2.13.1 and redo the exact same release?
>
2.13.0 has been published to maven central. That's how someone saw the
problem, after being synced to central.
So I need to do a 2.13.1.
> In any case, your commit is not a code commit, so voting the release can
> be quickly done (maybe asking for a 24h vote instead of 3days could help).
>
Yeah, good idea. I'll try to do that asap.
Guillaume
>
>
> On 19/06/2024 21:55, Guillaume Nodet wrote:
> > During the release, I experienced a problem when trying to close the
> > staging repository. One of the signature was wrong and nexus did not want
> > to close the repository. I ended up bypassing the usual release process
> > (mvn release:perform) and did a manual deploy. Unfortunately, I forgot
> to
> > build the source jars, so none of the jar has an associated source jar in
> > maven central.
> >
> > The problem should have been fixed by my last commit [1]. I don't think
> > there's a way to deploy just the source jars, so should I cut a 2.13.1
> > release ?
> >
> > Cheers,
> > Guillaume Nodet
> >
> > [1]
> >
> https://github.com/apache/mina-sshd/commit/50d1d9fd2f4d21a22f8eb978a2e4f47c1349e5bb
> >
>
> --
> *Emmanuel Lécharny* P. +33 (0)6 08 33 32 61
> elecharny@apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
> For additional commands, e-mail: dev-help@mina.apache.org
>
>
--
------------------------
Guillaume Nodet
Re: Missing source files for SSHD 2.13.0 release
Posted by Emmanuel Lécharny <el...@gmail.com>.
Can't you just cancel the 2.13.1 and redo the exact same release?
In any case, your commit is not a code commit, so voting the release can
be quickly done (maybe asking for a 24h vote instead of 3days could help).
On 19/06/2024 21:55, Guillaume Nodet wrote:
> During the release, I experienced a problem when trying to close the
> staging repository. One of the signature was wrong and nexus did not want
> to close the repository. I ended up bypassing the usual release process
> (mvn release:perform) and did a manual deploy. Unfortunately, I forgot to
> build the source jars, so none of the jar has an associated source jar in
> maven central.
>
> The problem should have been fixed by my last commit [1]. I don't think
> there's a way to deploy just the source jars, so should I cut a 2.13.1
> release ?
>
> Cheers,
> Guillaume Nodet
>
> [1]
> https://github.com/apache/mina-sshd/commit/50d1d9fd2f4d21a22f8eb978a2e4f47c1349e5bb
>
--
*Emmanuel Lécharny* P. +33 (0)6 08 33 32 61
elecharny@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For additional commands, e-mail: dev-help@mina.apache.org