[3.0] Maven/Nightly build fix - bundle names change #1183
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is fix for issue related with eclipselink-plugins.zip bundle.
Main purpose of this fix is to keep names of the
orc.eclipse.persistence
artifacts packed ineclipselink-plugins.zip
bundle consistent with older versions of the EclipseLink.EclipseLink artifacts in eclipselink-plugins-*.zip are named in the same way as in 2.6, 2.7 bundles
e.g.
org.eclipse.persistence.core_2.7.9.v20210604-2c549e2208.jar
xorg.eclipse.persistence.core_3.0.2.v20210610-1fda5b4d4e.jar
MANIFEST.MF
content is changed too.Bundle-Version
containsmajor.minor.micro.version.vYYYYMMDDHHmm
e.g.Bundle-Version: 3.0.2.v202106101448
plus new additional properties e.g.
Some note about bundles at Eclipse.org lifecycle.
These bundles available at
https://www.eclipse.org/eclipselink/downloads/nightly.php
https://www.eclipse.org/eclipselink/downloads/milestones.php
https://www.eclipse.org/eclipselink/downloads/
are build during a nightly build.
During promotion/release process are generated just Maven artifacts published at
https://jakarta.oss.sonatype.org/content/groups/staging/org/eclipse/persistence/eclipselink/2.7.9/
and later
in the Maven Central.
Bundles at Eclipse.org are just copied from Nightly to Milestones (e.g. RC1, MP1, ...) and Download (Final).
This is reason why timestamp stored in bundles at Eclipse.org is usually older, than timestamp in artifacts stored in Maven Central.
How to verify/test it without Jenkins environment (nightly build job):
mvn clean install -DskipTests
TEST_SUMMARY_SRC
,ECLIPSELINK_PROJECT
inpopulateTestResultsHTML.sh
and execute it to create requiredtest-summary.html
files. Without this step next one fails.mvn verify -pl :org.eclipse.persistence.nightly -P test-lrg
<EL_PROJECT>/bundles/nightly/target
populateTestResultsHTML.tar.gz
Signed-off-by: Radek Felcman radek.felcman@oracle.com