Change to 3.10-SNAPSHOT #5096
Merged
Change to 3.10-SNAPSHOT #5096
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jodygarnett
force-pushed
the
3.10.x-snapshot-versions
branch
from
f7843e5
to
511bc9c
Compare
jodygarnett
force-pushed
the
3.10.x-snapshot-versions
branch
from
511bc9c
to
39602df
Compare
jodygarnett
force-pushed
the
3.10.x-snapshot-versions
branch
from
39602df
to
e67becf
Compare
This allows dependent projects to depend on the branch, without interruption each time a release is made. This change also double checks schema plugins produce a jar and zip as is already done on master
jodygarnett
force-pushed
the
3.10.x-snapshot-versions
branch
from
e67becf
to
4f601ad
Compare
|
I need to grab the release script changes for this pull request. |
# Conflicts: # update-version.sh # updateBranchVersions.sh # updateReleaseVersions.sh
josegar74
approved these changes
Jan 28, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 allows dependent projects to depend on the branch, without interruption each time a release is made.
This is especially useful for schema plugins referencing geonetwork via parent, and transitive dependencies.
See #5095
This change also double checks schema plugins produce a jar and zip as is already done on master
After this pull request the 3.10.6 release cycle looks like:
3.10.6-SNAPSHOT, schemas/pom.xml3.7, schema plugin parent reference3.7reference3.10.6-0, schemas/pom.xml3.7, schema plugin parent3.7reference3.10-SNAPSHOT, schemas/pom.xml3.10-SNAPSHOT, schema plugin parent3.10-SNAPSHOTosgeo snapshot repository reference3.10.7, schemas/pom.xml3.10.7, schema plugin parent3.10.7osgeo release repository reference3.10-SNAPSHOT, schemas/pom.xml3.10-SNAPSHOT, schema plugin parent3.10-SNAPSHOTosgeo snapshot repository referenceAs shown above schema plugin developers no longer have to change their
pom.xmlparent reference each time geonetwork releases. Indeed they only need to change when the schema plugin wishes to make a release.