Skip to content
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

[Build] Remove unused creation of missing sources in Maven publication #2732

Conversation

HannesWell
Copy link
Member

Since eclipse-platform/eclipse.platform.releng#126 respectively eclipse-platform/eclipse.platform.releng#167 no missing source artifacts are created anymore so the associated part of the CBIaggregator.sh script can be cleaned-up.

@merks @akurtakov or @mickaelistria or do you think that this could be useful again one day?

Since [1] respectively [2] no missing source artifacts are created
anymore so the associated part of the CBIaggregator.sh script can be
cleaned-up.

[1] - eclipse-platform/eclipse.platform.releng#126
[2] - eclipse-platform/eclipse.platform.releng#167
@akurtakov
Copy link
Member

IMO Maven publication should not generate sources and if a missing source case arise it should be handled in build scripts and not in publishing.

@merks
Copy link
Contributor

merks commented Jan 7, 2025

Maybe this was used for ecj in the past...

I would hope we'd never need this again...

@laeubi
Copy link
Contributor

laeubi commented Jan 7, 2025

IMO Maven publication should not generate sources and if a missing source case arise it should be handled in build scripts and not in publishing.

Just wanted to mention that sources are a requirement for maven-central publication, and the recommendation is to generate a fake artifact for the cases where no source can be given.

@merks
Copy link
Contributor

merks commented Jan 7, 2025

Yes, it's a requirement, unless you are Apache and then you can dump your open source binaries without your open source source. 😱

@HannesWell
Copy link
Member Author

HannesWell commented Jan 7, 2025

IMO Maven publication should not generate sources and if a missing source case arise it should be handled in build scripts and not in publishing.

Just wanted to mention that sources are a requirement for maven-central publication, and the recommendation is to generate a fake artifact for the cases where no source can be given.

Yes and that's also done for javadoc-artifacts where a note is added that references the doc bundles respectively the help.
The part to be removed is different as it creates a source-artifact with real sources it downloads from the git-repo.

But it's not used nowadays and as Ed said, hopefully won't be necessary in the future. Therefore I continue with the deletion.
Thanks for your feedback.

@HannesWell HannesWell merged commit 76458c5 into eclipse-platform:master Jan 7, 2025
4 checks passed
@HannesWell HannesWell deleted the maven-publication-remove-source-creation branch January 7, 2025 23:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants