Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Votes and Staging Repo Expirations

Hi,
I'm not convinced that these Stagings will be expiring...  Specifically, I looked at Deployment.  Yes, the directory (https://oss.sonatype.org/content/repositories/staging/jakarta/enterprise/deploy/jakarta.enterprise.deploy-api/) itself has a timestamp of July 23, but the contents have newer timestamps (https://oss.sonatype.org/content/repositories/staging/jakarta/enterprise/deploy/jakarta.enterprise.deploy-api/1.7.3/).

And, we have other contents of the Staging repository that are much older than 30 days...  For example,
https://oss.sonatype.org/content/repositories/staging/jakarta/activation/jakarta.activation-api/1.2.1/
https://oss.sonatype.org/content/repositories/staging/jakarta/jws/jakarta.jws-api/1.1.1/

So, maybe the 30 day expiration gets reset everytime the Staging Repo gets touched?

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn:
https://www.linkedin.com/in/kevinwsutter



From:        David Blevins <dblevins@xxxxxxxxxxxxx>
To:        Bill Shannon <bill.shannon@xxxxxxxxxx>
Cc:        Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:        08/23/2019 05:19 PM
Subject:        [EXTERNAL] Re: [jakarta.ee-spec.committee] Votes and Staging Repo Expirations
Sent by:        jakarta.ee-spec.committee-bounces@xxxxxxxxxxx




Thanks, Bill.  I just asked that in the other thread.  No need to follow up.  Looks like if I get EJB up we have a small window to push a Jakarta EE API jar before deployment expires.

I'll be back shortly....


--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
310-633-3852

> On Aug 23, 2019, at 3:07 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
>
> jws is not part of Jakarta EE 8.
>
> The 2.1.0 version of jws-api was published Aug 22.
>
> David Blevins wrote on 8/23/19 2:54 PM:
>> I've just an exchange with Brian Fox whose CTO of Sonatype.  He confirms the ejb staged binaries were deleted due to expiration and they've had to start cracking down on the 30-day period due to starved resources.  I did not ask about the messy state of the staging repo overall.
>>
>> What this means for us is that we need new builds of:
>>
>> - jakarta.ejb-api
>> - jakarta.jws-api
>> - jakarta.enterprise.deploy-api
>>
>> The above are either gone already or will be gone by Monday.  If we do not get these up, there is no hope of a Jakarta EE 8 vote on Monday.
>>
>> I'll do EJB.  Kevin if you can redo jakarta.enterprise.deploy-api, that'd be awesome.
>>
>> That leaves us with jakarta.jws-api.  How will we get that one up?
>>
>>
>>

_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee





Back to the top