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

Support baseline replacement for all repositories with jar-signed content #30

Closed
merks opened this issue Dec 3, 2023 · 1 comment
Closed

Comments

@merks
Copy link
Contributor

merks commented Dec 3, 2023

These sites with jar-signed content should do baseline replacement:

This site does not need that because does not modify the direct-from-maven artifacts:

The aggregation consumes from the sites above so does not need special handling because it aggregates already-baseline-replaced content:

merks added a commit to eclipse-orbit/orbit-legacy that referenced this issue Dec 3, 2023
merks added a commit to eclipse-orbit/orbit-legacy that referenced this issue Dec 3, 2023
@merks
Copy link
Contributor Author

merks commented Dec 3, 2023

Initially each did a nightly build with a baseline replace of the corresponding latest release and now, going forward, each will do nightly/milestone builds with a baseline replace of the corresponding latest night build. As such, any new artifacts or modified artifacts will be produced once the first time by a nightly build and will be baseline replaced from that point on.

@merks merks closed this as completed Dec 3, 2023
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

No branches or pull requests

1 participant