hboutemy commented on pull request #100: URL: https://github.com/apache/maven-release/pull/100#issuecomment-1025195141
I don't like the habit people have at defining property for plugin version, no, but it's a habit that has been taken by many. hard-coding some plugin names in maven-release-plugin source code looks as much as a hack as the hacks you're trying to avoid: this is what made me start the discussion, because I think we don't yet get what the real issue is it seems the issue is when the current released project requires to use a previous version I must confess that testing maven-release-plugin is hard, and doing unit or integration tests = what I'd like to see before fixing a not clearly defined issue (with hard-coded values that make me uncomfortable) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
