> I remember another proposal which consisted of using the Gradle build to > rebuild Maven artifacts at the type of uploading to Nexus, which I liked > less because it involved re-building, and who knows what may happen that > could produce slightly different binaries. I like your new proposal better. >
Right - it would have to be a one-step operation, otherwise I wouldn't bet on those JARs being the same... > > Those are browsable and artifacts can be downloaded from there before > voting (although I'm not sure if anybody inspects those maven artifacts) > > I suspect you know this, but the smoke tester does download these > artifacts and runs some checks. > We could still build that zip for the smoke tester. The important thing here is that local artifact building and staged artifacts would be synced (uploaded within one gradle command). An alternative is to implement post-vote artifact upload in gradle (or ant within gradle). This is also possible but seems somewhat backward... Dawid >
