[GitHub] [tomcat-jakartaee-migration] rmaucher commented on issue #3: Bug: Removing signature from JAR file with JCE providers leads to SecurityException
rmaucher commented on issue #3: Bug: Removing signature from JAR file with JCE providers leads to SecurityException URL: https://github.com/apache/tomcat-jakartaee-migration/issues/3#issuecomment-613924051 Yes, a resource filtering pattern or some kind could be a good add with plenty of uses. Still copy out and in should work and would likely be easier for you to do with your JCE JAR. 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: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[GitHub] [tomcat-jakartaee-migration] rmaucher commented on issue #3: Bug: Removing signature from JAR file with JCE providers leads to SecurityException
rmaucher commented on issue #3: Bug: Removing signature from JAR file with JCE providers leads to SecurityException URL: https://github.com/apache/tomcat-jakartaee-migration/issues/3#issuecomment-613880074 I think users should probably use scripting to exclude problem JARs from the migration. Trying to do too much would lead to more problems, here a likely excessive memory use [there is the same problem with SB which wants some uncompressed JARs, also not doable without full load in memory]. This tool is IMO better if it stays simple. 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: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
