On Apr 27, 2012, at 9:55 PM, Hervé BOUTEMY wrote:
> yes, +1 for the first step - ie annotations for plugin.xml generation
Yes, this is the wisest, most compatible way to go. It can easily be done using
ASM to process the annotations and produce the plugin.xml. Works fine. This
also allows peopl
yes, +1 for the first step - ie annotations for plugin.xml generation
but -0 for discovery with runtime annotation instead of plugin.xml
and yes, I took time to document (end reference JFrog's implementation) but
don't have really time to code it even if the feature would be a great benefit
IMHO
Some of us are still on 2.0.x.
I for one, don't see the need to introduce (the possibility of) annotation
hell into what is an already well understood mechanism.
-Chris
On Sat, Apr 28, 2012 at 4:01 AM, Olivier Lamy wrote:
> I would prefer not be core change dependent. Some folks are still usin
On 04/27/2012 01:34 PM, Ansgar Konermann wrote:
JFrog (the Artifactory guys) has already published a set of Java
1.5 annotations for mojo development, including a m-plugin-p extension to
use them.
Beware that (acc. to their documentation) the tool relies on APT, which is
deprecated in JDK 6
I would prefer not be core change dependent. Some folks are still using 2.x
.
And 'classloader scanning' at runtime level will have IHMO a performance
cost !
So I would prefer plugin metadata generation (the trick will be having the
mix of doclet and annotations : perso I'm not sure it's a good ide
pr 27, 2012 at 2:34 PM, Ansgar Konermann <
ansgar.konerm...@googlemail.com> wrote:
> Hi there,
>
> I think JFrog (the Artifactory guys) has already published a set of Java
> 1.5 annotations for mojo development, including a m-plugin-p extension to
> use them. The source code is av
Hi there,
I think JFrog (the Artifactory guys) has already published a set of Java
1.5 annotations for mojo development, including a m-plugin-p extension to
use them. The source code is available on github [1], but unfortunately the
artifacts are not available in Central (there is a ticket in
We have implemented a Java 5 annotation for configuration parameters
(PullParameter) in the Android Maven Plugin that might be worth looking
at. We are still phasing them out across the system but a good place to
look at the usage is the ProguardMojo
https://github.com/jayway/maven-android-plugin/
+100
I've had a talk about this with Simone this month.
He'd done some investigation already.
I think there are two separate steps to be taken.
1. Generate the plugin.xml based on both annotations and doclets
2. Extend Maven Core to understand Mojo Annotations as well
The first one would already
Hi,
I'd like to work on 1.5 Annotations for Mojos.
Hervé started documentation here:
https://cwiki.apache.org/confluence/display/MAVEN/Java+5+Annotations+for+Plugins
The Stephen's idea for named without Mojo prefix looks fine (at least
for me). But I would prefer to not implement (yet) the other i
10 matches
Mail list logo
