[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ee4j-build] Script to compare and verify GlassFish modules
|
On 11/27/18 5:49 AM, Tomas Kraus wrote:
OK, it's available on
https://wiki.eclipse.org/JakartaEE_GlassFish_Modules_Check_Script
Added BSD License header.
Romain: Maybe you can use it in GF jobs to see whether new integragted
artifacts are matching those rules.
Feel free to raise a PR, GF is using a declarative pipeline that is in
the repository (/Jenkinsfile).
What's "multi-release setup".
Tomas
Dne 27.11.18 v 2:06 Bill Shannon napsal(a):
Interesting, thanks!
I suppose the wiki is as good a place as any to put this.
Care to share the output? How are we doing with the latest builds? :-)
Tomas Kraus wrote on 11/22/18 08:29 AM:
Hi All,
I made this script for our team to compare content of Oracle
Glassfish and new
JakartaEE Glassfish modules directory.
<old_path> :: Oracle GlassFish, e.g.
/some/oracle/glassfish4/glassfish/modules
<new_path>:: Jakarta EE GlassFish, e.g.
/some/jakartaee/glassfish4/glassfish/modules
Usage: check.sh [-jlnmv] <old_path> <new_path>
<old_path> :: Path to directory containing old jars
<new_path> :: Path to directory containing new jars
-j :: Check whether class files were built for proper Java platform
-l :: Check whether archives in <new_path> contain LICENSE file
-n :: Check whether archives in <new_path> contain NOTICE file
-m :: Check whether archives in <new_path> contain proper
multirelease setup
-v :: Verbose output
Maybe it will help to someone.
Also, should this be uploaded to Eclipse wiki too?
Tomas
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build
