On Thu, 21 Jun 2018 at 11:17, Stefan Bodewig <bode...@apache.org> wrote:
> On 2018-06-21, Gintautas Grigelionis wrote: > > > POM template has inconsistent Ant versions, 1.7.1 in compile scope and > > 1.8.1 in provided scope. > > True. > > This happened in c3f8655 which updated the dependencies to 1.8.1 because > one of the unit tests used a method of ant-testutil that hasn't been > present in Ant 1.7. > > We could fix the test or explicitly document Ant 1.8.x as new > requirement - which really doesn't exist except for the tests. > > The upgrade would be a breaking change but I don't expect it would break > anything in real life. Some of the other antlibs may require Ant 1.7 but > the only other one I'd expect to get new releases (Compress) is at 1.8 > already, so upgrading the dependency probably doesn't do any harm to > them. > I decide to look at antlib builds, and I wonder why common/build.properties contain javac.-source=1.2 javac.-target=1.2 Shouldn't antlibs be baselined to something more recent? If I remember it correctly, Ant 1.8 was meant for Java 1.4, so I would suggest either that or the oldest maintained version of Ant, i.e. 1.9, corresponding to Java 5. Gintas P.S. I'm struggling to understand why "ant test" of antlibs bails because "compile-tests" goes "setup-for-junit-tests, antlib, resolve" rather than doing "resolve" first and using the retrieved dependencies?
