+1.
- Downloaded the .tar.gz binary
- Installed locally, checked the NOTICE and some tasks' manuals. Look fine.
- Built some random existing Ant based projects using this new version.
All went fine.
-Jaikiran
On 19/06/18 12:38 PM, Stefan Bodewig wrote:
Hi all
I've created a n
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
+1.
- Downloaded the .tar.gz binary
- Checked some docs in the manual
- Used this new version to run builds against existing internal Ant
projects.
All went fine.
-Jaikiran
On 19/06/18 12:38 PM, Stefan Bodewig wrote:
Hi all
I've created a new release candidate for 1.10.4 with a
Thank you for running this release, Stefan.
-Jaikiran
On 22/06/18 9:09 PM, Stefan Bodewig wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Apache Ant Team is pleased to announce the releases of Apache Ant
1.9.12 and 1.10.4.
Apache Ant is a Java library and command-line tool that
+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
the workspace
* NEW: Support for storing credentials securely
Do you vote for the release of these binaries?
-Jaikiran
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
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?
-Jaikiran
On 28/06/18 9:05 AM, bugzi...@apache.org wrote:
https://bz.apache.org/bugzilla/show_bug.cgi?id=33169
Ranjeet
y purpose.
So I'll vote a -1 on this now. I know we have gone through 3 voting
rounds for this release, so thank you everyone for being patient and
testing out the binaries. I'll file this issue in JIRA and hopefully
spend some time in Eclipse this weekend to try and s
This vote is now officially cancelledfor the reasons noted below.
-Jaikiran
On 28/06/18 12:11 PM, Jaikiran Pai wrote:
On 27/06/18 10:12 PM, Nicolas Lalevée wrote:
Since there is a work around (hitting refresh after resolve) and it
is an RC, we could ship it like that and fix it later. But
the
isLeadingPath API solely based on the names of that passed files rather
than their actual resolved location on the filesystem? I haven't yet
tried it out myself to have a more clearer understanding of how it will
end up behaving in the context that we use this API.
-Jaikiran
O
On 28/06/18 8:37 PM, Stefan Bodewig wrote:
On 2018-06-28, Jaikiran Pai wrote:
However, looking at the FileUtils#isLeadingPath(...) implementation, I
wonder why it even uses normalize. Given that the goal of that API (as
stated in the javadoc) is to figure out if one path leads the other,
to
nt and may not even be valid. I'm going to
build the latest changes of Ant give it a try against a bunch of my
theoretical use cases and see if my suspicions are really valid or not.
[1]
https://github.com/apache/ant/commit/6a41d62cb9ab4e640b72cb4de42a6c211dea645d
-Jaikiran
On 0
nless someone else sees any issues, I think we can go
ahead and do the release that you had planned for.
-Jaikiran
On 03/07/18 1:16 PM, Stefan Bodewig wrote:
On 2018-07-02, Stefan Bodewig wrote:
On 2018-07-02, Jaikiran Pai wrote:
I just checked the commits related to this and it looks mostly
co
On 01/07/18 6:35 PM, Nicolas Lalevée wrote:
Le 28 juin 2018 à 08:41, Jaikiran Pai a écrit :
On 27/06/18 10:12 PM, Nicolas Lalevée wrote:
Since there is a work around (hitting refresh after resolve) and it is an RC,
we could ship it like that and fix it later. But due to the automatic
playground and forcing it on the rest of
the community. At this point, I personally believe that reviewing these
meaningless changes is a waste of time and energy. I'm in favour of
rolling back the entire commit set if that's what it takes.
-Jaikiran
.
-Jaikiran
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
On 05/07/18 2:42 PM, Stefan Bodewig wrote:
On 2018-07-05, Jaikiran Pai wrote:
I personally believe that reviewing these meaningless changes is a
waste of time and energy. I'm in favour of rolling back the entire
commit set if that's what it takes.
+1
although reverting the commi
s that had gone in between the trailing
whitespace, force updated merge commits on master. Reviewed this
comparison diff and it looked fine and correct to me. Pushed this state
to "master" branch of upstream repo.
At this point, these branches are in a state where they can be used for
us to this.
-Jaikiran
On 06/07/18 5:19 PM, j...@apache.org wrote:
Hello all
Just for your info, please take into consideration for a rollback or
not descision (I am neither happy with the commit, nor happy with a
rollback and therefore am 0 on rollback or not):
I have written a small ch
with this new version
(and fails with previous 1.9.x released version) to verify the
https://bz.apache.org/bugzilla/show_bug.cgi?id=62164 issue:
src="http://downloads.sourceforge.net/easymock/easymock-3.2.zip";
dest="${basedir}/downloaded/"/>
-Jaikiran
quot;
feature of Java task works:
A.java:
public class A {
public static void main(final String[] args) throws Exception {
System.out.println("Hello Ant 1.10.5!");
}
}
Worked fine.
-Jaikiran
On 10/07/18 3:25 PM, Stefan Bodewig wrote:
Hi all
I&#x
to submit
bug reports, patches, or suggestions for improvement, see the Apache Ant
website https://ant.apache.org/
-Jaikiran Pai, on behalf of the Apache Ant community
signature.asc
Description: OpenPGP digital signature
Haven't checked the job, but why is this system property required to be set?
-Jaikiran
On 20/07/18 12:51 AM, Gintautas Grigelionis wrote:
> I'd like to add a Java option to Ivy builds -Dhttps.protocols=TLSv1.2 but I
> get
> This job's current authorization strategy d
if I ever
had those permissions or if it's something that changed with the recent
Jenkins upgrade.
-Jaikiran
On 20/07/18 1:34 PM, Gintautas Grigelionis wrote:
> My hypothesis is that Java 7 must have TLS version forced to 1.2 in order
> to avoid protocol errors when downloading new binari
I've committed a change[1] to handle this in the part where we trigger
the tutorial run.
[1]
https://github.com/apache/ant-ivy/commit/43ddccb859b94c79350ece7520af4c991c2bb5e6
-Jaikiran
On 24/07/18 10:53 PM, Gintautas Grigelionis wrote:
> Thank you for all attempts, the failure occur
There are a few more jobs that need to be reconfigured a bit to get them
working. I'm working with infra team to have that sorted out. Please
ignore the failure mails from those jobs for now.
-Jaikiran
On 25/07/18 10:30 AM, Jaikiran Pai wrote:
> I've committed a change[1] to handl
Almost all jobs that I know of have been taken care of now. There's a
"Ivy-tests-Windows" job which is pending, but for that I need some help
from infra team. I am discussing it with them separately and I expect it
to be resolved soon. I'll fix that job tomorrow.
-Jaikiran
On 25/07/18 6:45 PM, Jaikiran Pai wrote:
> Almost all jobs that I know of have been taken care of now. There's a
> "Ivy-tests-Windows" job which is pending, but for that I need some help
> from infra team. I am discussing it with them separately and I expect it
> to
I would like to test/import a few more projects (that Nicolas mentioned
in one the mails) locally into the latest upstream version of the IDE,
before starting a release. I have only tested a few so far.
-Jaikiran
On 28/07/18 2:28 PM, Gintautas Grigelionis wrote:
> Thanks, Jaikiran. Would you
Sure, will fix it this week. Right now, I don't have necessary
permissions to edit it.
-Jaikiran
On 05/08/18 8:58 PM, Gintautas Grigelionis wrote:
> There's one more Jenkins job failing due to outdated Ant, Ivy Check (
> https://builds.apache.org/view/All/job/Ivy-check/).
&g
Noted. Just waiting for the infra team to sort out the access issue.
-Jaikiran
On 12/08/18 2:28 AM, Gintautas Grigelionis wrote:
> Hi Jan and Jaikiran,
>
> looks like IvyDE trunk build needs attention, too (SSL protocol failure
> when resolving Checkstyle).
>
> Thanks, Gintas
Which vendor and version of Java is this?
-Jaikiran
On 13/08/18 6:39 PM, Simon IJskes - QCG wrote:
> I still have problems installing ant binary distribution (1.10.5) and
> using the email task.
>
> I've tried to complete the binary directories by running either:
>
>
Yes, it looks like one of our changes broke this. We seem to just fetch
the mail API jar(s) and no longer fetch the jars which includethe
provider implementation(s). Can you please file a bug for this, in the
Ant bugzilla?
-Jaikiran
On 13/08/18 7:13 PM, Simon IJskes - QCG wrote:
> It looks l
I pushed a commit to both our 1.9.x and master branches to include a
change which should bring in the right jars as part of the fetch.
In near future, I'll try and update our mail task tests to be a bit more
robust for checking the basic usage of this task.
-Jaikiran
On 13/08/18 7:
Hi Simon,
Yes, you can file a bug. I'll update it to record that it's been handled
in an upcoming release. As usual, our nightly builds are available[1] to
test this fix, till the release is ready.
[1] https://builds.apache.org/job/Ant_Nightly/lastSuccessfulBuild/artifact/
-Jaikiran
Thank you for reporting the issue and testing the fix, Simon.
-Jaikiran
On 14/08/18 1:39 AM, Simon IJskes - QCG wrote:
> fix works. Thanks!
>
> On 08/13/2018 09:55 PM, Simon IJskes - QCG wrote:
>> https://bz.apache.org/bugzilla/show_bug.cgi?id=62621
>>
>> On 08/13/
h more intuitive and
gives me more control as well as a better read of what the test case
expects. Keeping that detail aside, I decided to use a particular coding
style that I was comfortable with when adding that code. The tests are
working fine. So what was the need to override that commit with a coding
style change? Is this how you are going to continue with your future
commits?
-Jaikiran
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
e been
> helpful in eventual migration to JUnit 5, too.
JUnit 5 migration isn't related to the commit I am talking about.
-Jaikiran
>
> Gintas
>
> On Wed, 15 Aug 2018 at 03:14, Jaikiran Pai wrote:
>
>> Gintas,
>>
>>
>> On 14/08/18 10:14 PM, gin...@apa
Is that the reason you moved to this style of coding? I don't plan to
use ExpectedException or that style of testing in code that I write. Are
you going to keep overriding such commits?
-Jaikiran
On 15/08/18 1:18 PM, Gintautas Grigelionis wrote:
> Jaikiran,
>
> your code all
/commit/ffb80b688a12d4e60ab4be466ec0b3e396bb0078
-Jaikiran
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
ly,label_exp=Windows/lastCompletedBuild/testReport/src.tests.antunit.taskdefs/tstamp-test_xml/testMagicProperty/
-Jaikiran
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
Hi Stefan,
On 22/08/18 12:00 AM, Stefan Bodewig wrote:
> On 2018-08-16, Jaikiran Pai wrote:
>
>> However, I would like some inputs on whether such support for setting
>> the system properties in a non-forked execution should be at the
>> junitlauncher task level
More of a FYI - The URLResolverTest failures, in this list, appear to be
my fault, introduced in a commit I pushed this week. I will take a look
tonight to see what the issue there is and fix (or rollback) my changes.
-Jaikiran
On 24/08/18 12:22 PM, Apache Jenkins Server wrote:
> See
>
I am going to disable this JDK 10 b46 against Windows job. It's been
failing for a while and all due to infrastructure issues. I don't see
any other JDK 10 (Windows) selection option either. Any objections to
disabling these tests against this version, on Windows?
-Jaikiran
On 27/08/
://bugs.openjdk.java.net/browse/JDK-8209965
-Jaikiran
On 24/08/18 2:35 PM, Rory O'Donnell wrote:
> Hi Stefan,
>
> *JDK 11 build 28 is our first JDK 11 Release Candidate [1]
> *
>
> * JDK 11 Early Access build 28 is available at : - jdk.java.net/11/
>
> *FOSS fixes in recent
anges aren't a fix.
-Jaikiran
On 29/08/18 11:34 AM, gin...@apache.org wrote:
> Repository: ant-ivy
> Updated Branches:
> refs/heads/master d976a4a27 -> fd81f4461
>
>
> Update the release notes
>
> Project: http://git-wip-us.apache.org/repos/asf/ant-ivy/repo
&
Hi Simon,
Is there a specific issue that you want to be part of the release?
-Jaikiran
On 06/09/18 2:20 AM, Simon IJskes - QCG wrote:
> Hi,
>
> Is it possible to cast a new release? If possible within 2 weeks?
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+N
n
to initiate the vote next month (November) just to allow a few more
weeks for anyone to step forward if they would like to maintain the
project.
-Jaikiran
On 22/08/23 9:32 pm, Stefan Bodewig wrote:
Hi all
before I get to the actual content of this mail:
* I'm cross-posting to three l
Hello David,
I ran the Ant testsuite[1] against JDK 24 EA build 24-ea+21-2447 and no
unexpected failures were encountered.
[1]
https://ci-builds.apache.org/job/Ant/job/Ant%20Master%20Linux%20(latest%20EA%20JDK)/54/
-Jaikiran
On 25/10/24 7:58 pm, David Delabassee wrote:
Welcome to the
includeantruntime="no">
@@ -371,8 +367,7 @@
@@ -388,8 +383,7 @@
destfile="${test.dir}/org/apache/ivy/core/settings/custom-resolver.jar"
I haven't tried any else than building the jar with this change.
-Jaikir
plan to retire Ivy has been abandoned. As
usual, it will be very helpful if others, especially those who use Ivy
and have some experience with it, contribute to the project.
-Jaikiran
On 17/11/24 4:10 pm, Maarten Coene wrote:
Hi all,
good news, there will be no vote to retire the project for n
+1
Downloaded the apache-ivy-2.5.3-bin.zip from the dist location. Checked
the NOTICE. Ran an old Ivy project using JDK 8. No issues encountered.
-Jaikiran
On 23/12/24 6:41 pm, Maarten Coene wrote:
Hi all,
I have built a release candidate for Ivy 2.5.3
The git tag of this release is
https://github.com/apache/ant-ivy.git as the repo and then
triggered a job. That has fetched the latest and the build is in
progress (build number 55).
We will have to check why the gitbox repo is either missing that new
commit or not fetching the latest. I will check later today.
-Jaikiran
On 26/03
The gitbox repo is now up-to-date.
-Jaikiran
On 27/03/25 12:49 am, Maarten Coene wrote:
Thanks Jaikiran!
If I can do something to help you finding the issue, let me know.
Maarten
On Wed, Mar 26, 2025 at 1:50 AM Jaikiran Pai wrote:
Hello Maarten,
The job was correctly configured to use
ling lists is
available here
https://maven.apache.org/resolver-ant-tasks/mailing-lists.html
-Jaikiran
On 17/06/25 10:31 pm, Per Nyfelt wrote:
Hi,
I created a PR here
https://github.com/apache/maven-resolver-ant-tasks/pull/56
It fixes the issue reported here:
https://github.com/apache/mave
ests. I will do that at a later date.
-Jaikiran
On 06/06/25 12:59 pm, David Delabassee wrote:
Welcome to the June installment of the OpenJDK Quality Outreach newsletter.
JDK 25, scheduled for General Availability on September 16, 2025, has entered
Rampdown Phase One (RDP1)[1]. The JDK 25 featu
veral years. Looking forward to the
continued usage of this build tool in the Java ecosystem.
-Jaikiran
On 27/06/25 1:35 am, Stefan Bodewig wrote:
https://lists.apache.org/thread/3co2lfvvm9dcottnq8tsn3gs34z6v3xt
what a ride.
It is probably too late to put together some kind of birthday
celebration
Hello Stefan,
On 26/06/25 5:16 pm, Stefan Bodewig wrote:
> On 2025-06-26, Jaikiran Pai wrote:
>
>> However on Windows we are seeing a large number of test failures. I
>> looked into those failures and those all relate to the "heads up"
>> section in your mai
/Ant%20Master%20Linux%20(latest%20EA%20JDK)/59/
Please take a look at those 2 commits and I would like to hear if those
look OK or would need to be handled differently. The newly proposed JDK
property isn't used in these changes and we don't need to set it at
least for the current te
Thank you Roger and Stefan for the reviews.
-Jaikiran
On 02/07/25 6:11 am, Roger Whitcomb wrote:
Hi Jaikiran,
Looked through the changes and they look good and simple and robust. I like not
having to use the new system property.
Thanks,
~Roger Whitcomb
On Jul 1, 2025, at 9:52 AM, Jaikiran
701 - 760 of 760 matches
Mail list logo
