Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-build] Wrong release in staging

This is the main reason we used the promoted repo group of maven.java.net for GlassFish.
i.e it's another repo group in the nexus workflow.

This most useful when doing new versions of final API artifacts.
Unfortunately that's not available in oss.sonatype.org

On Fri, Nov 2, 2018 at 8:25 AM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:
Hi,

On Fri, Nov 2, 2018 at 3:22 PM Lukas Jungmann <lukas.jungmann@xxxxxxxxxx> wrote:
depends on what one tells the job to do... 

Yes, about that, I "hoped" (but in vain, I guess), that the job didn't have enough power/access to actually release. E.g. that at most it could stage and prompt to close/release, but that actually synching to Maven central would still be a manual step.

in case of jpa-api, the "bug" has been already identified and fixed[1]

Unfortunately, the diff is protected. When logged-in I get: "No permission to view config history".

Can you post the diff here if possible? Might be good for all of us to learn from.
 
and have good understanding of
what, when and why they do what is written in them, you should be safe...

Yeah, I guess ;) But I have a sinking feeling most everybody is walking a little in the dark here, copied the scripts from the wiki and just prayed they worked.

Kind regards,
Arjan


_______________________________________________
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

Back to the top