Hi Elliotte,

Thank you for the feedback.

I understand your concern. I was approaching this primarily from the
perspective of improving cross-platform cache reuse, but I agree that
modifying or normalizing file contents during checksum calculation
introduces concerns around byte-for-byte reproducibility.

Your point about preserving the exact checked-in contents is important. I
don't want to introduce behaviour that compromises that principle.

I'll reconsider this direction and explore other areas of the Maven
ecosystem for a GSoC project.

Thank you for taking the time to review the idea.

Best regards,
Harsha

On Mon, Nov 16, 2026 at 7:21 PM Elliotte Rusty Harold <[email protected]>
wrote:

> On Mon, Nov 16, 2026 at 12:37 PM Harsha B <[email protected]>
> wrote:
> >
> > Hi everyone,
> >
> > I'm Harsha, a Computer Science Engineering student and a contributor to
> > Apache Maven. I'm planning to apply for GSoC 2027 and wanted to share an
> > idea early to get community feedback.
> >
> > The proposal: Configurable input normalization for cross-platform build
> > cache reuse.
> >
> > Current situation:
> >
> > The Maven Build Cache Extension calculates file hashes using raw bytes.
> > Consequently, the same source files checked out with CRLF line endings on
> > Windows and LF line endings on Linux can produce different cache keys,
> > preventing cache reuse.
> >
>
> This is not normalization. This is modification. In 2026 this feels
> very wrong. What's checked in is what should be checked out with no
> line ending normalization of any kind ever, not by git, not by maven.
> Everything should be byte per byte reproducible and platform
> independent.
>
> I don't know what git does, and we can't control that, but I don't
> want to add more line ending modification epicycles to Maven. I'm a
> big -1 on this proposal.
>
> --
> Elliotte Rusty Harold
> [email protected]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to