Hi Stefan,
**JDK 11 EA build 8, *under both the GPL and Oracle EA licenses, is
now available at **http://jdk.java.net/11**. **
*
* Newly approved Schedule, status & features
o http://openjdk.java.net/projects/jdk/11/
* Release Notes:
o http://jdk.java.net/11/release-notes
*
Github user twogee commented on the issue:
https://github.com/apache/ant-ivy/pull/69
@supertick FYI, Ivy 2.5.0 RC is on the way, @nlalevee has kindly taken the
role of release manager. Your latest commits are not merged to master, though.
If you are interested in using 2.5.0, please
Github user sutchark commented on the issue:
https://github.com/apache/ant-ivy/pull/69
How should we let you know? Here?
I am interested in using 2.5.0.
---
-
To unsubscribe, e-mail:
Hi Martin,
the issue is somewhat misleading. JUnit tests must be runner-agnostic, it
should make no difference whether it's Ant-JUnit* or Surefire.
However, it is my experience that Surefire needs basedir property to find
things where Ant-JUnit* finds them.
Once upon a time, Surefire lacked the
On 2018-04-11, Gintautas Grigelionis wrote:
> 2018-04-11 6:25 GMT+00:00 Jaikiran Pai :´
>> On 10/04/18 12:27 AM, Gintautas Grigelionis wrote:
>>> I wrote earlier that I was about to review the unit tests.
>>> I was particularly unhappy about the root-property hack for
On 2018-04-12, Nicolas Lalevée wrote:
> The Junit task is printing a warning if it finds multiple versions of
> Ant in the classpath of the unit tests. It seems it doesn’t do
> correctly the job if the ant runtime is explicitly removed from the
> classpath.
Quite possible.
> Here the function
> Le 12 avr. 2018 à 18:29, Nicolas Lalevée a écrit
> :
>
> I have built a release candidate for Ivy 2.5.0-rc1.
>
> The git tag of this release is:
> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tag;h=refs/tags/2.5.0-rc1
>
>
2018-04-12 15:18 GMT+00:00 Stefan Bodewig :
> On 2018-04-12, Gintautas Grigelionis wrote:
>
> > 2018-04-12 14:39 GMT+00:00 Stefan Bodewig :
>
> >> On 2018-04-11, Gintautas Grigelionis wrote:
>
> >>> XMLCatalogTest is an example of unit tests complicated by
> Le 12 avr. 2018 à 16:57, Stefan Bodewig a écrit :
>
> On 2018-04-12, Nicolas Lalevée wrote:
>
>> The Junit task is printing a warning if it finds multiple versions of
>> Ant in the classpath of the unit tests. It seems it doesn’t do
>> correctly the job if the ant
On 2018-04-12, Gintautas Grigelionis wrote:
> 2018-04-12 15:18 GMT+00:00 Stefan Bodewig :
>> On 2018-04-12, Gintautas Grigelionis wrote:
>>> 2018-04-12 14:39 GMT+00:00 Stefan Bodewig :
On 2018-04-11, Gintautas Grigelionis wrote:
>
On 2018-04-12, Nicolas Lalevée wrote:
> As far as I can see, the classpath used by checkForkedPath is the
> proper one. The function which manipulates the classpath to add the
> Ant runtime [1] is called before. So I should start looking into the
> AntClassLoader which is improperly finding the
+1.
Thank you Nicolas for running this release.
Tested the following:
- Downloaded the .tar.gz binary
- Checked some random docs, that are part of the download. Looks fine.
- Built some random internal projects using this downloaded version of
Ivy, using Java 8. All went well.
- Verified
2018-04-12 14:39 GMT+00:00 Stefan Bodewig :
> On 2018-04-11, Gintautas Grigelionis wrote:
>
> > XMLCatalogTest is an example of unit tests complicated by root property.
>
> Actually, the test even passes if you remove the line using the property
> as long as your current
On 2018-04-12, Gintautas Grigelionis wrote:
> 2018-04-12 14:39 GMT+00:00 Stefan Bodewig :
>> On 2018-04-11, Gintautas Grigelionis wrote:
>>> XMLCatalogTest is an example of unit tests complicated by root property.
>> Actually, the test even passes if you remove the line
14 matches
Mail list logo