| I think we should submit one Sonatype issue for all EE4J projects and it should come from Eclipse because Eclipse owns Sonatype accounts. It will save a lot of time coordinating it. 
 — Dmitry 
 Hi,I've checked the Nexus UI at https://oss.sonatype.org, but did not findany related settings.There is no need to go through webmaster (initially). The project canopen a ticket at OSSRH. If it's a general setting, we can certainlycomment to have this fixed for all projects.Regards,FredOn 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-- Frederic GurrRelease Engineer | Eclipse Foundation Europe GmbHAnnastr. 46, D-64673 ZwingenbergHandelsregister: Darmstadt HRB 92821Managing Directors: Ralph Mueller, Mike Milinkovich, Chris Laroque_______________________________________________ee4j-build mailing listee4j-build@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://www.eclipse.org/mailman/listinfo/ee4j-buildsuggesting 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
 
 
 |