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

Remove non-reproducible Implementation-Build-Date manifest entry #55

Merged
merged 1 commit into from
Sep 27, 2022
Merged

Conversation

@cowtowncoder
Copy link
Member

cowtowncoder commented Sep 26, 2022

@hboutemy Do these need to be removed since they break RB? (I assume so, just checking)

Do you think there is any downside? Is there equivalent metadata to indicate build time, or is that just... unavoidable loss? I don't know if tooling cares about that, and I guess artifacts still have external timestamps.

@cowtowncoder
Copy link
Member

I guess it's fine, how about I'll just merge this.

@cowtowncoder cowtowncoder merged commit 11deb4a into FasterXML:master Sep 27, 2022
@cowtowncoder cowtowncoder changed the title remove non-reproducible Implementation-Build-Date Remove non-reproducible Implementation-Build-Date manifest entry Sep 27, 2022
@cowtowncoder cowtowncoder added this to the 48 milestone Sep 27, 2022
@cowtowncoder
Copy link
Member

@hboutemy I think that Reproducible build somehow caused this:

FasterXML/jackson-databind#3680

which is peculiar in that all class files do have consistent timestamp, but one that is neither one specified in Maven property NOR epoch (but 10 years later). WDYT?

@cowtowncoder
Copy link
Member

This sounds quite familiar: open-telemetry/opentelemetry-java-instrumentation#2517

@hboutemy
Copy link
Contributor Author

I answered on FasterXML/jackson-databind#3680

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.

2 participants