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
antlib to its current level of Java (1.)5?
>
> We still create Ant 1.9.x releases from time to time and 1.9.x would not
> be able to use newer releases. Having said that, it is not as if we had
> much active development of AntUnit, so it w
Having said that, it is not as if we had
much active development of AntUnit, so it wouldn't miss out much.
Stefan
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
Similarly to the question on Ivy, is there any compelling reason we should
continue to constrain this antlib to its current level of Java (1.)5?
Matt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Apache Ant Team is pleased to announce the releases of Apache
AntUnit 1.4.1.
Apache AntUnit is an Antlib that provides a test framework for Apache
Ant tasks and types.
This release fixes the antlib.xml descriptor so that AntUnit now also
works
Hi all
with +1s by Jaikiran Pai, Maarten Coene, Jan Materne, Martijn Kruithof
and myself and no other votes the vote has passed.
I'll publish the artifacts now and send out the announcement / update
the site later today.
Many thanks to all who evaluated the release
Stefan
-
I completely forgot to vote myself.
+1
Stefan
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
AntUnit 1.4.1 based on RC1
+1
Maarten
Op zaterdag 3 juli 2021 14:41:50 CEST schreef Stefan Bodewig
:
Hi all
I've created a release candidate for AntUnit 1.4.1:
git tag: 1_4_1_RC1
on commit: e436acf
tarballs: https://dist.apache.org/repos/dist/dev/ant/antlibs/an
Downloaded src+bin.zip and did some tests. All fine.
+1
Jan
-Ursprüngliche Nachricht-
Von: Maarten Coene
Gesendet: Sonntag, 4. Juli 2021 12:17
An: Ant Developers List
Betreff: Re: [VOTE] Release Apache AntUnit 1.4.1 based on RC1
+1
Maarten
Op zaterdag 3 juli 2021 14:41:50 CEST
+1
Maarten
Op zaterdag 3 juli 2021 14:41:50 CEST schreef Stefan Bodewig
:
Hi all
I've created a release candidate for AntUnit 1.4.1:
git tag: 1_4_1_RC1
on commit: e436acf
tarballs: https://dist.apache.org/repos/dist/dev/ant/antlibs/antunit/
revision: 48645
+1.
Did some basic verification:
- Downloaded apache-ant-antunit-1.4.1-bin.tar.gz from
https://dist.apache.org/repos/dist/dev/ant/antlibs/antunit/binaries/
- Extracted locally. Checked the NOTICE file.
- Checked the WHATSNEW file.
- Checked the docs/index.html
- Checked that ant-antunit
Hi all
I've created a release candidate for AntUnit 1.4.1:
git tag: 1_4_1_RC1
on commit: e436acf
tarballs: https://dist.apache.org/repos/dist/dev/ant/antlibs/antunit/
revision: 48645
Maven artifacts:
https://repository.apache.org/content/repositories/orgapacheant
Hi all
sorry, I got occupied "elsewhere" and somehow forgot I wanted to create
a release candidate. Will do so during the weekend.
Stefan
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail:
Hello Stefan,
Releasing a new version sounds good. As for the version number, I'll let
you decide since I don't have prior background with AntUnit releases :)
-Jaikiran
On 23/05/21 2:37 pm, Stefan Bodewig wrote:
Hi all
it looks as if we didn't do what we preach, see
https:
On my wishlist I think running on Java8-16 is on top.
Java<8 is nice.
Modernizing is not necessary.
And a new release is a good idea.
Jan
-Ursprüngliche Nachricht-
Von: Stefan Bodewig
Gesendet: Sonntag, 23. Mai 2021 11:07
An: dev@ant.apache.org
Betreff: Creating a New AntUnit Rele
Hi all
it looks as if we didn't do what we preach, see
https://bz.apache.org/bugzilla/show_bug.cgi?id=65315 :-)
Over the past three years we haven't seen any reason to change anything
inside of AntUnit. The issue above is probably standing in the way for
somebody, so I'd like
On 2019-05-27, Martijn wrote:
> What maybe with this regards is a problem is the update of the
> http:///www.apache.org/licenses to https in the LICENSE file. (I will
> revert those).
> The reference to the license in the source file header is not part of
> the license itself, it is a reference
Hi,
Interesting, right at the top, the page itself refers to the https
location nowadays. In the licensing FAQ also a reference to the https
version is endorsed, not the http version.
What maybe with this regards is a problem is the update of the
http:///www.apache.org/licenses to https in
On 2019-05-26, wrote:
> updated reference to license from http to https using find . -type f -exec
> sed -i
> s/http://www.apache.org/licenses/LICENSE-2.0/https://www.apache.org/licenses/LICENSE-2.0/
> {} \;
I'm afraid we can't do that. The license URL is part of the license
text, changing th
> Betreff: Re: Antlib SVN and antunit Java versions
>
>
> On 19/12/18 11:29 PM, Stefan Bodewig wrote:
> > On 2018-12-18, Jaikiran Pai wrote:
> >
> >> One option in similar cases that we have employed in other jobs is
> to
> >> configure the Java system p
supported in a Java release after Java 1.5.
> I'd be in favor of updating the jobs. Nobody would build releases using
> Java 1.5 either, I guess.
Done. I have updated the jobs of antlib svn and antunit to use Java 8 to
build it.
>
>> At a more higher level, I think it'
On 2018-12-18, Jaikiran Pai wrote:
> One option in similar cases that we have employed in other jobs is to
> configure the Java system property -Dhttps.protocols to "TLSv1.2". But
> this version of TLS is only supported in a Java release after Java 1.5.
I'd be in favor of updating the jobs. Nobod
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 [
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 not to let
> clients with
> lower TLS versions (lesser
While looking at some of our Jenkins jobs, to reconfigure them to use
gitbox (wherever necessary), I notice that there are 2 jobs[1][2] which
are for Antlib SVN and Antunit libraries. Both these jobs are configure
for JDK 5, because those projects target Java 5 as the minimal runtime.
However, the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Apache Ant Team is pleased to announce the releases of Apache
AntUnit 1.4.
Apache AntUnit is an Antlib that provides a test framework for Apache
Ant tasks and types.
This release fixes a few race-conditions in LogCapturer and the
br-template
On 2018-06-24, Gintautas Grigelionis wrote:
> On Sun, 24 Jun 2018 at 14:38, Stefan Bodewig wrote:
>> So if we went to a JUnit 4 only model in antlib-commons with what you
>> describe this would require the Antlib that updated to a new
>> antlibs-commons version to change all existing JUnit tests
Hi all
with +1s by Maarten Coene, Stefan Bodewig, Gintautas Grigelionis,
Jaikiran Pai and no other votes the vote has passed.
I'll publish the artifacts and announce the release later today.
Stefan
-
To unsubscribe, e-mail: dev
+1.
- Downloaded the .tar.gz binary
- Checked some of the docs/manual
- Ran a simple project using this released version
- Checked the NOTICE file
All looks fine.
-Jaikiran
On 22/06/18 11:02 AM, Stefan Bodewig wrote:
Hi all
this is the third RC for AntUnit 1.4 with the problems Gintas
+1 (let's save JUnit 4 for the future :-)
On Fri, 22 Jun 2018 at 07:32, Stefan Bodewig wrote:
> Hi all
>
> this is the third RC for AntUnit 1.4 with the problems Gintas identified
> fixed.
>
> tag:
>
> https://git-wip-us.apache.org/repos/asf?p=an
On Sun, 24 Jun 2018 at 14:38, Stefan Bodewig wrote:
> So if we went to a JUnit 4 only model in antlib-commons with what you
> describe this would require the Antlib that updated to a new
> antlibs-commons version to change all existing JUnit tests?
>
My point was that should some antlib start us
On 2018-06-22, Stefan Bodewig wrote:
> vote will be open for 72 hours and not close before 2018-06-25 05:30 UTC.
making my own vote explicit
+1
Stefan
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional com
rong.
> BuildFileRule is necessary when test case no longer extend BuildFileRule
> which extends TestCase which is JUnit 3,
So if we went to a JUnit 4 only model in antlib-commons with what you
describe this would require the Antlib that updated to a new
antlibs-commons version to change all
On Sun, 24 Jun 2018 at 12:43, Stefan Bodewig wrote:
> On 2018-06-24, Gintautas Grigelionis wrote:
> > Actually, the targets are written in a way that checks explicitly for
> > JUnit 3. Should they be rewritten to check for JUnit 4, the baseline
> > has to be moved to all the way Ant 1.9.5 becaus
On 2018-06-24, Gintautas Grigelionis wrote:
> On Fri, 22 Jun 2018 at 09:45, Stefan Bodewig wrote:
>> On 2018-06-22, Gintautas Grigelionis wrote:
>>> Well, setup-for-junit-tests states that JUnit is not available and
>>> quits.
>> So it lacks a dependency on resolve.
>>> I'd like to understand
After looking at build rules, I realised that full support for JUnit 4
would require all antlibs
(and AntUnit in particular) to depend on Ant 1.9.5; however, the rules are
set in antlibs-common,
so maybe It's worth a separate discussion.
Gintas
On Fri, 22 Jun 2018 at 09:00, Maarten Coene
On Fri, 22 Jun 2018 at 09:45, Stefan Bodewig wrote:
> On 2018-06-22, Gintautas Grigelionis wrote:
>
> > Well, setup-for-junit-tests states that JUnit is not available and
> > quits.
>
> So it lacks a dependency on resolve.
>
> > I'd like to understand why setup targets are there at all.
>
> They
Github user twogee commented on the pull request:
https://github.com/apache/ant-antlibs-antunit/commit/f66f1178dcb42af44f4008493262782afe7c9f4d#commitcomment-29461462
In README:
In README on line 23:
BTW, JUnit 4 would require Java 5, too
Github user bodewig commented on the pull request:
https://github.com/apache/ant-antlibs-antunit/commit/f66f1178dcb42af44f4008493262782afe7c9f4d#commitcomment-29461360
In README:
In README on line 23:
Possibly :-) - I think the index.html says something different and the
Github user twogee commented on the pull request:
https://github.com/apache/ant-antlibs-antunit/commit/f66f1178dcb42af44f4008493262782afe7c9f4d#commitcomment-29461325
In README:
In README on line 23:
Really? ð®
On 2018-06-22, Gintautas Grigelionis wrote:
> On Fri, 22 Jun 2018 at 07:22, Stefan Bodewig wrote:
>> On 2018-06-21, Gintautas Grigelionis wrote:
>>> P.S. I'm struggling to understand why "ant test" of antlibs bails
>>> because "compile-tests" goes "setup-for-junit-tests, antlib, resolve"
>>> rat
On Fri, 22 Jun 2018 at 07:22, Stefan Bodewig wrote:
> On 2018-06-21, Gintautas Grigelionis wrote:
> > 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 ret
+1
Maarten
Van: Stefan Bodewig
Aan: dev@ant.apache.org
Verzonden: vrijdag 22 juni 7:32 2018
Onderwerp: [VOTE] Release AntUnit 1.4 based on RC3
Hi all
this is the third RC for AntUnit 1.4 with the problems Gintas identified
fixed.
tag:
https://git-wip-us.apache.org/repos/asf
Hi all
this is the third RC for AntUnit 1.4 with the problems Gintas identified
fixed.
tag:
https://git-wip-us.apache.org/repos/asf?p=ant-antlibs-antunit.git;a=tag;h=fb7a42470f8a6de50686f37519e27a068c576606
tarballs:
https://dist.apache.org/repos/dist/dev/ant/antlibs/antunit
update them.
> Shouldn't antlibs be baselined to something more recent?
I'd say yes for any Antlib that was under active development - i.e. at
best AntUnit and Compress (which is my pet project but likely not used
by many people).
> P.S. I'm struggling to understand why "ant tes
On Thu, 21 Jun 2018 at 11:17, Stefan Bodewig 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
I think moving to Ant 1.8.x would be a better option, given the
relatively low chances of it causing any issues.
-Jaikiran
On 21/06/18 2:47 PM, Stefan Bodewig 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 p
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
pres
POM template has inconsistent Ant versions, 1.7.1 in compile scope and
1.8.1 in provided scope.
Gintas
On Thu, 21 Jun 2018 at 08:57, Stefan Bodewig wrote:
> Hi all
>
> this is the second RC for AntUnit 1.4 with the problems Jaikiran
> identified fixed.
>
> tag:
&
Hi all
this is the second RC for AntUnit 1.4 with the problems Jaikiran
identified fixed.
tag:
https://git-wip-us.apache.org/repos/asf?p=ant-antlibs-antunit.git;a=tag;h=21c61e523c767bd1433544596478e9af7ce98858
tarballs:
https://dist.apache.org/repos/dist/dev/ant/antlibs/antunit
On 2018-06-19, Jaikiran Pai wrote:
> I don't know if the copyright year issue should warrant a new vote. If it
> doesn't, then it's a +1 for this release from me.
I'm afraud it does. Strange this splipped through as it is one of the
things I check when vetting releases other people have
cut. Ove
- Downloaded the tarballs (both source and binaries). Installed locally.
- Verified the checksum file. All fine.
- Ran a few antunit tests via simple Ant build files. All fine.
This all looked fine. There are some minor issues though:
1. The NOTICE file copyright year is 2005-2014
2. The
On 2018-06-18, Stefan Bodewig wrote:
> Hi all
> there haven't been big changes but the race condition has been nagging
> us, so I've prepared artifacts to release them as AntUnit 1.4.
> tag:
>
> https://git-wip-us.apache.org/repos/asf?p=ant
Hi all
there haven't been big changes but the race condition has been nagging
us, so I've prepared artifacts to release them as AntUnit 1.4.
tag:
https://git-wip-us.apache.org/repos/asf?p=ant-antlibs-antunit.git;a=tag;h=c4af2e6f2ff632b896a15e7611e01b36bf4eada9
tarballs:
+1
Jan
> -Ursprüngliche Nachricht-
> Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
> Gesendet: Montag, 4. Juni 2018 10:32
> An: dev@ant.apache.org
> Betreff: Re: AntUnit Bug Causing Jenkins Failures
>
> Sounds fine to me.
>
> -Jaikiran
>
>
>
version of AntUnit and push that to Ant's
lib/optional - and then monitor Jenkins for a while validating the
fix. And if it seems to work, cut a new AntUnit release.
This would break build jobs that try to populate lib/optional from
existing repos (either via fetch.xml or Ivy or whatever) until t
Hi all
one of the recurring issues that make Jenkins builds fail is a
thread-safety bug in AntUnit's log capturing code. This is supposed to
be fixed in AntUnit's master branch.
I propose to build an alpha version of AntUnit and push that to Ant's
lib/optional - and then monito
Github user jaikiran commented on the issue:
https://github.com/apache/ant-antlibs-antunit/pull/1
Thank you. Merged.
---
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev
Github user asfgit closed the pull request at:
https://github.com/apache/ant-antlibs-antunit/pull/1
---
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
Github user bodewig commented on the issue:
https://github.com/apache/ant-antlibs-antunit/pull/1
looks good to me
---
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h
GitHub user jaikiran opened a pull request:
https://github.com/apache/ant-antlibs-antunit/pull/1
Avoid potential thread safety issues in LogCapturer
This commit is prompted by the exception I saw in one of the Ant Jenkins
jobs which failed with:
```
/home/jenkins
On 2016-07-11, Stefan Bodewig wrote:
> On 2016-07-11, Stefan Bodewig wrote:
>> On 2016-06-24, Jan Matèrne (jhm) wrote:
>>> I try to understand, why AntUnit is failing on the CI ...
>>> (Works on my Win7 machine).
>> It looks as if the current working director
On 2016-07-11, Stefan Bodewig wrote:
> On 2016-06-24, Jan Matèrne (jhm) wrote:
>> I try to understand, why AntUnit is failing on the CI ...
>> (Works on my Win7 machine).
> It looks as if the current working directory is not what one would
> expect. In your configuration us
On 2016-06-24, Jan Matèrne (jhm) wrote:
> I try to understand, why AntUnit is failing on the CI ...
> (Works on my Win7 machine).
It looks as if the current working directory is not what one would
expect. In your configuration using "-f" it failed to find the build
file, and in m
I try to understand, why AntUnit is failing on the CI ...
(Works on my Win7 machine).
Jan
> -Ursprüngliche Nachricht-
> Von: Apache Jenkins Server [mailto:jenk...@builds.apache.org]
> Gesendet: Freitag, 24. Juni 2016 12:40
> An: notificati...@ant.apache.org
> Betreff:
The job is ready.
But the last build gives me an error:
https://builds.apache.org/view/A-D/view/Ant/job/AntLib-antunit/lastBuild/con
sole
[au:antunit] Build File:
/x1/jenkins/jenkins-slave/workspace/AntLib-antunit/src/tests/antunit/assertR
esourceExists-test.xml
[au:antunit] Tests run: 4
806749177 -> 39ad231a2
>
>
> upgrade AntUnit
>
>
> Project: http://git-wip-us.apache.org/repos/asf/ant/repo
> Commit: http://git-wip-us.apache.org/repos/asf/ant/commit/39ad231a
> Tree: http://git-wip-us.apache.org/repos/asf/ant/tree/39ad231a
> Diff: http://git-wip-us
Hi all,
with +1s by
Nicolas Lalevée
Antoine Levy Lambert
Peter Reilly
and my own implied +1 and no other binding votes the vote has passed.
I'll publish all artiefacts and update the site/announce the release
after mirrors have caught up.
Thanks
Stefan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Apache AntUnit Ant Library provides a test framework for Ant tasks
and types.
AntUnit 1.3 adds new assertions that deal with non-file resources better
than the existing ones of 1.2 and provides additional access to the log
created during tests
+1
Per A. Blaasmo
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
t :
> >
> >> Hi all,
> >>
> >> delayed because I wanted to wait for mails to arrive again.
> >>
> >> Antunit 1.3 RC1 is available for review here:
> >> https://dist.apache.org/repos/dist/dev/ant/antlibs/antunit/
> >> (svn revi
+1 for me
Antoine
On May 11, 2014, at 11:07 AM, Nicolas Lalevée
wrote:
> +1 for me
>
> Nicolas
>
> Le 11 mai 2014 à 12:42, Stefan Bodewig a écrit :
>
>> Hi all,
>>
>> delayed because I wanted to wait for mails to arrive again.
>>
>&
+1 for me
Nicolas
Le 11 mai 2014 à 12:42, Stefan Bodewig a écrit :
> Hi all,
>
> delayed because I wanted to wait for mails to arrive again.
>
> Antunit 1.3 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/ant/antlibs/antunit/
>
Hi all,
delayed because I wanted to wait for mails to arrive again.
Antunit 1.3 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/ant/antlibs/antunit/
(svn revision 5298)
Maven artifacts are here:
https://repository.apache.org/content/repositories
FRA-1983?jql=project%20%3D%20INFRA%2
> 0AND%20text%20~%20%22ant%20git%22
>
>
>> -Ursprüngliche Nachricht-
>> Von: Stefan Bodewig [mailto:bode...@apache.org]
>> Gesendet: Dienstag, 6. Mai 2014 08:55
>> An: dev@ant.apache.org
>> Betreff: Cutting AntUnit 1.3
--
> Von: Stefan Bodewig [mailto:bode...@apache.org]
> Gesendet: Dienstag, 6. Mai 2014 08:55
> An: dev@ant.apache.org
> Betreff: Cutting AntUnit 1.3
>
> Hi all
>
> after a few years (really) of dormancy I've applied a few patches to
> AntUnit and would like to cut a new
Hi all
after a few years (really) of dormancy I've applied a few patches to
AntUnit and would like to cut a new release. I still need to fix the
code introduced in 56470 since at least one test in Ant's testsuite
relies on the old behavior, so breaking BWC is a problem here.
How
Much appreciated Stefan.
It's a great tool; I wrote an ant script recently to auto build and
deploy oracle databases from an SVN repository. It was a monster of a
script and the AntUnit scripts I wrote for it were indispensable!
Regards,
Chris Holman
http://uk.linkedin.com/in/chrisdh
On 2014-04-29, wrote:
> Hi Stephan: nod of appreciation for AntUnit :-),
Oh, many people have contributed.
> Is the code base quiet because there are no further changes required,
> or is there an alternative that I should use instead?
Probably because it does what is needed by Ant i
Hi Stephan: nod of appreciation for AntUnit :-),
Is the code base quiet because there are no further changes required,
or is there an alternative that I should use instead?
Being able to dump the logs is very handy when debugging the
tests/build scripts :-)
If the LogCapturer was only
On 2014-04-29, wrote:
> Good point on the rationale behind this functionality. Not sure what
> reason there could be to have the log reported as a single line.
> Though I can imagine existing scripts working round it by inserting
> EOL characters at the end of an echo statement.
It's been years
Antoine
On Apr 28, 2014, at 4:05 PM, chris.hol...@awltux.com wrote:
Hi,
I realise the AntUnit project is pretty quiet, but I have a fix I'd
like to submit.
The LogCapturer currently concatenates all messages onto the same
line. Not very readable when you send the log to file.
I
submit a change for AntUnit?
>
> Hi,
>
> I realise the AntUnit project is pretty quiet, but I have a fix I'd
> like to submit.
>
> The LogCapturer currently concatenates all messages onto the same line.
> Not very readable when you send the log to file.
>
-u .
Regards,
Antoine
On Apr 28, 2014, at 4:05 PM, chris.hol...@awltux.com wrote:
> Hi,
>
> I realise the AntUnit project is pretty quiet, but I have a fix I'd like to
> submit.
>
> The LogCapturer currently concatenates all messages onto the same line. Not
> very
Hi,
I realise the AntUnit project is pretty quiet, but I have a fix I'd
like to submit.
The LogCapturer currently concatenates all messages onto the same
line. Not very readable when you send the log to file.
I've added an EOL to each append in method:
LogCapturer.mes
On 2014-01-02, Jesse Glick wrote:
> On Thu, Jan 2, 2014 at 2:22 AM, wrote:
>+try {
>+jarFile = new JarFile(file);
>+} catch (ZipException notAJar) {
>+// raised if a file that is not a ZIP
>
On Thu, Jan 2, 2014 at 2:22 AM, wrote:
> +try {
> +jarFile = new JarFile(file);
> +} catch (ZipException notAJar) {
> +// raised if a file that is not a ZIP
Would also be thrown if the file _i
Looks like Ant-Build-Matrix is finally fixed! I have reenabled mail sent to
notificati...@ant.apache.org so we can track regressions.
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev
Le 9 avr. 2012 à 07:35, Stefan Bodewig a écrit :
> Hi,
>
> by now I've managed to reduce the number of failing tests to 0 on two of
> the six build configurations. What remains:
>
> * a failure that only happens on Java5 machines WRT a closed ZIP. I'll
> re-investigate what is going on here
Hi,
by now I've managed to reduce the number of failing tests to 0 on two of
the six build configurations. What remains:
* a failure that only happens on Java5 machines WRT a closed ZIP. I'll
re-investigate what is going on here tomorrow
* some stange host-name resolution issue with the Ubun
> Author: hibou
> Date: Sun Mar 11 16:06:35 2012
> New Revision: 537
>
> Log:
> populate the release dist of ant
>
> Added:
>release/ant/KEYS
>release/ant/README.html
>release/ant/RELEASE-NOTES-1.8.3.html
>release/ant/antlibs/
>release/ant/
On 2012-02-24, Jesse Glick wrote:
> On 02/24/2012 12:12 AM, Stefan Bodewig wrote:
>> It is supposed to be used via ./build.sh antunit-tests.
> Ah. But when I do that, I get failures that I do not get when I use
> ./dist/bin/ant -lib lib/optional antunit-tests, e.g.:
> Build F
On 02/24/2012 12:12 AM, Stefan Bodewig wrote:
It is supposed to be used via ./build.sh antunit-tests.
Ah. But when I do that, I get failures that I do not get when I use
./dist/bin/ant -lib lib/optional antunit-tests, e.g.:
Build File: .../src/tests/antunit/bugfixes/br50866/br50866-test.xml
On 2012-02-23, Jesse Glick wrote:
> ...though it hangs in taskdefs/exec/apply-test.xml:
I've never seen it hang but some of the exec tests fail for me regularly
as well (as they occasionaly do on Gump).
Stefan
-
To unsubscribe,
On 2012-02-23, Jesse Glick wrote:
> On 02/23/2012 04:09 PM, Jesse Glick wrote:
>> $ ant -lib lib/optional/ant-antunit-1.2.jar antunit-tests
> Never mind, just figured out that you need to use
> $ ./dist/bin/ant ...
> to actually test trunk code! Maybe build.xml should detect
...though it hangs in taskdefs/exec/apply-test.xml:
apply-test.antunit:
Build File: .../src/tests/antunit/taskdefs/exec/apply-test.xml
...
"main" prio=10 tid=0x091c7c00 nid=0x24e0 in Object.wait() [0xf6947000]
java.lang.Thread.State: WAITING (on object monitor)
On 02/23/2012 04:09 PM, Jesse Glick wrote:
$ ant -lib lib/optional/ant-antunit-1.2.jar antunit-tests
Never mind, just figured out that you need to use
$ ./dist/bin/ant ...
to actually test trunk code! Maybe build.xml should detect this somehow and
warn you (though of course it would be
I get a bunch of test failures in trunk using
$ ant -lib lib/optional/ant-antunit-1.2.jar antunit-tests
under JDK 7u3, Ubuntu. Are these tests normally expected to pass?
-
To unsubscribe, e-mail: dev-unsubscr
d sending out the announcement.
>
> I'll also update the version of AntUnit in Ant's trunk.
>
> Stefan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Apache Ant Team is proud to announce the 1.2 release of Apache
AntUnit.
AntUnit is a library of task and types for Apache Ant that can be used
to perform functional tests using Ant build file. It is especially well
suited to test Ant tasks and
1 - 100 of 821 matches
Mail list logo
