Hi, So I've started working on the Jakarta EE migration tool. I've some enhancements in mind but I'd like to ensure there is a consensus before proceeding.
Here are my suggestions: - Turn the tool into a plugin for the main build systems (Maven, Gradle, Ant) to easily post process the jar/war files generated by a project. I've some experience on this side with my jsign project (https://github.com/ebourg/jsign) and I suggest adopting a similar multi module structure with separate artifacts. - Use a CLI parsing library (picocli, jcommander or commons-cli) to ease the addition of command line options. It may also bring help/manpage generation, tab completion, colored messages. - Parallel processing of directories, and maybe of archives too but that's trickier. - Support in-place migration of directories. I've implemented it for single files but it looks a bit dangerous for whole directories. I think it'd be safer to ask the user to confirm first. - In memory buffering. The converters read and write directly to the disk, writing first to memory and then to the disk speeds up the migration (on my system it halved the migration time of the Tomcat source tree). What do you think? Emmanuel Bourg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
