On 19/02/18 9:23 AM, Jaikiran Pai wrote:
On 19/02/18 1:37 AM, Stefan Bodewig wrote:
On 2018-02-15, Jaikiran Pai wrote:
We have 3 pre-defined formatters all of which are capable of receiving
this streamed sysout/syserr data. Each of these do _not_ hold on to
this sysout/syserr data in-memory
On 19/02/18 1:37 AM, Stefan Bodewig wrote:
On 2018-02-15, Jaikiran Pai wrote:
I'm now done with the initial goals that I had in mind for this
task. I've opened a PR[1] for review. I've included a manual for this
task and it can be currently found here[2]. I would suggest reading
the manual
On 2018-02-15, Jaikiran Pai wrote:
> I'm now done with the initial goals that I had in mind for this
> task. I've opened a PR[1] for review. I've included a manual for this
> task and it can be currently found here[2]. I would suggest reading
> the manual first, before reviewing the PR, since the
On 17/02/18 12:51 AM, Stefan Bodewig wrote:
On 2018-02-15, Jaikiran Pai wrote:
I'm now done with the initial goals that I had in mind for this
task. I've opened a PR[1] for review. I've included a manual for this
task and it can be currently found here[2]. I would suggest reading
the manual
On 2018-02-15, Jaikiran Pai wrote:
> I'm now done with the initial goals that I had in mind for this
> task. I've opened a PR[1] for review. I've included a manual for this
> task and it can be currently found here[2]. I would suggest reading
> the manual first, before reviewing the PR, since the
I just realized that the manual that I linked in my mail isn't
accessible to everyone. So here's an alternative link to the same
https://home.apache.org/~jaikiran/temp_workspace/manual/Tasks/junitlauncher.html
-Jaikiran
On 15/02/18 7:21 PM, Jaikiran Pai wrote:
I'm now done with the initial
From a release point of view - I know we are currently sorting out some
regressions and issues that have been uncovered by the latest release.
So if it makes things easier from a stability point of view, we can wait
to merge this only after we have done another release which addresses
only the
I'm now done with the initial goals that I had in mind for this task.
I've opened a PR[1] for review. I've included a manual for this task and
it can be currently found here[2]. I would suggest reading the manual
first, before reviewing the PR, since the manual will give an overall
idea of
On 2018-01-27, Jaikiran Pai wrote:
> Here's an update on where this effort now stands. As of yesterday, I
> have the basic minimal functionality that I had planned for this (new)
> task ready. There are other enhancements that this task will need as
> we go along but at this point, this should be
One minor but important detail - this feature/task will only be
available in the 1.10.x releases (whichever release we decide to include
this in) and won't be available in 1.9.x releases of Ant.
-Jaikiran
On 27/01/18 8:40 AM, Jaikiran Pai wrote:
Here's an update on where this effort now
Here's an update on where this effort now stands. As of yesterday, I
have the basic minimal functionality that I had planned for this (new)
task ready. There are other enhancements that this task will need as we
go along but at this point, this should be usable.
While working on this new
Thank you. I'm moving ahead with the new proposed task. Hopefully I
should be able to have something functional in a few days.
-Jaikiran
On 14/12/17 5:14 PM, Stefan Bodewig wrote:
On 2017-12-14, Jaikiran Pai wrote:
With that context, I would like to explain what I have attempted so
far and
FWIW, I'm for a separate task. It may simplify dropping tasks that become
mired in legacy (who needs Jasper from Tomcat 4 nowadays?)
Or maybe we should start an ant-legacy antlib? :-)
Gintas
2017-12-14 12:44 GMT+01:00 Stefan Bodewig :
> On 2017-12-14, Jaikiran Pai wrote:
>
>
On 2017-12-14, Jaikiran Pai wrote:
> With that context, I would like to explain what I have attempted so
> far and I would like inputs on whether I should follow this path
> and/or if there are other suggestions on how we should go ahead. As
> you are probably aware, the JUnitTask (the Ant task
After sending this mail, the more I think of it, I am not too sure
introducing a new task (junitlauncher) is serving any useful purpose. Of
course it does allow me to keep the task implementation simpler without
using the existing JUnitTask as an entry point of the call. But that is
an
15 matches
Mail list logo