Hello, While trying to upgrade JGIt I have to bring back bouncy castle libs into wildfly-core. While doing this I noticed that I don't need the same exact libs as what is in full (most notably the mail part). How do we handle such a case : having a different module in core vs full ? Should we add the mail part in core (maybe optional) or split the modules, or just overload in full ? Cheers, Emmanuel _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

Answers are inline: Le 16/03/2020 à 11:02, Darran Lofthouse a écrit : > Are they both the same version? Yes, it is just that I need the gpg part in core (for signature) but not the bc-mail that is defined in full. > > For other projects we have brought in the maven dependencies in dependency management in WildFly Core and then just add the additional > module definitions to WildFly. Currently there is only one BC module, do I understand correctly that I should split the BC module into several ones ? > > > On Fri, Mar 13, 2020 at 10:12 AM Emmanuel Hugonnet <ehugonne(a)redhat.com <mailto:ehugonne@redhat.com>> wrote: > > Hello, > > While trying to upgrade JGIt I have to bring back bouncy castle libs into wildfly-core. > > While doing this I noticed that I don't need the same exact libs as what is in full (most notably the mail part). > > How do we handle such a case : having a different module in core vs full ? > > Should we add the mail part in core (maybe optional) or split the modules, or just overload in full ? > > Cheers, > > Emmanuel > > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/wildfly-dev >