Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-build] Promoting a release to maven central?
Thanks! I did have a PR already to update the SNAPSHOT version - thanks for reminding me:

The other thing though was I was looking at the read only settings but then it struck me that I don't (even as project lead https://projects.eclipse.org/projects/ee4j.jta/who) have access to the settings on the repository - I will open a bugzilla for that thanks.

On Tue, 8 Jan 2019 at 16:12, Tomas Kraus <tomas.kraus@xxxxxxxxxx> wrote:

OK, great. :)

We are also doing few more steps on our projects:

1) merge release branch (1.3.2-RELEASE in your case) into EE4J_8 to have proper snapshot version there

2) set EE4J_8 as readonly - using obscure enough branch rule (attached)


Tomas

Dne 08.01.19 v 15:58 Tom Jenkinson napsal(a):

On Tue, 8 Jan 2019 at 10:56, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:
Great - thanks. I have executed it and will let you know when I see it in central :)

On Mon, 7 Jan 2019 at 21:27, Tomas Kraus <tomas.kraus@xxxxxxxxxx> wrote:

Hi Tom,

I already implemented and tested release on JSONP and JSONB API.

https://jenkins.eclipse.org/jsonp/job/nexus-staging/

https://jenkins.eclipse.org/jsonb/job/nexus-staging/

Will publish job content tomorrow on the wiki.


JTA project has also this nexus-staging job. I implemented missing release) case there:

  release)

    if [ "${RELEASE}" = 'true' ]; then
      if [ -n "${VERSION}" ]; then
        echo '-[ Releasing Nexus staging repository for JTA API ]-----------------------------'
        mvn -B ${NEXUS_PLUGIN_PARAMS} ${NEXUS_PLUGIN}:rc-release \
            -DstagingRepositoryId="${VERSION}"
      fi
    else
      echo '-[ Release confirmation was not selected ]--------------------------------------'
    fi
    ;;


You have 2 JTA deployments:

[INFO] jakartatransaction-1008 CLOSED   jakarta.transaction:jakarta.transaction-api:1.3.1
[INFO] jakartatransaction-1009 CLOSED   jakarta.transaction:jakarta.transaction-api:1.3.2

So for jakarta.transaction:jakarta.transaction-api:1.3.2 use those values in the form:

  • Branch: EE4J_8
  • Action: release
  • Version (Deployment ID): jakartatransaction-1009
  • Release: checked


Tomas

Dne 07.01.19 v 22:13 Tom Jenkinson napsal(a):
Thanks Bill!

On Mon, 7 Jan 2019 at 17:44, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
You need to use nexus-stagin:rc-release, as described at the end of my writeup.

Tom Jenkinson wrote on 1/7/19 8:21 AM:
Does anyone have some suggestion how to promote a release from staging into Maven central?

Thanks,
Tom

_______________________________________________
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



_______________________________________________
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
_______________________________________________
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

_______________________________________________
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
_______________________________________________
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