Re: Ant JUnit tests

Like discussed in the other thread, I don't understand what's wrong with setting the expected properties in the IDE itself (like the "ant.home"). IDEs provide these configurations/settings for reasons like these. What would it achieve by virtually disabling these tests, in IDE, by adding those

Ant JUnit tests

I am refactoring Ant JUnit tests with a goal to make them more "IDE-friendly". I found several tests that are implictly dependent on ant.home property being set. In these cases, the test should be prevented from execution by adding an assumption; however, perhaps there might be a suitable default,

Re: Include ANT_HOME location in "ant -version" ?

We ought to update the manual (in particular [1]) and make [2] (especially "ant -diagnostics") much more prominent. Gintas [1] https://ant.apache.org/manual/feedback.html [2] https://ant.apache.org/manual/install.html#Troubleshooting 2018-04-19 15:41 GMT+00:00 Jaikiran Pai

Re: [RESULT][VOTE] Ivy 2.5.0-rc1 Release

Binaries have been pushed, but the process to update the site still reference the old way, with a documentation managed with xooki. So I’ll need some time to create a process for asciidoc based documentation and run it. Nicolas > Le 19 avr. 2018 à 20:13, Nicolas Lalevée

[RESULT][VOTE] Ivy 2.5.0-rc1 Release

The release got 4 binding +1. The release is thus accepted. I’ll get it published then. Nicolas > Le 12 avr. 2018 à 18:29, Nicolas Lalevée a écrit > : > > I have built a release candidate for Ivy 2.5.0-rc1. > > The git tag of this release is: >

Include ANT_HOME location in "ant -version" ?

In context of this[1] and many similar questions/confusion previously, I am wondering if our "ant -version" output should even include, a line in the output, the location which is used as ANT_HOME? That will probably make it clearer and easy to understand where it's being printed from. Any