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

adapting comparable_patch.sh to new signature of removeExcludedFiles #3995

Merged
merged 1 commit into from
Oct 17, 2024

Conversation

judovana
Copy link
Contributor

@judovana judovana commented Oct 14, 2024

Copy link
Contributor

@karianna karianna left a comment

Choose a reason for hiding this comment

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

Spelling / Grammar pass on the comment please.

@judovana
Copy link
Contributor Author

Thanx, I had found only one and half of small issue. hth

@@ -338,7 +338,8 @@ echo "Successfully removed all Signatures from ${JDK_DIR}"
removeExcludedFiles

# Needed due to vendor variation in jmod re-packing after signing, putting attributes in different order
processModuleInfo
# Comparable patch, as per read-me, requires java on path
processModuleInfo "${JDK_DIR}" "${OS}" "$(dirname "$(dirname "$(readlink -f "$(which java)")")")"
Copy link
Contributor

Choose a reason for hiding this comment

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

Using "which java" maybe ok, but wondering if we ought to take a "backup" at the start of the JDK being compared, thus ensuring the class_version is good enough for the "javap" processing. This would be similar as was done here:

Copy link
Contributor Author

@judovana judovana Oct 15, 2024

Choose a reason for hiding this comment

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

To make backup of jdk ok. My redundant top level wrapper and also the (probably) existing one are doing backup of jdk/allowing to set up 3rd jdk . So that is ok. Unluckily I have not seen the way to pass it into the comparable_patch.sh properly.

Comparable_patch.sh is clear, it needs java/javac on path. Whoever modifed processModuleInfo, have violated that.

Comparable patch should remain as it is, and should not be doing any backups of jdk. Thats the task for its wrappers to deal with it as it is appropriate.

There can be follow up on this set of patches, which will elaborate on usage of path by comaprable_patch, to add additional solution, but right now the comaprable_patch.sh is broken, and this path is fixing it.

@judovana
Copy link
Contributor Author

@karianna @andrew-m-leonard ping please? The codebase is currently dead without this. A better solution may be elaborated on the fly

Copy link
Contributor

@andrew-m-leonard andrew-m-leonard left a comment

Choose a reason for hiding this comment

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

yep lets get this in as is, thanks

@judovana
Copy link
Contributor Author

tyvm!

@judovana
Copy link
Contributor Author

/integrate

@karianna
Copy link
Contributor

rerunning the failed job

@karianna karianna merged commit eb6b68e into adoptium:master Oct 17, 2024
26 checks passed
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.

3 participants