Re: [openmq-dev] Staging 6.0.0 (final)?

[arjan tijms <arjan.tijms@xxxxxxxxx>]

Hi,

On Wed, Dec 2, 2020 at 9:45 PM Piotr Żygieło <piotr@xxxxxxxxxx> wrote:

1. This job seems to be not parameterized - and its role is to promote everything that is currently staged. Does it mean IF it runs - all versions visible at https://jakarta.oss.sonatype.org/content/repositories/staging/org/glassfish/mq/mq-distribution/ - including M1, 2, 3 and RC1, 2, 3 would be released - if not dropped?

There's a description in the job that asks to just page the staging ID in the script, but all the newer versions of the script use a parameter. I just changed it to that.

The staging repository ID is picked up from the output of the first job, or if that is gone you can use the "list first" option to see it again.

Last output of first job:

[INFO] Performing remote staging...

[INFO] 

[INFO]  * Remote staging into staging profile ID "839cdc981d257"

[INFO]  * Created staging repository with ID "orgglassfishmq-1006".

[INFO]  * Staging repository at https://jakarta.oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgglassfishmq-1006

[INFO]  * Uploading locally staged artifacts to profile org.glassfish.mq

[INFO]  * Upload of locally staged artifacts finished.

[INFO]  * Closing staging repository with ID "orgglassfishmq-1006".

 

2.There is some pom.xml created on the fly in the 3_... job.

I'm not 100% sure who added that, but let's remove it. Then you always have the exact version of everything that the project has configured.

Btw we have the green light to release when we want: https://bugs.eclipse.org/bugs/show_bug.cgi?id=569005

That green light obviously doesn't take the availability of HK2 in Maven Central in account, but when that's there we can release OpenMQ.

Kind regards,

Arjan Tijms