Skip to content

Conversation

homberghp
Copy link
Contributor

Not all jar files appear to have a pom.properties file with Maven coordinates. Making up maven coordinates for such cases is unsafe (just guessing), so accept the jar file name if no maven coordinates exist

This modified CheckEmbeddedBinaries adds an optional column the 'manifest file'
with the value of the jar file for which the checksum is to be computed.

Other changes have to do with keeping order of manifest file and order of processing the same.


^Add meaningful description above

Click to collapse/expand PR instructions

By opening a pull request you confirm that, unless explicitly stated otherwise, the changes -

  • are all your own work, and you have the right to contribute them.
  • are contributed solely under the terms and conditions of the Apache License 2.0 (see section 5 of the license for more information).

Please make sure (eg. git log) that all commits have a valid name and email address for you in the Author field.

If you're a first time contributor, see the Contributing guidelines for more information.

If you're a committer, please label the PR before pressing "Create pull request" so that the right test jobs can run.

PR approval and merge checklist:

  1. Was this PR correctly labeled, did the right tests run? When did they run?
  2. Is this PR squashed?
  3. Are author name / email address correct? Are co-authors correctly listed? Do the commit messages need updates?
  4. Does the PR title and description still fit after the Nth iteration? Is the description sufficient to appear in the release notes?

If this PR targets the delivery branch: don't merge. (full wiki article)

Not all jar files appear to have a pom.properties file with
maven coordinates. Making up maven coordinates for such cases is unsafe
(just guessing), so accept the jar file name if no maven coordinates
exist
Copy link
Contributor

@matthiasblaesing matthiasblaesing left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the intention here? I don't get the problem that is being solved with this PR.

The task CheckEmbeddedBinaries is only ever invoked by the build of java/maven.embedded. It is part of the infrastructure that allows to resolve maven coordinates from SHA1 values of the corresponding JARs. It seems this option is currently being unused.

The task to check if the list contains the right binaries is IMHO correctly implemented. java/maven.embedder/external/binariesembedded-list is slit into pairs of SHA1 sum and maven coordinate. Then each jar inside apache-maven-<version>.zip is checked if it is in the list and matches the checksum.

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