ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bodewig <...@git.apache.org>
Subject [GitHub] ant issue #54: Let’s use Ivy (properly!) and drop Maven Ant tasks, Commons...
Date Wed, 27 Dec 2017 12:10:54 GMT
Github user bodewig commented on the issue:

    https://github.com/apache/ant/pull/54
  
    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 preformed 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.


---

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message