Re: [ee4j-build] Artifact deleted from staging

[Romain Grecourt <romain.grecourt@xxxxxxxxxx>]

I got the same answer from Joel directly.
Also asked if we could extend the retention period for EE4J staging 
repositories.

If not, we should perhaps think of transferring maven.java.net to eclipse.
This would give you (eclipse infra) admin access, and would provide more 
control.
It would also give us the "promoted" feature that is not available in OSSRH.

On 11/19/18 10:43 AM, Frederic Gurr wrote:
> Hi,
>
> Digging through the OSSRH JIRA revealed the following similar issues:
>
> https://issues.sonatype.org/browse/OSSRH-43184
> =>
>    * Open staging repositories are dropped after 7 days of inactivity.
>    * Closed staging repositories are dropped after 14 days of inactivity.
>    * Released staging repositories are dropped immediately, since their
>      contents would be available in the Releases repo.
>
> https://issues.sonatype.org/browse/OSSRH-14887
> =>
> "Note that deploying with the Nexus Staging Maven plugin or Ant tasks
> will, by default, automatically attempt to close the staging repository
> upon deployment and can be used to release the staging repository from
> the command line as well. This allows you to avoid logging into the
> OSSRH user interface altogether. More details can be found in the Maven
> and Ant sections of this guide."
>
> HTH,
>
> Fred
>
> On 19.11.18 11:48, Frederic Gurr wrote:
> > Hi,
> >
> > I've checked the Nexus UI at https://oss.sonatype.org, but did not find
> > any related settings.
> >
> > There is no need to go through webmaster (initially). The project can
> > open a ticket at OSSRH. If it's a general setting, we can certainly
> > comment to have this fixed for all projects.
> >
> > Regards,
> >
> > Fred
> >
> > On 18.11.18 10:43, Dmitry Kornilov wrote:
> > > It's not the first time it happend. We've already seen it with jaf. I am
> > > suggesting Eclipse webmasters to get in touch with Sonatype team about
> > > this issue. If they have some deleting tasks scheduled we want it to be
> > > disabled for our artifacts.
> > >
> > > -- Dmitry
> > >
> > > 18 нояб. 2018 г., в 6:33, Stuart Douglas <sdouglas@xxxxxxxxxx
> > > <mailto:sdouglas@xxxxxxxxxx>> написал(а):
> > >
> > > > Hi Everyone,
> > > >
> > > > I had a staged Servlet 4.0.2 release ready to go, but it appears to
> > > > have disappeared from the staging repo.
> > > >
> > > > It was definitely staged as it was visible under:
> > > >
> > > > https://oss.sonatype.org/content/repositories/staging/jakarta/servlet/
> > > >
> > > > Looking at our Jenkins instance we do not have a job set up to delete
> > > > the repo, and no jobs that modify the staging repo have been run in
> > > > the last 2 weeks.
> > > >
> > > > Is there a time limit on how long an artifact can stay in the staging
> > > > repo? If there is no time limit then I was wondering how fine grained
> > > > the staging repo permissions are, i.e. could a bug in another projects
> > > > Jenkins script drop our staging repo? If neither of these options
> > > > is possible does anyone have any other idea what could have happened?
> > > >
> > > > Stuart
> > > >
> > > >
> > > > _______________________________________________
> > > > ee4j-build mailing list
> > > > ee4j-build@xxxxxxxxxxx <mailto:ee4j-build@xxxxxxxxxxx>
> > > > To change your delivery options, retrieve your password, or
> > > > unsubscribe from this list, visit
> > > > https://www.eclipse.org/mailman/listinfo/ee4j-build
> > > _______________________________________________
> > > ee4j-build mailing list
> > > ee4j-build@xxxxxxxxxxx
> > > To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> > > https://www.eclipse.org/mailman/listinfo/ee4j-build