But you can inject singleton components (default in Plexus) which contain
state. I believe Dan Tran had written up a fully working example.
On Feb 17, 2015, at 6:03 AM, Kristian Rosenvold kristian.rosenv...@gmail.com
wrote:
Each execution has a new instance
17. feb. 2015 11:27 skrev Tibor
Hi Tibor,
the plugin is just a thin wrapper around the jdeps executable to make it
easier to integrate it with your Maven project. So for the Apache Maven
JDeps plugin it is out of scope. However, you could share your idea with
the jigsaw project[1]
thanks,
Robert
[1]
Each execution has a new instance
17. feb. 2015 11:27 skrev Tibor Digana tibordig...@apache.org:
Is the MOJO object reused in plugin executions?
I want to make sure that if I store some data in the instance fields in my
MOJO object, next execution in a new MOJO object is created and properly
Hi Robert,
It would be great to launch the JDeps within Javac compiler. Do you think it
would be possible for JDeps?
I like the way how my annotation processor (AP) is wired with the compiler.
I don't think that JDeps use annotations. I am not sure if compiler has
other kinds of processor
GitHub user paranoiabla opened a pull request:
https://github.com/apache/maven-doxia/pull/1
Adding support for multiple file extensions
Following this thread asciidoctor/asciidoctor-maven-plugin#125 Here's a
pull request that will allow parsers to specify more than one file
GitHub user paranoiabla opened a pull request:
https://github.com/apache/maven-doxia-sitetools/pull/1
Adding support for multiple file extensions
Following this thread asciidoctor/asciidoctor-maven-plugin#125 and also
https://github.com/apache/maven-doxia/pull/1 here's a pull
Is the MOJO object reused in plugin executions?
I want to make sure that if I store some data in the instance fields in my
MOJO object, next execution in a new MOJO object is created and properly
isolated from the context of previous execution.
Is it working like this in mvn core, or do we plan
