Got it. I will explain my plan first. First, I will write a maven-plugin today. The maven plugin can accept two parameters, one be repo git url, the other be test codes relatice dir. When the plugin invoke (at phase prepare-test-source), it will use jgit to clone the repo you set, and copy its test files into generated-test-sources folder. Then all tests in that repo will invoke one by one. After that, I will write an repo (named commons-crypto-test or something) and use that plugin, and use commons-crypto's snapshot as dependency. After that, I will write a set of github actions to run this repo's build.
Will this help? Gary Gregory <garydgreg...@gmail.com> 于2020年8月23日周日 下午10:40写道： > The Apache snapshot repository is here: > https://repository.apache.org/snapshots/ > You just need a repository entry in your POM pointing to it in order for > Maven to resolve versions postfixed with "-SNAPSHOT". > > Gary > > On Sun, Aug 23, 2020 at 10:31 AM Xeno Amess <xenoam...@gmail.com> wrote: > > > Hi Gary. > > Where is the snapshot jar? > > Is it at oss snapshot center? > > If so, then I will have a very, very tricky way to test it, > > and that test is reusable. > > > > > > Gary Gregory <garydgreg...@gmail.com> 于2020年8月23日周日 下午9:53写道： > > > > > Building the binaries can be tricky, be warned. > > > > > > The trickiest to validate are aarch64, arm, and artmhf. All help is > > welcome > > > of course. > > > > > > A smoke test would be to make sure that the native code from the > SNAPSHOT > > > jar from our SNAPSHOT repo can be loaded, for example, by calling from > > the > > > command line the class org.apache.commons.crypto.Crypto > > > > > > For example, on: > > > > > > Linux dfd13586af7a 4.19.76-linuxkit #1 SMP Tue May 26 11:42:35 UTC 2020 > > > x86_64 x86_64 x86_64 GNU/Linux > > > > > > java -cp target/classes org.apache.commons.crypto.Crypto > > > > > > should output: > > > > > > Apache Commons Crypto 1.1.0-SNAPSHOT > > > Native code loaded OK: 1.1.0-SNAPSHOT > > > Native name: Apache Commons Crypto > > > Native built: Aug 23 2020 > > > OpenSSL library loaded OK, version: 0x1000106f > > > OpenSSL library info: OpenSSL 1.0.1f 6 Jan 2014 > > > Random instance created OK: > > > org.apache.commons.crypto.random.OpenSslCryptoRandom@355da254 > > > Cipher instance created OK: > > > org.apache.commons.crypto.cipher.OpenSslCipher@6ff3c5b5 > > > Additional OpenSSL_version(n) details: > > > 1: not available > > > 2: compiler: cc -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT > > > -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -DL_ENDIAN -DTERMIO -g -O2 > > > -fstack-protector --param=ssp-buffer-size=4 -Wformat > > > -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions > > > -Wl,-z,relro -Wa,--noexecstack -Wall -DMD32_REG_T=int > -DOPENSSL_IA32_SSE2 > > > -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m > > > -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM > > > -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM > > > 3: built on: Tue Dec 4 20:09:18 UTC 2018 > > > 4: platform: debian-amd64 > > > 5: OPENSSLDIR: "/usr/lib/ssl" > > > > > > Gary > > > > > > On Sun, Aug 23, 2020 at 2:23 AM Bruno P. Kinoshita <ki...@apache.org> > > > wrote: > > > > > > > Hi Gary, > > > > > > > > I might be able to test on Win64 and Linux64 this week. You mentioned > > > > snapshots… what is the easiest way to test them? Run some code using > > the > > > > code of the snapshots, or perhaps run the build+tests from a > > tag/commit? > > > > > > > > > > > > Cheers > > > > Bruno > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sunday, 23 August 2020, 11:49:21 am NZST, Gary Gregory < > > > > garydgreg...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > > > > > Hi all, > > > > > > > > I intent on creating a release candidate for Commons Crypto soon. > > > > > > > > I pushed a snapshot today which contains native binaries for Windows > 32 > > > and > > > > 64, Linux 32 and 64, Mac 64, and ARM and ARM HF. > > > > > > > > Please help testing these on whatever platforms you may have access > to. > > > > > > > > Gary > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > >
