On Sat, Aug 06, 2011 at 03:11:05PM +0200, Baptiste MATHUS wrote:
> And by the way, documentation is cool.
> But even better is look for real-life example. And what's cool with
> opensource is that it's easy to find a bunch of examples from simple to very
> complex.
Just because X worked for someon
On Sat, Aug 06, 2011 at 03:08:34PM +0200, Baptiste MATHUS wrote:
> Well, you were in the right place.
> http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
> What are you missing?
Any indication of what one should put into the default-value to get a
handle on the mojo's entire
And by the way, documentation is cool.
But even better is look for real-life example. And what's cool with
opensource is that it's easy to find a bunch of examples from simple to very
complex.
Cheers
2011/8/6 Baptiste MATHUS
> Well, you were in the right place.
> http://maven.apache.org/guides/
Well, you were in the right place.
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
What are you missing?
As often today in programming, Maven mojo gets "external" property via
dependency injection.
That is, just declare your attribute with the right @parameter expression
On Thu, Aug 04, 2011 at 04:05:10PM -0400, Mark H. Wood wrote:
> Back to topic: I'm writing a plugin that needs access to the
> project's properties. Nothing environmental is passed to a mojo, and
> fishing through the Javadocs for static methods that look promising
> has turned up nothing so far.
First: if I'm writing a plugin for my own use, am I a user or a
developer? I'm not developing Maven itself and the Developer Centre
page admits of nothing in between.
Back to topic: I'm writing a plugin that needs access to the
project's properties. Nothing environmental is passed to a mojo, an
