GitHub user jaikiran opened a pull request:
https://github.com/apache/ant-ivy/pull/18
Fix IVY-1448
The commit here fixes the issue reported in
https://issues.apache.org/jira/browse/IVY-1448 and also includes a test case to
verify the fix.
**Note that this issue isn't repro
Now that the plan seems to be to release 2.5.x of Ivy, would it be fine if we
mandate the _minimum_ Java runtime version to be something higher than Java 5
that’s currently supported for 2.4.x
http://ant.apache.org/ivy/history/latest-milestone/compatibility.html.
Given that Java 6 itself has lo
I think that upgrading the requirement on the JDK is a good idea, because at
least us, the maintainers, need at some point to be able to test it if there is
an issue with that minimum JDK.
One thing to consider is which JDK is being required in the environment Ivy is
being used: Ant, Gradle, SB
The current version of Groovy has 1.6 as the minimum but is our maintenance
stream.
The upcoming next version will require 1.7 and versions with 1.8 as the
minimum are not too far away.
Ant 1.9.x is still on Java5 but Ant 1.10.x requires Java 8.
I don't think Gradle uses any Ivy classes any more.
I have changed the config of the build so it does a build, then checkstyle,
then findbugs, and then the unit tests.
Nicolas
> Le 18 mai 2017 à 08:21, J Pai a écrit :
>
> Now that the findbugs URL issue has been resolved with this PR[1] being
> merged, maybe we should change the targets that g
GitHub user jaikiran opened a pull request:
https://github.com/apache/ant-ivy/pull/19
IVY-1554 - Add (conditional) support for SHA-256 SHA-512 and SHA-384
checksum algorithms
The commit here adds support for SHA-256, SHA-512 and SHA-384 algorithms as
requested in https://issues.apa
I would favour 1.7 as it's the newest before the major update to Java8.
Having a 1.7 in the target environment should not been so restrictive ...
Jan
> -Ursprüngliche Nachricht-
> Von: Paul King [mailto:pa...@asert.com.au]
> Gesendet: Donnerstag, 18. Mai 2017 11:27
> An: Ant Developers Li
+1
-Jaikiran
On 18-May-2017, at 4:26 PM, Jan Matèrne (jhm) wrote:
I would favour 1.7 as it's the newest before the major update to Java8.
Having a 1.7 in the target environment should not been so restrictive ...
Jan
> -Ursprüngliche Nachricht-
> Von: Paul King [mailto:pa...@asert.com.a
Using 1.7 for the next release and then 1.8 for the following release makes
sense to me.
On 18 May 2017 at 05:58, J Pai wrote:
> +1
>
> -Jaikiran
> On 18-May-2017, at 4:26 PM, Jan Matèrne (jhm) wrote:
>
> I would favour 1.7 as it's the newest before the major update to Java8.
> Having a 1.7 in
Github user asfgit closed the pull request at:
https://github.com/apache/ant-ivy/pull/17
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
That's fine, IvyDE is already at Java 7/Eclipse 3.7.1; then IvyDE baseline
should be bumped to Java 8/Eclipse 4.4 with the next Ivy release. Hopefully
updatesite resolver could be used then.
2017-05-18 17:12 GMT+02:00 Matt Sicker :
> Using 1.7 for the next release and then 1.8 for the following r
Github user asfgit closed the pull request at:
https://github.com/apache/ant-ivy/pull/18
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
Gradle does have an Ivy plugin which wraps Ivy 2.2.0
2017-05-18 11:26 GMT+02:00 Paul King :
> The current version of Groovy has 1.6 as the minimum but is our maintenance
> stream.
> The upcoming next version will require 1.7 and versions with 1.8 as the
> minimum are not too far away.
>
> Ant 1.9
GitHub user jaikiran opened a pull request:
https://github.com/apache/ant-ivy/pull/20
Fix IVY-1522
The commit here contains a potential fix for the issue reported in
https://issues.apache.org/jira/browse/IVY-1522. This PR also contains a test
case to verify the fix.
**Not
So far the majority seems to be to require a minimum of Java 7. If there are no
concerns or objections to this by the end of this week, then on Monday, I’ll
raise a PR to mandate Java 7 for Ivy.
-Jaikiran
On 18-May-2017, at 11:48 PM, Gintautas Grigelionis
wrote:
That's fine, IvyDE is alread
As discussed on this mailing list [1] we should increase the minimum Java
version [2] from current (Ivy-2.4.0) Java5 to Java 7 (Ivy-2.5.0).
Decisions whether to increase to Java8 after that release should be make
after that release.
According to the bylaws [3] this vote is open for one week (until
+1
-Jaikiran
On 19-May-2017, at 10:55 AM, Jan Matèrne wrote:
As discussed on this mailing list [1] we should increase the minimum Java
version [2] from current (Ivy-2.4.0) Java5 to Java 7 (Ivy-2.5.0).
Decisions whether to increase to Java8 after that release should be make
after that release.
Ac
17 matches
Mail list logo
