-
Notifications
You must be signed in to change notification settings - Fork 89
Simplify publishToMaven.jenkinsfile #3035
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
merks
merged 1 commit into
eclipse-platform:master
from
merks:pr-simplify-publishToMaven
May 8, 2025
Merged
Simplify publishToMaven.jenkinsfile #3035
merks
merged 1 commit into
eclipse-platform:master
from
merks:pr-simplify-publishToMaven
May 8, 2025
Conversation
This file contains hidden or 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
- There is no need to filter out wanted content because the aggregator only aggregates what we want to publish. - There is no need to enrich the poms because the aggregator creates poms the meet the nexus publishing requirements and tests that the poms do actually conform. - There is no need to create javadoc stubs because the aggregator generates one (for every artifact with a corresponding `sources.jar`. - There is no need to recompute checksums because nothing is modified.
Contributor
Author
|
Has no build impact. |
HannesWell
added a commit
to HannesWell/eclipse.platform.releng.aggregator
that referenced
this pull request
May 8, 2025
And downgrade the JDK used in the publishToMaven Jenkins pipeline as we don't need the latest Java-22/23 features anymore, i.e. the ability to launch multi-file source-code programs. Follow-up on - eclipse-platform#3035
Member
|
Thanks a lot @merks for this work. It's really great to see how the publication to Maven-Central becomes easier and easier! Regarding the points you mentioned I just wanted to record that they are not necessary anymore, due your enhancements in respectively in the CBI aggregator. |
HannesWell
added a commit
to HannesWell/eclipse.platform.releng.aggregator
that referenced
this pull request
May 9, 2025
And downgrade the JDK used in the publishToMaven Jenkins pipeline as we don't need the latest Java-22/23 features anymore, i.e. the ability to launch multi-file source-code programs. Follow-up on - eclipse-platform#3035
HannesWell
added a commit
to HannesWell/eclipse.platform.releng.aggregator
that referenced
this pull request
May 9, 2025
And downgrade the JDK used in the publishToMaven Jenkins pipeline as we don't need the latest Java-22/23 features anymore, i.e. the ability to launch multi-file source-code programs. Follow-up on - eclipse-platform#3035
HannesWell
added a commit
to HannesWell/eclipse.platform.releng.aggregator
that referenced
this pull request
May 9, 2025
And downgrade the JDK used in the publishToMaven Jenkins pipeline as we don't need the latest Java-22/23 features anymore, i.e. the ability to launch multi-file source-code programs. Follow-up on - eclipse-platform#3035
HannesWell
added a commit
to HannesWell/eclipse.platform.releng.aggregator
that referenced
this pull request
May 9, 2025
And downgrade the JDK used in the publishToMaven Jenkins pipeline as we don't need the latest Java-22/23 features anymore, i.e. the ability to launch multi-file source-code programs. Follow-up on - eclipse-platform#3035
HannesWell
added a commit
to HannesWell/eclipse.platform.releng.aggregator
that referenced
this pull request
May 9, 2025
And downgrade the JDK used in the publishToMaven Jenkins pipeline as we don't need the latest Java-22/23 features anymore, i.e. the ability to launch multi-file source-code programs. Follow-up on - eclipse-platform#3035
HannesWell
added a commit
that referenced
this pull request
May 9, 2025
And downgrade the JDK used in the publishToMaven Jenkins pipeline as we don't need the latest Java-22/23 features anymore, i.e. the ability to launch multi-file source-code programs. Follow-up on - #3035
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.
sources.jar.