[jira] [Assigned] (IVY-1609) Removal of WARN deprecation when not valid

2019-10-10 Thread Jaikiran Pai (Jira)
[ https://issues.apache.org/jira/browse/IVY-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaikiran Pai reassigned IVY-1609: - Assignee: Jaikiran Pai > Removal of WARN deprecation when not valid >

[jira] [Commented] (IVY-1609) Removal of WARN deprecation when not valid

2019-10-10 Thread Jaikiran Pai (Jira)
[ https://issues.apache.org/jira/browse/IVY-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949137#comment-16949137 ] Jaikiran Pai commented on IVY-1609: --- Hello Greg, Are you saying that this message gets logged when the

[jira] [Assigned] (IVY-1610) Invalid collision should not error retrieve

2019-10-10 Thread Jaikiran Pai (Jira)
[ https://issues.apache.org/jira/browse/IVY-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaikiran Pai reassigned IVY-1610: - Assignee: Jaikiran Pai > Invalid collision should not error retrieve >

[jira] [Resolved] (IVY-1610) Invalid collision should not error retrieve

2019-10-10 Thread Jaikiran Pai (Jira)
[ https://issues.apache.org/jira/browse/IVY-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaikiran Pai resolved IVY-1610. --- Fix Version/s: master Resolution: Fixed I think this is the same as what Sebastian mentioned in

[jira] [Commented] (IVY-1586) Retrieves test-library instead of binary-library

2019-10-10 Thread Jaikiran Pai (Jira)
[ https://issues.apache.org/jira/browse/IVY-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949134#comment-16949134 ] Jaikiran Pai commented on IVY-1586: --- [~snagel], I just pushed a fix which I believe should fix the

[ant-ivy] branch master updated: IVY-1586 IVY-1610 Make sure that empty value of "classifier" in pom.xml is considered the same as classifier not being specified

2019-10-10 Thread jaikiran
This is an automated email from the ASF dual-hosted git repository. jaikiran pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/ant-ivy.git The following commit(s) were added to refs/heads/master by this push: new 400cb51 IVY-1586 IVY-1610 Make sure that

[jira] [Commented] (IVY-1610) Invalid collision should not error retrieve

2019-10-10 Thread Jaikiran Pai (Jira)
[ https://issues.apache.org/jira/browse/IVY-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949094#comment-16949094 ] Jaikiran Pai commented on IVY-1610: --- Hello Greg, Is there a ivy.xml that you can attach which reproduces

[jira] [Commented] (IVY-1611) Need embedded way of getting log messages

2019-10-10 Thread Jaikiran Pai (Jira)
[ https://issues.apache.org/jira/browse/IVY-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949089#comment-16949089 ] Jaikiran Pai commented on IVY-1611: --- > In 2.4.x - this was possible : > Main.setLogger(new

Jenkins build is back to stable : Ant-Build-Matrix-master-Linux » xenial,JDK 11 (latest) #1567

2019-10-10 Thread Apache Jenkins Server
See

Jenkins build became unstable: Ant Master Compatibility Linux » xenial,JDK 1.8 (latest) #22

2019-10-10 Thread Apache Jenkins Server
See

[ant] branch master updated: bz-63827 Minor change

2019-10-10 Thread jaikiran
This is an automated email from the ASF dual-hosted git repository. jaikiran pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/ant.git The following commit(s) were added to refs/heads/master by this push: new a7a1906 bz-63827 Minor change a7a1906 is

Jenkins build is back to stable : Ant-Build-Matrix-master-Linux » xenial,JDK 1.9 (latest) #1566

2019-10-10 Thread Apache Jenkins Server
See

Jenkins build is back to stable : Ant Master Compatibility Linux » xenial,JDK 13 (latest) #21

2019-10-10 Thread Apache Jenkins Server
See

Jenkins build is back to stable : Ant Master Compatibility Linux » xenial,JDK 1.9 (latest) #21

2019-10-10 Thread Apache Jenkins Server
See

Jenkins build is back to stable : Ant Master Compatibility Linux » xenial,JDK 10 (latest) #21

2019-10-10 Thread Apache Jenkins Server
See

Jenkins build became unstable: Ant-Build-Matrix-master-Linux » xenial,JDK 1.9 (latest) #1565

2019-10-10 Thread Apache Jenkins Server
See

Jenkins build became unstable: Ant-Build-Matrix-master-Linux » xenial,JDK 11 (latest) #1565

2019-10-10 Thread Apache Jenkins Server
See

Jenkins build became unstable: Ant Master Compatibility Linux » xenial,JDK 13 (latest) #20

2019-10-10 Thread Apache Jenkins Server
See

[Bug 63827] LegacyXmlResultFormatter of JUnitLauncher Task does not write StackTrace of failure

2019-10-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63827 --- Comment #4 from Jaikiran Pai --- > Just one question, why using "cause.get()" when "t" is already a final > variable (of "cause.get()")? Because working on too many unrelated things and not focusing enough for a "simple fix" :) You are

Jenkins build became unstable: Ant Master Compatibility Linux » xenial,JDK 1.9 (latest) #20

2019-10-10 Thread Apache Jenkins Server
See

[Bug 63827] LegacyXmlResultFormatter of JUnitLauncher Task does not write StackTrace of failure

2019-10-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63827 --- Comment #3 from mse...@guh-software.de --- Great :) Just one question, why using "cause.get()" when "t" is already a final variable (of "cause.get()")? -- You are receiving this mail because: You are the assignee for the bug.

Jenkins build is back to stable : Ant Master Compatibility Linux » xenial,JDK 12 (latest) #20

2019-10-10 Thread Apache Jenkins Server
See

[Bug 63827] LegacyXmlResultFormatter of JUnitLauncher Task does not write StackTrace of failure

2019-10-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63827 Jaikiran Pai changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[ant] branch master updated: bz-63827 Print out stacktrace in "legacy-xml" when the test is aborted too

2019-10-10 Thread jaikiran
This is an automated email from the ASF dual-hosted git repository. jaikiran pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/ant.git The following commit(s) were added to refs/heads/master by this push: new 02ffb25 bz-63827 Print out stacktrace in

Jenkins build became unstable: Ant Master Compatibility Linux » xenial,JDK 10 (latest) #20

2019-10-10 Thread Apache Jenkins Server
See

[Bug 63827] LegacyXmlResultFormatter of JUnitLauncher Task does not write StackTrace of failure

2019-10-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63827 --- Comment #1 from mse...@guh-software.de --- Created attachment 36816 --> https://bz.apache.org/bugzilla/attachment.cgi?id=36816=edit Patch which adds Stacktrace to failures & abortions (without filtering the stacktrace) -- You are

[ant] branch master updated: bz-63827 Print out the stacktrace when writing out the XML from "legacy-xml" formatter of junitlauncher

2019-10-10 Thread jaikiran
This is an automated email from the ASF dual-hosted git repository. jaikiran pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/ant.git The following commit(s) were added to refs/heads/master by this push: new 23a3665 bz-63827 Print out the stacktrace when

[Bug 63827] New: LegacyXmlResultFormatter of JUnitLauncher Task does not write StackTrace of failure

2019-10-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63827 Bug ID: 63827 Summary: LegacyXmlResultFormatter of JUnitLauncher Task does not write StackTrace of failure Product: Ant Version: 1.10.7 Hardware: PC Status: