Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] [jakartaee-spec-project-leads] PR for org.eclipse.ee4j:project pom

It looks like OSSRH has resolved the issues with the cdi staging repo.  Should this PR just be closed now?

FYI, for future reference, the Jenkins build for doing the EE4J parent pom build is here:

Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    

From:        Scott Stark <starksm64@xxxxxxxxx>
To:        JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>
Cc:        Jakarta specification disccusions <>
Date:        08/07/2019 12:21 PM
Subject:        [EXTERNAL] [jakartaee-spec-project-leads] PR for org.eclipse.ee4j:project pom
Sent by:        jakartaee-spec-project-leads-bounces@xxxxxxxxxxx

The following PR:

Updates the staging profile to include a workaround for the current jakarta.enterprise:jakarta.enterprise.cdi-api staging ssue by adding the staging repository that exists after the current global staging repository.

Spec projects that depend on the cdi-api could update their parent pom reference to:
Once this has been merged and released to be able to build against the current staged 2.0.2 cdi-api release.

Speaking of releasing, I’m not seeing which CI does this build. Can someone who know where this is merge and release this and let the leads list know.

jakartaee-spec-project-leads mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top