Re: [el-dev] Tagging RC2

[<Hussain.NM@xxxxxxxxxxxxx>]

Mark,

In the api jar, the MANIFEST.MF has Bundle-Version as 4.0.0.SNAPSHOT.
In the Javadoc jar,
- the package summary still reads Jakarta Expression Language 3.0
- the footer is incorrect and still reads
Copyright © 2017–2020 Eclipse Foundation. All rights reserved.

I do not see the need to publish the el-parent. From what I see it just aggregates the project modules. Can it be used in dependency management or something?

I understand your goal is to be able to tag a specific commit for all sub-projects with same version. This will become difficult to maintain. The api and impl will not have simultaneous releases always. For e.g., the api and spec might be in version 4.0.0 and 4.0 respectively and you might need to release impl with version 4.0.1. In this case the parent will be updated to 4.0.1 too.

Even I attempted to clean up the pom in ejb-api[1]. The best solution I have come up is to tag the sub-projects with an individual identifier api-4.0.0-RELEASE, spec-4.0-FINAL

[1] https://github.com/hussainnm/ejb-api/tree/cleanup-pom

Thanks
Hussain
-----Original Message-----
From: el-dev-bounces@xxxxxxxxxxx <el-dev-bounces@xxxxxxxxxxx> On Behalf Of Mark Thomas
Sent: Wednesday, June 10, 2020 2:25 AM
To: el-dev@xxxxxxxxxxx
Subject: Re: [el-dev] Tagging RC2

[External]


On 09/06/2020 20:55, Mark Thomas wrote:

<snip/>

> On the positive side, once I have this figured out with EL, it will be
> easy to update the other projects to do the same.

Woot!

https://jakarta.oss.sonatype.org/content/groups/staging/jakarta/el/el-parent/4.0.0-RC2/

https://jakarta.oss.sonatype.org/content/groups/staging/jakarta/el/jakarta.el-api/4.0.0-RC2/

https://jakarta.oss.sonatype.org/content/groups/staging/org/glassfish/jakarta.el/4.0.0-RC2/

These are staged but not yet published.

I'd appreciate additional eyes on this before I hit the publish button.

Mark

This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.