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
That's consistent with GitHub repo clones being available, but without
"clone me at GitHub" ribbons.
On the other hand, I rewrote the manual
Thanks for correcting the omission.
But, the task manual page states that junit.jar of JUnit 4 might still be
For junit-vintage engine:
- junit.jar (JUnit 4.x version)
so perhaps it's worth a note anyway.
I was wondering why junitlauncher
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
Github user twogee commented on the pull request:
@jaikiran would it be possible to add a `classpath` attribute?
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 which states regular users
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
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.
On 12/03/18 4:53 PM, Stefan Bodewig wrote:
Github user jaikiran closed the pull request at:
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
Github user jaikiran commented on the issue:
This is now merged upstream. Closing this PR. Thanks Stefan for the
To unsubscribe, e-mail:
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
Github user twogee commented on the issue:
@AurelienLourot we moved the discussion to
To unsubscribe, e-mail:
Mail list logo