Re: Ant JUnit tests

2018-04-20 15:26 GMT+00:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>: > > Le 20 avr. 2018 à 07:09, Gintautas Grigelionis <g.grigelio...@gmail.com> > a écrit : > > > > I am refactoring Ant JUnit tests with a goal to make them more > > "IDE-friendl

Re: Ant JUnit tests

2018-04-20 17:34 GMT+00:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>: > > > Le 20 avr. 2018 à 18:48, Gintautas Grigelionis <g.grigelio...@gmail.com> > a écrit : > > > > 2018-04-20 15:26 GMT+00:00 Nicolas Lalevée <nicolas.lale...@hibnet.org > <mail

Re: Use of org.hamcrest.Matchers

Hmm... are you sure that Gump has hamcrest-library? By the looks of it, the classpath contains antlr 3 and bcel 5... Gintas 2018-04-22 8:45 GMT+00:00 Stefan Bodewig : > Hi > > when Apache Gump builds Ant it builds it against Hamcrest 2.x which used > to work fine as long as

Re: Mass changes to various projects under Ant umbrella - should we be doing it?

2018-04-15 9:59 GMT+00:00 Stefan Bodewig <bode...@apache.org>: > On 2018-04-15, Gintautas Grigelionis wrote: > > > Could you please explain what alternative approach does the "root" > > property support > > It has been added wit

Re: Mass changes to various projects under Ant umbrella - should we be doing it?

2018-04-14 16:23 GMT+00:00 Stefan Bodewig <bode...@apache.org>: > On 2018-04-13, Gintautas Grigelionis wrote: > > > 2018-04-13 5:33 GMT+00:00 Stefan Bodewig <bode...@apache.org>: > > >> Ant test cases are not designed to be run from an IDE, this has n

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: Ant JUnit tests

in IDE, by adding > those assumptions? > > -Jaikiran > > > > On 20/04/18 10:39 AM, Gintautas Grigelionis wrote: > >> I am refactoring Ant JUnit tests with a goal to make them more >> "IDE-friendly". I found several tests that are implictly dependent on

Re: Ant JUnit tests

is the a suitable value of ant.home? Thanks, Gintas 2018-04-20 13:16 GMT+00:00 Jan Matèrne (jhm) <apa...@materne.de>: > Why not an assert with a meaningful message to test if the property is set? > > Jan > > > -Ursprüngliche Nachricht- > > Von: Gintautas

Re: Use of org.hamcrest.Matchers

2018-04-22 13:56 GMT+00:00 Stefan Bodewig <bode...@apache.org>: On 2018-04-22, Gintautas Grigelionis wrote: > > > Hmm... are you sure that Gump has hamcrest-library? > > No, you are correct. I was under the impression it was using Hamcrest > 2.x while it was not - Ha

Re: Use of org.hamcrest.Matchers

2018-04-22 22:32 GMT+00:00 Martin Gainty : > MG>Hi Gintas please see question below > > I wish we could replace fetch.xml with an Ivy equivalent :-) > MG>lib/libraries.properties > MG>hamcrest-core.version=1.3 > MG>hamcrest-library.version=${hamcrest-core.version} > > MG>if

Re: ant git commit: Yet more isEmpty()

2018-04-15 10:04 GMT+00:00 Stefan Bodewig : > On 2018-04-15, wrote: > > > @@ -275,10 +270,7 @@ public class DefaultLogger implements BuildLogger { > > new BufferedReader(new > StringReader(event.getMessage( { > > >

SBT branch in Ivy repo

I asked sbt developers [1] whether they would like to use the same Git repo. The consensus seems to be that sbt would like to have their own branch (or two). Would it be acceptable to graft sbt branch(es) to Ivy repo? Gintas [1] https://github.com/sbt/ivy/issues/28

Re: SBT branch in Ivy repo

question, sbt maintainers could either fork the original Ivy repo or become committers. Are there some political issues that I did not notice? Gintas 2018-03-29 14:49 GMT+02:00 Stefan Bodewig <bode...@apache.org>: > On 2018-03-25, Gintautas Grigelionis wrote: > > > I asked

Re: ant git commit: Add dependency description

2018-03-17 16:09 GMT+01:00 Gintautas Grigelionis <g.grigelio...@gmail.com>: > > > I was wondering why junitlauncher task depended on all jars being present > in Ant classpath with no possibility to set a separate classpath for the > task? > ... especially because ant -f

Re: Snapshot access to regular users of Ant

Thanks for pointing this out. To me, it means one thing: release more often. The way I read it, publishing is not forbidden per se, but rather advertising. That's consistent with GitHub repo clones being available, but without "clone me at GitHub" ribbons. On the other hand, I rewrote the manual

Re: ant git commit: Add dependency description

Thanks for correcting the omission. But, the task manual page states that junit.jar of JUnit 4 might still be necessary ... For junit-vintage engine: - junit-vintage-engine.jar - junit.jar (JUnit 4.x version) ... so perhaps it's worth a note anyway. I was wondering why junitlauncher

Re: junitlauncher dependency on JUnit4?

My understanding is that junitlauncher has a dependency on JUnit 4 through vintage engine. I guess pom should provide profiles for engine choice. See my earlier questions re the task classpath. Gintas Den tis 20 mars 2018 16:28Stefan Bodewig skrev: > Hi > > I've just added

Re: Snapshot access to regular users of Ant

2018-03-20 18:03 GMT+01:00 Stefan Bodewig <bode...@apache.org>: > On 2018-03-19, Gintautas Grigelionis wrote: > > > Maybe Ant Task Guidelines could be exposed under under "Contributing" > > as a landing page, and the relevant information could be moved into

Re: junitlauncher dependency on JUnit4?

2018-03-20 16:43 GMT+01:00 Stefan Bodewig <bode...@apache.org>: > On 2018-03-20, Gintautas Grigelionis wrote: > > > My understanding is that junitlauncher has a dependency on JUnit 4 > through > > vintage engine. I guess pom should provide profiles for engine c

Re: Snapshot access to regular users of Ant

:00 Stefan Bodewig <bode...@apache.org>: > On 2018-03-17, Gintautas Grigelionis wrote: > > > On the other hand, I rewrote the manual (which was still talking about > > CVS), suggesting that the proper way to propose code changes would be > > a GitHub PR rather than an ar

Re: Ant documentation

2018-03-01 10:43 GMT+01:00 Jan Matèrne (jhm) : > > > I made an attempt to convert the manual to HTML 5, the rationale > > being > > > that HTML 5 deprecates tt tag and recommends to replace it with tags > > > like code, kbd, samp and var, which could be used in a more > >

Re: AW: committer += gintas

ttps://blogs.apache.org/infra/entry/git_based_websites_available > [2] https://svn.apache.org/viewvc/ant/ > > > > > > -Ursprüngliche Nachricht- > > Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com] > > Gesendet: Montag, 26. Februar 2018 09:46 > > An: Ant Devel

Re: Ant documentation

2018-03-02 9:54 GMT+01:00 Stefan Bodewig <bode...@apache.org>: > On 2018-03-01, Stefan Bodewig wrote: > > >> On Thu, Mar 1, 2018 at 7:28 AM, Gintautas Grigelionis < > >> g.grigelio...@gmail.com> wrote: > > >>> I tried then to u

Re: Ant documentation

2018-03-02 7:44 GMT+01:00 Jan Matèrne (jhm) : > > > > > I made an attempt to convert the manual to HTML 5, the rationale > > > > being > > > > > that HTML 5 deprecates tt tag and recommends to replace it with > > > > > tags like code, kbd, samp and var, which could be used in a

Re: Ivy release this month?

The ugly thing 2018-02-27 22:40 GMT+01:00 Gintautas Grigelionis <g.grigelio...@gmail.com>: > 2018-02-18 20:30 GMT+01:00 Stefan Bodewig <bode...@apache.org>: > >> [Personally I prefer discussion by email over discussion in github >> issues.] >> > > The

Re: Ivy release this month?

2018-02-18 20:30 GMT+01:00 Stefan Bodewig : > [Personally I prefer discussion by email over discussion in github > issues.] > The beauty is that GitHub comments are echoed in mailing list, and, in case of PR mentioning JIRA issues, in JIRA as well. Gintas

Re: Ant documentation

2018-03-02 13:13 GMT+01:00 Stefan Bodewig <bode...@apache.org>: > On 2018-03-02, Gintautas Grigelionis wrote: > > > 2018-03-02 9:54 GMT+01:00 Stefan Bodewig <bode...@apache.org>: > > >> On 2018-03-01, Stefan Bodewig wrote: > > >>>>

Re: [Bug 33169] KIndly update the date feature

On Thu, 28 Jun 2018 at 11:43, Jan Matèrne (jhm) wrote: > > > Just curious about our bugzilla infrastructure - do random users get > > > to change the content of these bugs, even if they aren't the ones who > > > reported the issue? > > > > Yes. > > > > Back when Bugzilla was introduced the

Re: Java 11 Compatibility Problem

Equinox JarProcessor [1] seems to use pack200 CLI. 1. https://git.eclipse.org/c/equinox/rt.equinox.p2.git/plain/bundles/org.eclipse.equinox.p2.jarprocessor/src/org/eclipse/internal/provisional/equinox/p2/jarprocessor/JarProcessor.java Gintas On Thu, 11 Oct 2018 at 17:00, Nicolas Lalevée wrote:

Re: Tests in Surefire

and, while building Ant? > > -Jaikiran > > > On 20/10/18 3:31 PM, Gintautas Grigelionis wrote: > > I believe that in order to execute Ant test suite in Surefire one must > > configure basedir which unfortunately affects Ant test projects. Perhaps > it > > would m

Re: Tests in Surefire

On Tue, 23 Oct 2018 at 12:25, Stefan Bodewig wrote: > On 2018-10-20, Gintautas Grigelionis wrote: > > > I believe that in order to execute Ant test suite in Surefire one must > > configure basedir which unfortunately affects Ant test projects. > > I'm not sure I share t

Re: Tests in Surefire

On Wed, 24 Oct 2018 at 00:29, Gintautas Grigelionis wrote: > On Tue, 23 Oct 2018 at 12:25, Stefan Bodewig wrote: > >> On 2018-10-20, Gintautas Grigelionis wrote: >> >> > I believe that in order to execute Ant test suite in Surefire one must >> > configure bas

Re: ant git commit: Add magic names for tests, run more tests in Surefire

On Sun, 28 Oct 2018 at 21:02, Stefan Bodewig wrote: > On 2018-10-28, Gintautas Grigelionis wrote: > > On Sun, 28 Oct 2018 at 20:23, Stefan Bodewig wrote: > > >> I guess I need to create a branch to either convince you it is possible > >> or convince me that

Re: ant git commit: Add magic names for tests, run more tests in Surefire

> The tests for core fail for me (CommandlineJava) anyway. I think I've > already said that running Ant's unit tests in Maven is a non-goal for me > :-) > I'll have a closer look at it tomorrow, if you don't mind. Could you please provide some details of your setup? Even if running unit tests

Re: ant git commit: Add magic names for tests, run more tests in Surefire

On Sun, 28 Oct 2018 at 18:17, Stefan Bodewig wrote: > On 2018-10-28, Gintautas Grigelionis wrote: > > On Sun, 28 Oct 2018 at 17:59, Stefan Bodewig wrote: > > >> I wonder whether it wouldn't be a good idea to create a separate class > >> for constants used du

Re: ant git commit: Add magic names for tests, run more tests in Surefire

On Sun, 28 Oct 2018 at 20:23, Stefan Bodewig wrote: > On 2018-10-28, Gintautas Grigelionis wrote: > > On Sun, 28 Oct 2018 at 18:48, Stefan Bodewig wrote: > >> On 2018-10-28, Gintautas Grigelionis wrote: > >>> On Sun, 28 Oct 2018 at 18:17, Stefan Bodewig > wrote

Re: ant git commit: Add magic names for tests, run more tests in Surefire

On Sun, 28 Oct 2018 at 18:48, Stefan Bodewig wrote: > On 2018-10-28, Gintautas Grigelionis wrote: > > On Sun, 28 Oct 2018 at 18:17, Stefan Bodewig wrote: > >> On 2018-10-28, Gintautas Grigelionis wrote: > >>> On Sun, 28 Oct 2018 at 17:59, Stefan Bodewig >

Re: Tests in Surefire

On Thu, 25 Oct 2018 at 09:05, Gintautas Grigelionis wrote: > On Wed, 24 Oct 2018 at 00:29, Gintautas Grigelionis < > g.grigelio...@gmail.com> wrote: > >> On Tue, 23 Oct 2018 at 12:25, Stefan Bodewig wrote: >> >>> On 2018-10-20, Gintautas Grigelionis wrot

Re: ant git commit: Add magic names for tests, run more tests in Surefire

On Sun, 28 Oct 2018 at 17:59, Stefan Bodewig wrote: > On 2018-10-23, wrote: > > > > http://git-wip-us.apache.org/repos/asf/ant/blob/679a9422/src/main/org/apache/tools/ant/MagicNames.java > > >+/** > >+ * Magic property that makes unit tests based on BuildFileTest > >+ * or

Re: ant git commit: Add magic names for tests, run more tests in Surefire

> Thanks, I'll merge it to master, then. > I've notice in Nightly that Ant treats MagicTestNames as a test, too. Would it make sense to add a test method, checking for documented properties? Gintas

Re: ant git commit: Add magic names for tests, run more tests in Surefire

On Mon, 29 Oct 2018 at 10:00, Stefan Bodewig wrote: > There is no cycle: core <- testutil <- tests of core > > It is just Maven's model that doesn't allow you to introduce test scope > dependencies that depend on your code under test. A model I disagree > with. > > So in the maven POMs we might

Tests in Surefire

I believe that in order to execute Ant test suite in Surefire one must configure basedir which unfortunately affects Ant test projects. Perhaps it would make sense to have a magic property that (in combination with detection of Surefire environment) would allow BuildFileRule to call

Re: ant git commit: Check spelling

c8d4e8a26aadedL25 > < > https://github.com/apache/ant/commit/54b6df2f44c5cb4f9573f99330c2d2908f1bf506#diff-9ad784be5493fb9473c8d4e8a26aadedL25 > > > > Nicolas > > > > > -Jaikiran > > > > > > On 11/09/18 12:17 PM, Gintautas Grigelionis wrote: > >> How was this different from P

Re: [ant] branch master updated: Update JSCh (see http://www.jcraft.com/jsch/ChangeLog)

Thanks, sorry about missing pom.xml and the manual. Gintas On Thu, 27 Dec 2018 at 14:21, Jaikiran Pai wrote: > Hi Stefan, > > Thank you for reminding me of those files. I have now pushed a commit in > both the branches which updates these files to use the new version. > > -Jaikiran > > On

Re: Antlib SVN and antunit Java versions

On Tue, 18 Dec 2018 at 10:44, Dominique Devienne wrote: > On Tue, Dec 18, 2018 at 9:21 AM Jaikiran Pai wrote: > > > [...] 2 jobs[1][2] which are for Antlib SVN and Antunit libraries. > > Both these jobs are configure for JDK 5 [...] > > However, the Maven central repo [...[ has been configured

Re: jmod and jlink support

On Fri, 30 Nov 2018 at 19:25, Craig Pell wrote: > Or am I misunderstanding the goal? Are you suggesting that future > versions of Ant should just be built with Java 9 (or later)? If so, > that would suggest that the "needs.jdk9+" selector is not needed, right? > I believe the goal is to

Re: Need inputs before starting a new RC for 1.10.6

On Thu, 28 Mar 2019 at 15:36, Stefan Bodewig wrote: > On 2019-03-28, Jaikiran Pai wrote: > > > As far as I understand the pom files that we maintain and publish to > > Maven central are basic minimal. However, a bunch of relatively recent > > commits have introduced certain changes to those

Re: New Confluence Wiki

Perhaps [1] could be placed under Proposals? Also, links to antbook.org should point to [2] instead. And, FWIW, Kevin Lee has put his book on GitHub [3]. Gintas [1] https://cwiki.apache.org/confluence/display/ANT/MergeCandidates18xBranch [2] https://www.manning.com/books/ant-in-action [3]

Re: Buliding IvyDE

Is there any documentation readily available? The links in the document below are not easy to follow https://www.eclipse.org/eclipse/development/porting/eclipse_4_12_porting_guide.html Gintas On Sat, 14 Sep 2019 at 09:20, Aleksandar Kurtakov wrote: > On Fri, Sep 13, 2019 at 4:17 PM Tim Astle

Re: Planning to initiate a Ivy release

Many thanks, Jaikiran. Please consider updating JSch to 0.1.55 (fixes bugs with EC crypto) and Commons VFS to 2.4.1 (upgrades HTTP Client to 4.5+). May I suggest considering preemptive authentication (aka IVY-1280) and Ivy reports without img links to Ivy website (aka IVY-922)? Gintas On Sun, 8

Re: Planning to initiate a Ivy release

Thanks for prompt response. Please see the comments bellow. On Sun, 8 Sep 2019 at 14:39, Jaikiran Pai wrote: > > On 08/09/19 12:41 PM, Gintautas Grigelionis wrote: > > Many thanks, Jaikiran. Please consider updating JSch to 0.1.55 (fixes > bugs > > with EC crypto) > &g

Re: Next plans for Ivy

On Sat, 2 Nov 2019 at 20:32, Matt Sicker wrote: > The more JDKs you require in the build, the harder it > is to set up. If you target Java 8 but build at a newer release, you could > possibly get away with a single JDK plus an API checker to avoid using new > things. > Talking of API checkers,

Re: Script task specification

By the way, the failure "unable to create engine" was due to OpenJDK 7 lacking Rhino. Perhaps worth a mention, too. Gintas On Wed, 30 Oct 2019 at 21:59, Gintautas Grigelionis wrote: > Thanks for prompt reply and all pointers. idReferences seem to have no > connecti

Re: Next plans for Ivy

It will be good to be on the same page with major dependencies (and hopefully fix that old nut listTokenValues() :-) Please consider Java 11 for TLSv1.3 when time comes (or the next LTS version, Java 17 when it's out -- by then, pack200 will surely be gone...) Gintas On Wed, 30 Oct 2019 at

Re: Script task specification

(jhm) [mailto:apa...@materne.de] > > > Gesendet: Dienstag, 29. Oktober 2019 08:03 > > > An: 'Ant Developers List' > > > Betreff: AW: Script task specification > > > > > > It seems that the task must be executed before. > > > If you add a >de

Script task specification

The documentation of the script task states: "All items (tasks, targets, etc) of the running project are accessible from the script, using either their name or id attributes (as long as their names are considered valid Java identifiers, that is). " However, the following fails:

Re: Time for 1.10.8 release?

Thanks, the PR is ready now. Please have a look at #111, too (a cherry-pick of #110 for master branch). Gintas On Fri, 10 Jan 2020 at 15:30, Jaikiran Pai wrote: > There's time. If it's a straightforward PR, I'll merge it. > > -Jaikiran > > On 10/01/20 7:46 pm, Gintautas Gr

Re: Time for 1.10.8 release?

I was planning a tiny PR to update the third party libraries, if there's time still. Gintas On Fri, 10 Jan 2020 at 14:54, Jaikiran Pai wrote: > I just noticed that we have added some good number of bug fixes[1] since > our 1.10.7 release and it's been already 4 months since that release. If >

Re: [DISCUSS] EOL the 1.9.x branch with the 1.9.15 release

+1 if that counts. I don't think there's much use of Java 7- nowadays, especially when networked. Gintas On Wed, 20 May 2020 at 13:24, Stefan Bodewig wrote: > It looks as if the vote will simply not pass because of a lack of > participation - which is certainly fine. Unless we get more binding

Re: GraalVM JavaScript Again

On Mon, 10 Aug 2020 at 17:52, Stefan Bodewig wrote: > Hi > > right now master sets polyglot.js.allowAllAccess to true when it detects > the script engine is a GraalVM engine. This is necessary if the script > wants to use any of the Ant objects. > > Jaikiran suggests to enable full Nashorn

Re: [CI] Creating Jobs on New ci-builds Machine

On Mon, 10 Aug 2020 at 16:23, Stefan Bodewig wrote: > On 2020-08-10, Stefan Bodewig wrote: > > > I intend to also migrate AntUnit (so we do have a template for Antlib > > builds) and maybe the Windows Matrix for Ant's master. > > Both done, as well as Compress Antlib, Ivy, Ivy Tests and IvyDE.

Re: Migrating build jobs

> > Our build job for testing our POMs (by building Ant from POM) could be > migrated (easily) because there is no type=Maven any more. Maybe building > via Shell ... > Looks like "Freestyle Project" -> Build step "Execute top-level Maven targets" is a possibility? Gintas

Re: Ivy expertise needed for Bug 65110

On Fri, 29 Jan 2021 at 08:59, Stefan Bodewig wrote: > On 2021-01-28, Jaikiran Pai wrote: > > > I had a quick look and to me this looks like a bug in our build.xml > > itself and not related to Ivy. > > My bad. I must admit I really don't know much about Ivy at all and > forgot how the jars we

Re: Release 1.10.10 of Ant?

BTW jasper-compiler 4.x artifacts seem to lack pom files in Maven Central. There are 5.0.x and 5.5.x that contain pom files. Gintas On Thu, 25 Feb 2021 at 06:41, Gintautas Grigelionis wrote: > PR 142? > > Gintas > > On Thu, 25 Feb 2021 at 03:56, Jaikiran Pai wrote: > &

Re: Release 1.10.10 of Ant?

PR 142? Gintas On Thu, 25 Feb 2021 at 03:56, Jaikiran Pai wrote: > Our last release for 1.10.x of Ant happened in September 2020. There > have been a good number of bug fixes and enhancements done since > then[1]. Should we go ahead and release 1.10.10 in the coming weeks? I > don't have any

Re: Impact of Java SecurityManager being deprecated for removal post Java 17

On Thu, 19 Aug 2021 at 12:01, Stefan Bodewig wrote: > I didn't mean the Antlib to be backwards compatible, but rather to offer > it and tell people to switch over to it. It would be the first time we'd > remove a core feature of Ant completely, though, so we may need to > discuss whether there

Re: Impact of Java SecurityManager being deprecated for removal post Java 17

On Mon, 23 Aug 2021 at 17:39, Stefan Bodewig wrote: > On 2021-08-19, Gintautas Grigelionis wrote: > > > On Thu, 19 Aug 2021 at 12:01, Stefan Bodewig wrote: > > >> I didn't mean the Antlib to be backwards compatible, but rather to offer > >> it and tell peop

Re: Impact of Java SecurityManager being deprecated for removal post Java 17

Hi, The most acute problem is this: SecurityManager seems to be involved in handling of return code from forked processes. How does JDK 17+ solve that? Regarding the permissions type: if the sandbox is gone in JDK, then permissions should go, too. For the reference, a summary of permissions

Re: Impact of Java SecurityManager being deprecated for removal post Java 17

ngliche Nachricht- > Von: Stefan Bodewig > Gesendet: Sonntag, 19. September 2021 15:04 > An: dev@ant.apache.org > Betreff: Re: Impact of Java SecurityManager being deprecated for removal > post Java 17 > > On 2021-09-19, Gintautas Grigelionis wrote: > > > On Mon, 23

Re: [VOTE] Release Apache Ant 1.10.12 based on RC1

On Sat, 2 Oct 2021 at 15:48, Gavin McDonald wrote: > > Please not that the ASF nor its projects release Binaries. > (They are provided to users as a convenience) > We also do not vote on releases based on Binaries. > > The vote should be based on whether or not the 'source' - that > is being

Re: Release 1.10.12 of Ant?

On Tue, 28 Sept 2021 at 09:25, Stefan Bodewig wrote: > I think there is a MR by Gintas to replace the Maven Ant Tasks with > Ivy. Might be time to revisit it. > That MR was waiting for Ivy 2.5 (SHA-2 support). I would like to revisit it, but it may wait until the next release. Thanks for

Re: [VOTE] Release Apache Ant 1.10.12 based on RC1

If the goal of 1.10.12 is to be compilable on Java 17, shouldn't unit tests for script-related tasks in Ant core be complemented with an assumption that Rhino, Nashorn or Graal JS is around? Gintas On Tue, 5 Oct 2021 at 10:58, Paul King wrote: > +0 (non-binding) > > I checked: > * LICENSE &

Re: [VOTE] Release Apache Ant 1.10.12 based on RC1

On Thu, 7 Oct 2021 at 16:27, Jaikiran Pai wrote: > > On 07/10/21 11:27 am, Gintautas Grigelionis wrote: > > If the goal of 1.10.12 is to be compilable on Java 17, > > This 1.10.12 release of Ant (like our previous releases) is a bug fix > release. Ant 1.10.x requ

Re: Java 8 for AntUnit

On Sun, 13 Feb 2022 at 21:50, Matt Benson wrote: > Okay to stick with Java 5 for now, for the 1.9.x reason. > > Thanks, > Matt > Can JUnit 3 be removed? I believe JUnit 4 has Java 5 as a baseline. Gintas

Re: Antlib test classpath

On Sat, 5 Feb 2022 at 08:19, Stefan Bodewig wrote: > I must admit that I never tried to use things with Ivy at all. When I > run tests I do so with several -lib arguments (and always need to figure > out what is required as I don't do it often enough). > > If you figured things out it would

<    1   2   3   4