GitHub user jaikiran opened a pull request:
https://github.com/apache/ant-ivy/pull/11
IVY-1499 Prevent potential NPE during retrieve
The commit here adds a null check to prevent a potential NPE that is
reported in JIRA https://issues.apache.org/jira/browse/IVY-1499
You can merge th
GitHub user jaikiran opened a pull request:
https://github.com/apache/ant-ivy/pull/12
IVY-1482 Fix potential NPE in XmlReportOutputter
The commit here adds a null check to prevent potential NPE reported in JIRA
https://issues.apache.org/jira/browse/IVY-1482
You can merge this pull
First off, I'm not an Ivy or Ant committer. The proposal that I make
below for an Ivy release is based on what was discussed in a recent mail
thread about the future of Ivy
https://www.mail-archive.com/dev@ant.apache.org/msg45078.html. There was
a suggestion that someone from community voluntee
A short report on status (and more detailed answers to Nicholas questions):
- the doc builds correctly once I clone ant-xooki repository on Github
into doc/xooki;
- the style clone on Github is empty; I did "wget -np -nd -r
https://svn.apache.org/repos/asf/ant/site/ivyde/sources/style/
Do we really need a beta release? If you're working on bugfixes first, then
a regular 2.4.1 release would be great. It would go through the normal
Apache release candidate process, and perhaps we could get some Gradle
developers to test it out as well since they still seem to be big users of
Ivy.
I'm fine calling it a 2.4.1. The only reason I mentioned it as a beta is to
iron out any issues involved in the process itself which, from what I read
in the other thread, might involve certain challenges for the first time.
-Jaikiran
On Sunday, December 11, 2016, Matt Sicker wrote:
> Do we real
Issues in the release process? Those would be handled by multiple release
candidates. People normally only use alphas and betas for new projects or
new major versions of projects at Apache.
On 11 December 2016 at 19:53, J Pai wrote:
> I'm fine calling it a 2.4.1. The only reason I mentioned it a
Sounds fine then.
-Jaikiran
On Monday, December 12, 2016, Matt Sicker wrote:
> Issues in the release process? Those would be handled by multiple release
> candidates. People normally only use alphas and betas for new projects or
> new major versions of projects at Apache.
>
> On 11 December 2016
