Thank you, Vincent for the link. It completely describes the way to
create default execution without the need to configure it when using the
plugin.
I learnt a lot!
On Mon, Jun 8, 2015 at 7:53 PM, Vincent Latombe
wrote:
> This annotation just allows you to skip the declaration when you
> add t
This annotation just allows you to skip the declaration when you
add the execution to your pom.
If you want to skip the block, you'll need to create a custom
packaging [1]. Then you'd specify my-packaging in
your pom, instead of jar (or any other value you
currently use)
Cheers,
Vincent
[1]
h
Let me continue with another question. Currently, my Mojo implementation has
@Mojo(name = "my-goal-name", defaultPhase = LifecyclePhase.GENERATE_SOURCES)
However, I still need to add `` when I'm using the plugin;
otherwise it's just ignored.
I was expecting that the Mojo annotation would remove t
Hi Andreas,
Thank you for the pointer. It helped and it worked.
I was using an improper life cycle phase as the default.
Cheers,
Behrooz
On Mon, Jun 8, 2015 at 6:13 PM, Andreas Gudian
wrote:
> Hi,
>
> You can check the build-helper-maven-plugin, which has a tiny goal to add a
> source direct
Hi,
You can check the build-helper-maven-plugin, which has a tiny goal to add a
source directory to the project:
https://github.com/mojohaus/build-helper-maven-plugin/blob/master/src/main/java/org/codehaus/mojo/buildhelper/AddSourceMojo.java
The maven-eclipse-plugin picks up all source directorie
Hi,
I am trying to follow what `maven-plugin-plugin` Mojo does when generating
HelpMojo.java.
It also updates eclipse's .classpath some way (?) that I can see the
`target/generated-sources/plugin`
as a source folder in my IDE.
Similarly, this is also what maven-jaxb2-plugin does when generating
s
