Hi Karl,
Thanks again for the argument. For me it's still a valid question of how
for example the license plugin
would apply itself on its source structure to fix/update Java header before
a release? (Of course, I
understand the principle of linearizability to fix the circular issue).
Just in cas
Hi,
On 7/18/16 9:31 PM, Behrooz Nobakht wrote:
Hi,
Thanks for the reply and I agree with the logical circular dependency
argument.
But I still believe that this is valid test/use case for a Maven plugin
being developed.
I don't agree with that...cause for those things it is best having IT's
Hi,
Thanks for the reply and I agree with the logical circular dependency
argument.
But I still believe that this is valid test/use case for a Maven plugin
being
developed.
The profile idea 'self-test/run' works in this case for what I'm working on;
but I think main reason is that logic here only
Hi,
trying to run your own plugin which you are developing within the same
project will not work cause that already sounds like a circle ..
That's the reason to use invoker-plugin to have full fledged project
running as tests...
A profile will not really help, cause you need to do a `mvn i
Hi,
I am developing a Maven Plugin and trying to follow documentation[1] to use
maven-invoker-plugin
from the auto-generated profile 'run-its' to run an execution of the plugin
under dev on itself.
As an example, let's consider mojouas/license-maven-plugin. One of it's
goals is 'update-file-heade
