Re: [wildfly-dev] Refactoring the WildFly OpenSSL project

This is great news. Thanks Farah!

On Wed, Jul 22, 2020 at 11:32 AM Farah Juma <fjuma(a)redhat.com&gt; wrote: > As it stands today, the WildFly OpenSSL project contains both Java code > and native code. This means that each time we need to do a release, we need > to build the natives, regardless of whether or not there have actually been > changes made to the native code. The process of building the natives on > various platforms takes time and has caused delays in the past that could > have been avoided if we were able to handle changes to the Java code only > as a separate release. We have actually found that there have been many > times where a release has involved changes to only the Java code. To > simplify the release process, we're going to be splitting out the native > code from the WildFly OpenSSL project into a separate project. That > way, changes to the Java code only will be able to be handled as a separate > release, without needing to rebuild the natives. The proposed changes can > be found in our incubator: > > https://github.com/wildfly-security-incubator/wildfly-openssl-natives > https://github.com/wildfly-security-incubator/wildfly-openssl/tree/2.x > > The native modules that have been split out are going to retain the same > group and artifact ID as they had when contained in the wildfly-openssl > project. > > Regards, > Farah > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev -- James R. Perkins JBoss by Red Hat _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev