@Gary Gregory <garydgreg...@gmail.com> Hi. I done it at https://github.com/XenoAmess/commons-crypto-smoke-test Please have a look.
> I don't quite see how but I am obviously not comprehending your plan. Then I will explain it again :) Step 1, I wrote a maven-plugin, whose usage is to copy tests from another repo when build. That plugin is released at https://github.com/XenoAmess/add-from-repo-maven-plugin btw. Step 2, I wrote a repo, who have nothing in src, and have Apache Commons Crypto 1.1.0-SNAPSHOT as dependency. And this repo use that plugin I wrote in step 1, to force copy all test codes directly from Crypto's git repo. Notice that only copy tests(src/test), no sources(src/main), means this repo do not build any sources, but only invoke tests upon original jars. Well I do think, if all tests in original lib (Commons Crypto) CAN pass, then we can say that it works correctly in this platform. (If I be wrong you can just tell me what examinations we need to add, and I will add them) Step 3, I wrote github actions to make this repo we made in Step 2, to make this repo run on windows, macos, and ubuntu. And the result is all pass. Is this explanation better? I'm not very good at English, sorry if I made some mistakes. Gary Gregory <garydgreg...@gmail.com> 于2020年8月23日周日 下午11:18写道： > I wondering if anyone can confirm the following issue and/or help explain > it, on MacOS 10.15.6 with OpenSSL 1.1.1g, running: > > mvn package > > then: > > java -Xdiag -Xcheck:jni -cp target/classes > -Dcommons.crypto.lib.tempdir=target/ org.apache.commons.crypto.Crypto > WARNING in native method: JNI call made without checking exceptions when > required to from CallStaticObjectMethod > WARNING in native method: JNI call made without checking exceptions when > required to from CallObjectMethod > Apache Commons Crypto 1.1.0-SNAPSHOT > Native code loaded OK: 1.1.0-SNAPSHOT > Native name: Apache Commons Crypto > Native built: Aug 22 2020 > Exception in thread "main" java.lang.UnsatisfiedLinkError: OpenSSL_version > at org.apache.commons.crypto.OpenSslInfoNative.OpenSSL(Native Method) > at org.apache.commons.crypto.Crypto.main(Crypto.java:144) > > I wonder if we have issues on 1.1.x vs 1.0.x. > > My versions: > > openssl version > OpenSSL 1.1.1g 21 Apr 2020 > > mvn -version > Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) > Maven home: /opt/apache-maven-3.6.3 > Java version: 1.8.0_265, vendor: AdoptOpenJDK, runtime: > /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.15.6", arch: "x86_64", family: "mac" > > Thank you, > Gary > > > On Sat, Aug 22, 2020 at 7:48 PM 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 > > > > > > >
