Romain is not a member of the orb-dev list. Forwarding his
correction/reply.
-------- Forwarded Message --------
This has nothing to do with Maven.
The master branch is protected so the process implemented by the
release scripts do not update the branch.
Instead they create a branch with the next version update to be
merged back with a PR.
On 4/24/19 4:16 PM, Ed Bratt wrote:
+ Romain (our Maven release expert)
Romain,
Could you confirm that we're doing this properly?
Thanks,
-- Ed
On 4/24/2019 11:06 AM, Russell Gold
wrote:
That seems to be the result of the way the Jenkins job does
it. You’ll see https://search.maven.org/search?q=a:glassfish-corba
to show 4.2.1
but the release process doesn’t update the
master branch poms. That has to be done separately.
Russ Gold
Hi,
We
have a 4.2.1 release tagged on GitHub however
master is still showing 4.2.1-SNAPSHOT.
Are
we wanting to do an ORB release soon?
If
so I can kick off the Eclipse release process and
will need a description of what is in it. JDK 11
compatibility(?)
What
steps do we need to do to get a 4.2.1 over the
line?
Stephen Millidge
_______________________________________________
orb-dev mailing list
orb-dev@xxxxxxxxxxx
To change your delivery options, retrieve
your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/orb-dev
_______________________________________________
orb-dev mailing list
orb-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/orb-dev
