mabrarov commented on pull request #24: URL: https://github.com/apache/maven-ear-plugin/pull/24#issuecomment-730289313
@hboutemy, The ["Maven EAR Plugin 3.2.0 with skinnyModules option"](https://lists.apache.org/thread.html/rbcf8c12948893ff80483e2456fb6bdd78a20c94720746a94ad474741%40%3Cusers.maven.apache.org%3E) topic I started in the us...@maven.apache.org mailing list has no answers for a week. It looks like we won't get any feedback except [the one](/apache/maven-ear-plugin/pull/24#pullrequestreview-530790385) which we got here from @rfscholte. Maybe it's time to complete with this pull request and pull request #22 (these 2 pull request will produce merge conflicts which I resolved in [merge/MEAR-153_into_MEAR-216](/mabrarov/maven-ear-plugin/tree/merge/MEAR-153_into_MEAR-216) branch) and then release Maven EAR Plugin 3.2.0. Thank you for your help. @rfscholte, If you agree with [my proposal](/apache/maven-ear-plugin/pull/24#issuecomment-727590153) and with my suggestion to implement the proposal in a dedicated (new) feature request (pull request), then please confirm that here (approval of this pull request is appreciated too). Please note that this pull request doesn't prevent implementation of that proposal in a backward compatible way - this is the thing which I care about, because I'd prefer to not implement `skinnyModules` feature at all if it will make impossible giving later the maximum control you suggested. Thank you for sharing this idea. I'll open Jira ticket for `sharedLibs` property of EAR module. Maybe I'll be able to work on it this year. ---------------------------------------------------------------- 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
