Github user twogee commented on the issue:
https://github.com/apache/ant-ivy/pull/64
@AurelienLourot we moved the discussion to
[JIRA](https://issues.apache.org/jira/browse/IVY-1280)
---
-
To unsubscribe, e-mail: de
Thanks for the input, Stefan. I took your suggestion and exposed a API
to get the Project on that custom interface. It doesn't/can't directly
use the IntrospectionHelper support available to project components,
since unlike nested elements of a task, this custom class can be plugged
in somethin
Github user jaikiran commented on the issue:
https://github.com/apache/ant/pull/60
This is now merged upstream. Closing this PR. Thanks Stefan for the
extensive review.
---
-
To unsubscribe, e-mail: dev-unsubscr...
Github user jaikiran closed the pull request at:
https://github.com/apache/ant/pull/60
---
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
I (finally) merged the JUnit 5 work to master. Rest of the fork related
work for this task is something that I don't plan to make available in
this release (the work is going to take some time). So I guess, we can
make a new release.
-Jaikiran
On 12/03/18 4:53 PM, Stefan Bodewig wrote:
On 2
This is now done. The Ant_Nightly job now generates the Ant distribution
which can be used for testing the bug fixes/features that go into the
"master" branch. The distribution is available at
https://builds.apache.org/job/Ant_Nightly/lastSuccessfulBuild/artifact/distribution/
-Jaikiran
On 0
I was about to send a mail to the user mailing list about the Ant
nightly job which publishes the daily snapshots, so that they can test
some bug fixes and new features (JUnit 5 in particular). However, I
happened to read the Apache release policy[1] which states regular users
aren't even meant
Github user twogee commented on the pull request:
https://github.com/apache/ant/commit/a312b6728acb7a8d1f8765899615205b3042cb7e#commitcomment-28138020
@jaikiran would it be possible to add a `classpath` attribute?
---
-
The change noted in this commit isn't actually needed i.e. the
junitlauncher task doesn't require the junit.jar to be available as
noted in the junitlauncher task's manual.
I however forgot to include the JUnit 5 platform API dependencies in
this Library Dependencies table, which I'll add now.
Thanks for correcting the omission.
But, the task manual page states that junit.jar of JUnit 4 might still be
necessary
...
For junit-vintage engine:
- junit-vintage-engine.jar
- junit.jar (JUnit 4.x version)
...
so perhaps it's worth a note anyway.
I was wondering why junitlauncher tas
Thanks for pointing this out. To me, it means one thing: release more often.
The way I read it, publishing is not forbidden per se, but rather
advertising.
That's consistent with GitHub repo clones being available, but without
"clone me at GitHub" ribbons.
On the other hand, I rewrote the manual (
11 matches
Mail list logo
