Let’s use Ivy (properly!) and drop Maven Ant tasks + Commons OpenPGP by twogee · Pull Request #54 · apache/ant

twogee · 2017-12-26T20:56:37Z

The implementation is incomplete, please comment.
I put the extraneous stuff in attic subdirectory for reference.
release/upload.xml could very well be integrated in build.xml (because of project.version).
fetch.xml does not implement all targets nor updating of Ant distribution
(could be done by restricting ivy:resolve to a particular conf). 🎅

asfgit · 2017-12-27T06:09:11Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/16/

asfgit · 2017-12-27T06:10:04Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/22/

bodewig · 2017-12-27T12:10:53Z

I don't have any problem with you replacing stuff that works with other stuff that works as well. But before you put too much effort into it, maybe you should look through https://github.com/apache/ant/blob/master/ReleaseInstructions to see what is and what is not used during a release at all.

As I've managed a few releases myself let me start by telling you that I have run fetch.xml when we upgraded BCEL but usually don't use it at all as my workspace already contains everything I need to build a release.

I have never used build-osx-pkg.py (and am not aware of anybody ever using it, buildosxpackage has never been true for me and there is no pkg file in http://archive.apache.org/dist/ant/binaries/) or signit.xml (as I prefer to use the command line for that, I think Antoine has used it in the past).

As I usually am not an Ivy user I'd prefer my everyday build of Ant to not require me to place Ivy on the CLASSPATH, I'm totally content with not integrating upload with the normal build process as uploading is a very rare exceptional use case only ever performed by a single person. But that's just my preference, YMMV.

twogee · 2017-12-27T17:00:28Z

I would like to point out one distinction: I would like to replace the stuff that works (sort of) with less stuff that does the same job, and hopefully more. Besides, my beef with Maven Ant tasks was that they morphed into Aether Ant tasks, and then Maven Resolver Ant tasks and changed syntax along the way, and I couldn't add Bintray using Maven Ant tasks (at least not in a trivial way).

buildosxpackage is a requested feature, and it does no harm to keep it, albeit in a simple native implementation.

The point with signit.xml is that Ivy does it all in one go with upload.xml and with less stuff in ivy.xml

I can change fetch.xml so that release conf goes into a separate place, and so Ivy + BouncyCastle are kept out of sight (unlike Maven Ant tasks).

bodewig · 2017-12-27T20:28:20Z

I didn't suggest to remove the buildosxpackage feature, just that you are putting quite a bit of effort into an area that is probably never used - at least not much.

As I said, I don't use signit at all and I do not want to give the passphrase to my PGP key on the command line. As long as I can keep using the gpg command line and Ivy will then upload the signatures I've created, I'm fine with it.

twogee · 2017-12-27T21:55:46Z

buildosxpackage was peanuts compared to getting rid of root system property kludge for surefire in tests.

BTW, Ivy signer saves you work with

signing in advance
having to declare all signatures in ivy.xml
publishing extraneous checksums for signatures

I'd rather add another ivy.xml for distributions that would use filesystem resolver to publish signed distributions into the svn repo... svn resolver for Ivy seems a bit of an overkill.

twogee · 2017-12-27T22:21:52Z

Re password input: isn't there a task with SecureInputHandler for that?

bodewig · 2017-12-28T10:05:09Z

For the changes you plan to introduce to the release process I urge you to not change things just because they look better to you. As it stands I'd be your main user and I'm fine with the process as it is and am completely happy with signing artifacts manually (which happens whenever I cut a release, so twice every few months at best).

Our Nexus is going to create extraneous checksums anyway, no matter what Ivy does. Not sure about your second point (I don't declare anything anywhere). You are completely losing me when you talk about the svn resolver, I don't see any reason to use Ivy in order to publish artifacts to dist.apache.org at all.

twogee · 2017-12-28T11:02:21Z

I am very well aware of your role. I hope we agree about KISS or continuous improvement, though.

In particular, regarding the second point, please compare release/ivy.xml with ivy.xml (too bad the diff is so huge that Git thinks they're two different files). The price of simplification to pay, so to speak, is signing while uploading. If you're not willing to discuss that, we can leave the whole upload discussion out and only focus on fetch. However, there is one more point with distributions (zip and tar), if you bear with me.

It is my understanding of the release process that distributions are manually copied and checked into Subversion. My point was that the process could be better documented by creating an extra ivy.xml which would be used by upload (or upload-like) process and thus be semi-automated.

bodewig · 2017-12-28T11:45:02Z

Sorry if I sounds bossy here, this is not at all what I'm trying to be. It's more like your user asking you to verify your product improvements are actually improvements for them. :-)

I'm certainly not against improvements, neither continuous nor as bigger bangs.

TBH I don't really care for the content of a write-once Ivy file much, but that may be just me. Maybe I'm (a bit) old-fashioned, I actually really want to upload files to Nexus and svn manually rather than automate this, as this is the step where I personally verify all artifacts one more time before calling for a vote.

We probably should move the upload discussion to the dev list and really focus on the fetch part here.

bodewig · 2017-12-28T16:33:35Z

We probably should move the upload discussion to the dev list

https://lists.apache.org/thread.html/2a951ca8c7808e604e243567157898730cba4d41f575d92adabaf264@%3Cdev.ant.apache.org%3E

twogee · 2017-12-28T17:42:10Z

Good idea. Meanwhile, I'd like commit the pkg-distribution target sans python to avoid distraction.

asfgit · 2017-12-31T09:42:47Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/23/

asfgit · 2017-12-31T09:43:28Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/17/

asfgit · 2018-01-16T19:57:16Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/18/

asfgit · 2018-01-16T21:07:31Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/24/

asfgit · 2018-01-16T21:12:15Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/19/

asfgit · 2018-01-16T21:56:46Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/25/

twogee · 2018-01-18T22:30:50Z

I revised the documentation as suggested and added correct entries for Groovy in the process.

asfgit · 2018-01-18T22:38:24Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/26/

asfgit · 2018-01-18T23:29:35Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/20/

asfgit · 2018-01-19T06:38:52Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/21/

asfgit · 2018-01-19T06:39:44Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/27/

asfgit · 2018-01-19T09:34:09Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/22/

asfgit · 2018-01-19T09:35:11Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/28/

asfgit · 2018-01-19T10:29:31Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/23/

asfgit · 2018-08-12T12:25:00Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/79/

asfgit · 2018-08-12T12:25:12Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/73/

asfgit · 2018-08-12T20:35:46Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/82/

asfgit · 2018-08-12T20:36:08Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/76/

asfgit · 2018-08-20T15:26:35Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/77/

asfgit · 2018-08-20T15:42:48Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/83/

asfgit · 2018-08-28T19:47:39Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/79/

asfgit · 2018-08-28T19:47:44Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/85/

asfgit · 2018-11-09T06:04:22Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/94/

asfgit · 2018-11-09T06:05:45Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/88/

asfgit · 2018-12-27T09:23:31Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/104/

asfgit · 2018-12-27T09:23:53Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/110/

asfgit · 2018-12-27T23:05:21Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/106/

asfgit · 2018-12-27T23:05:48Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/112/

asfgit · 2019-05-26T08:50:25Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Windows/126/

asfgit · 2019-05-26T08:50:56Z

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant%20Github-PR-Linux/120/

twogee force-pushed the dog-food-ivy branch from 86494a6 to 0f50a72Compare December 27, 2017 05:59

twogee force-pushed the dog-food-ivy branch from 0f50a72 to bf2e2d4Compare December 31, 2017 09:32

twogee changed the title ~~Let’s use Ivy (properly!) and drop Maven Ant tasks, Commons OpenPGP, …~~Let’s use Ivy (properly!) and drop Maven Ant tasks + Commons OpenPGPDec 31, 2017

twogee force-pushed the dog-food-ivy branch from 991aa0a to 56dc144Compare January 19, 2018 06:29

twogee force-pushed the dog-food-ivy branch from e9e4b05 to d9b2724Compare August 12, 2018 12:15

twogee force-pushed the dog-food-ivy branch from d9b2724 to 1850697Compare August 12, 2018 20:26

twogee force-pushed the dog-food-ivy branch from 1850697 to 37b4d9aCompare August 20, 2018 15:15

twogee force-pushed the dog-food-ivy branch from 37b4d9a to 0cb2119Compare August 28, 2018 19:38

twogee force-pushed the dog-food-ivy branch from 0cb2119 to eacf4adCompare November 9, 2018 05:47

twogee force-pushed the dog-food-ivy branch from eacf4ad to 59aef5eCompare December 27, 2018 09:14

twogee force-pushed the dog-food-ivy branch from 59aef5e to 29c8738Compare December 27, 2018 22:48

twogee force-pushed the dog-food-ivy branch from 29c8738 to 0ecb642Compare May 26, 2019 08:41

twogee force-pushed the dog-food-ivy branch from 0ecb642 to c8a3f92Compare January 19, 2020 08:38

twogee force-pushed the dog-food-ivy branch from c8a3f92 to 548026cCompare March 8, 2020 15:40

twogee force-pushed the dog-food-ivy branch 2 times, most recently from b8e03d9 to 8a546dbCompare March 5, 2021 16:26

Let’s use Ivy (properly!) and drop Maven Ant tasks + Commons OpenPGP
d4b599a

twogee force-pushed the dog-food-ivy branch from 8a546db to d4b599aCompare July 18, 2021 13:40

Uh oh!

Conversation

twogee commented Dec 26, 2017• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

asfgit commented Dec 27, 2017

Uh oh!

asfgit commented Dec 27, 2017

Uh oh!

bodewig commented Dec 27, 2017• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

twogee commented Dec 27, 2017• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

bodewig commented Dec 27, 2017

Uh oh!

twogee commented Dec 27, 2017

Uh oh!

twogee commented Dec 27, 2017

Uh oh!

bodewig commented Dec 28, 2017

Uh oh!

twogee commented Dec 28, 2017

Uh oh!

bodewig commented Dec 28, 2017

Uh oh!

bodewig commented Dec 28, 2017

Uh oh!

twogee commented Dec 28, 2017

Uh oh!

asfgit commented Dec 31, 2017

Uh oh!

asfgit commented Dec 31, 2017

Uh oh!

asfgit commented Jan 16, 2018

Uh oh!

asfgit commented Jan 16, 2018

Uh oh!

asfgit commented Jan 16, 2018

Uh oh!

asfgit commented Jan 16, 2018

Uh oh!

twogee commented Jan 18, 2018

Uh oh!

asfgit commented Jan 18, 2018

Uh oh!

asfgit commented Jan 18, 2018

Uh oh!

asfgit commented Jan 19, 2018

Uh oh!

asfgit commented Jan 19, 2018

Uh oh!

asfgit commented Jan 19, 2018

Uh oh!

asfgit commented Jan 19, 2018

Uh oh!

asfgit commented Jan 19, 2018

Uh oh!

asfgit commented Aug 12, 2018

Uh oh!

asfgit commented Aug 12, 2018

Uh oh!

asfgit commented Aug 12, 2018

Uh oh!

asfgit commented Aug 12, 2018

Uh oh!

asfgit commented Aug 20, 2018

Uh oh!

asfgit commented Aug 20, 2018

Uh oh!

asfgit commented Aug 28, 2018

Uh oh!

asfgit commented Aug 28, 2018

Uh oh!

asfgit commented Nov 9, 2018

Uh oh!

asfgit commented Nov 9, 2018

Uh oh!

asfgit commented Dec 27, 2018

twogee commented Dec 26, 2017•
edited
Loading

bodewig commented Dec 27, 2017•
edited
Loading

twogee commented Dec 27, 2017•
edited
Loading