You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran the scripts on a CentOS 6.5 VM built from the "minimal.iso".
This revealed that the "patch" RPM is also a prerequisite to success in addition to "git", "wget", "unzip", and a Java installation.
Also, your script does not detect that the patch command is missing, skips over applying the patches, and goes ahead and launches the Maven build.
A useful comment to add to the readme would be a hint to do a "tail -f ./eap-build/work/build.log" once the script launches the Maven build. Otherwise, many minutes of quiet anticipation ensue.
Suggestion for enhancement: It would be great if one could specify both the baseline version of EAP as well as a specific full path to the patch file. In my case, I'm editing the patch file to advance to the most recent minor version of the patched dependencies instead of falling back to the last closest. Since I don't know what Redhat is hiding and what we are missing, figured there is a chance that upstream of those dependencies contain the fixes in later versions.
The text was updated successfully, but these errors were encountered:
Thanks for your work!
I ran the scripts on a CentOS 6.5 VM built from the "minimal.iso".
This revealed that the "patch" RPM is also a prerequisite to success in addition to "git", "wget", "unzip", and a Java installation.
Also, your script does not detect that the patch command is missing, skips over applying the patches, and goes ahead and launches the Maven build.
A useful comment to add to the readme would be a hint to do a "tail -f ./eap-build/work/build.log" once the script launches the Maven build. Otherwise, many minutes of quiet anticipation ensue.
Suggestion for enhancement: It would be great if one could specify both the baseline version of EAP as well as a specific full path to the patch file. In my case, I'm editing the patch file to advance to the most recent minor version of the patched dependencies instead of falling back to the last closest. Since I don't know what Redhat is hiding and what we are missing, figured there is a chance that upstream of those dependencies contain the fixes in later versions.
The text was updated successfully, but these errors were encountered: