BLasan commented on pull request #1597: URL: https://github.com/apache/fineract/pull/1597#issuecomment-781376831
> > Hi - instead of excluding this from the check, you really should look to exclude the duplicate inclusion of the same dependency. It only makes sense to remove it from the check if there is no other way to avoid it - eg if two different jars, which are both required, contain the same class. But that's not the case here, so excluding one of the dependencies would be the right way forward IMHO. > > @BLasan and @ptuomola how can i find where this dependency is being called and how do we address removing it and yet still be able to utilize it in this class > > i have also noticed sometime that even the order of the dependencies in dependencies.gradle file matters alot Yuh, if we can avoid having the `jakarta.activation/jakarta.activation-api/1.2.2` dependency from javax.mail, we'll be able to resolve this ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
