On 3/17/20, 11:37 PM, "OmPrakash Muppirala" <[email protected]> wrote:
My 2 cents:
I don't think we need to go back to the Ant vs Maven discussion. If the
Maven build/stage/release scripts works flawlessly, an Ant task can simply
call it. There is no reason both cannot be worked on continuously. In the
same way, if Maven users want, they can call Ant scripts as needed.
Why do both camps want the other way to go away?
I don't want one to go away. I want to use Maven for what it is good for and
Ant for what it is good for.
For example, we also publish to NPM as part of the release. There is a
node.js script that gets called from the Ant script during the release
process. The node.js script is a black box as far as the Ant script is
concerned.
That said, Carlos if you think you can get a release done with just Maven,
please go ahead and give it a shot. From what I remember, the Maven part
of the build/release was the issue and not the Ant portions. We all would
love to see improvements there.
Alex, you say that Carlos did not work in the trenches during the release
process, but are objecting (I think, if I understand your email correctly)
to him wanting to work now. That seem contradictory, IMHO.
I'm saying that if Carlos/Chris go back to the Maven Release Plugin process, it
will likely bring us back to the same problems we created the CI steps to work
around. So why go through all of that again?
Like Piotr just posted, Carlos should get in the trenches and get the CI steps
to work with the new Maven poms. Not acknowledging that there have been past
problems using the process they propose is going to result in more time wasted.
-Alex
