Just an update on this in case there is anyone else who is interested.
I found an answer to this on stackoverflow:
http://stackoverflow.com/questions/8389825/creating-a-maven-mojo-that-automatically-adds-new-source-folders-to-the-build
On Wed, Nov 30, 2011 at 3:07 PM, Stephen Connolly
wrote:
>
That just defined the default phase that the goal will bind to if you don't
specify a phase... but you need to bind a goal to a phase in the consumer's
pom or the packaging lifecycle
On 30 November 2011 23:00, Jeff MAURY wrote:
> This is done through a Javadoc annotation in your Mojo source file
This is done through a Javadoc annotation in your Mojo source file.
Regards
Jeff MAURY
On Wed, Nov 30, 2011 at 11:45 PM, Andrew Eisenberg <
andrew.eisenb...@gmail.com> wrote:
> Sorry for asking so many questions, but I am now confused. When you
> say "You must bind your mojo to a specific phase
On 30 November 2011 22:45, Andrew Eisenberg wrote:
> Sorry for asking so many questions, but I am now confused. When you
> say "You must bind your mojo to a specific phase", where does this
> binding happen? Inside the pom associated with the mojo or inside the
> plugin consumer's pom? Earlier,
Sorry for asking so many questions, but I am now confused. When you
say "You must bind your mojo to a specific phase", where does this
binding happen? Inside the pom associated with the mojo or inside the
plugin consumer's pom? Earlier, I think you implied that this had to
happen in the consumer
No, you can have a mojo automatically invoked as soon as it is declared in
a pom. You must bind your mojo to a specific phase.
Regards
Jeff MAURY
On Wed, Nov 30, 2011 at 10:48 PM, Andrew Eisenberg <
andrew.eisenb...@gmail.com> wrote:
> On Wed, Nov 30, 2011 at 1:31 PM, Jeff MAURY
> wrote:
> > Yo
On Wed, Nov 30, 2011 at 1:31 PM, Jeff MAURY wrote:
> You can develop a Mojo that will do the trick but you will have to
> configure it in you pom (at least define it so that it will be invoked) so
> I don't see the added value compared to the build-helper-plugin
Right. Well, the only benefit is t
You can develop a Mojo that will do the trick but you will have to
configure it in you pom (at least define it so that it will be invoked) so
I don't see the added value compared to the build-helper-plugin
Regards
Jeff MAURY
On Wed, Nov 30, 2011 at 7:53 PM, Andrew Eisenberg <
andrew.eisenb...@gma
Thanks, Jeff and Stephen for your answers. I know about the
build-helper-maven-plugin, but this adds about 20 lines of
configuration to the pom and I was hoping to avoid that. Also,
forcing users to specify a parent pom is not feasible since users will
likely have their own parent poms to use.
M
If you need to add source folders, there is an existing Maven plugin to do
it: the build-helper-maven-plugin. Check the doc at
http://mojo.codehaus.org/build-helper-maven-plugin
Regards
Jeff MAURY
On Sat, Nov 26, 2011 at 1:58 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> eithe
either mandate a parent pom... they will have to reference your plugin in
their pom and the execution from the pluginmgmt will be pulled in, or
custom lifecycle (they will need to ref the plugin and set extensions to
true...
themselves the only two ways to skin the cat
- Stephen
---
Sent from my
Hi all,
I am trying to create a maven plugin that transparently adds a new
source folder to the project. It is always the same folder and so
there should be no configuration required from the user. I've been
going through
http://www.sonatype.com/books/mvnref-book/reference/writing-plugins.html
12 matches
Mail list logo
