Thanks, I will keep an eye out for John's build plan work (I assume it won't
be available until some major release).
If we were working under Linux I could probably tee the output then gawk it
to find what project and phase it was working on and then used that to
generate what I need.
For now I h
On 30 Jul 07, at 2:59 PM 30 Jul 07, John Petritis wrote:
Here is why:
Sure, I'm just saying that to do any of this the plugin doesn't need
to know anything about the phase it's running in. This is definitely
something you would want to do from a lifecycle perspective. If you
want the
Here is why:
It (my plugin) will be be run in multiple phases, and needs to log:
- what pom is being made
- what phase it is in
- the time my plugin is run
There are parts of our build that can take a very long time to run if
certain problems occur.
By monitoring a log of when some various poin
On 30 Jul 07, at 1:18 PM 30 Jul 07, John Petritis wrote:
I need to be able to get the phase my plugin is run in.
Why?
There is no way to get the phase a plugin is running in as you
generally declare that from the outside i.e. a workflow that the mojo
takes part in.
I will probably ma
I need to be able to get the phase my plugin is run in.
I will probably make it run in multiple phases.
I would prefer to get the phase from an @parameter expression="${???}"
But I cannot figure out what variable name to use in it.
(I am basically trying to make a logger that tracks when maven g
