cstamas commented on PR #118:
URL: https://github.com/apache/maven-release/pull/118#issuecomment-1118960807

   @rfscholte or @hboutemy would be good if any of you would bless this PR so 
we can merge. Again, as before, if there is any other PR scheduled, please 
merge it BEFORE this one, I will handle conflicts.
   
   But, this PR clearly shows severe issues with m-release-p:
   * why does release redo Maven CLI? (see use of commons-cli), this is 
obviously a duplication of logic here
   * why does release resolve anything at all? Several of us have hard time to 
understand what is happening here
   
   All in all, I still think what I said before: "this plugin does WAAY more 
than it should", and hence, is very fragile (the plugin but it's process as 
well).
   
   Anyway, let's move on, and we can tinker more about these later.


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to