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 install`
first and than run your project with something like `mvn -Pself-testing
verify` ? Not a good idea?
And finally this is not best practice...
What you can do is to define a previous released version of your plugin
in your pom ...That's what for example maven-invoker-plugin itself is
doing.. ;-)
Kind regards
Karl Heinz Marbaise
On 7/18/16 9:43 AM, Behrooz Nobakht wrote:
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-header'.
And, it actually has an integration-test executed by maven-invoker-plugin
but it's on a sample project.
What if I wanted to run the update-file-header on the license-maven-plugin
itself? How?
One straight way would be introduce another profile to configure the plugin
to run on itself, but is this a
good practice on Maven plugin development?
Thanks,
Behrooz
[1]: http://maven.apache.org/plugins/maven-invoker-plugin/
[2]:
https://github.com/mojohaus/license-maven-plugin/tree/master/src/it/update-file-header-test-mojo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
