On Fri, Feb 3, 2017 at 10:22 AM Stuart McCulloch wrote:
> Circling back to the original question: yes you can override components in
> recent versions of Maven but there are some caveats. First your component
> must be visible to the plugin (ie be in the same realm or a
Here's a brief overview of the different layers...
Maven plugin annotations are only used at plugin build time to generate
Maven's plugin.xml - they are not used at runtime (at least the container
doesn't use them)
Maven uses this plugin.xml descriptor to setup the plugin in Plexus
(creating the
On 3 Feb 2017 16:44, "Laird Nelson" wrote:
On Fri, Feb 3, 2017 at 1:15 AM Hervé BOUTEMY wrote:
> notice:@Component we're using in a Mojo is from Maven Plugin Tools
> org.apache.maven.plugins.annotations.Component [1]
>
Right; I (now :-)) understand
notice:@Component we're using in a Mojo is from Maven Plugin Tools
org.apache.maven.plugins.annotations.Component [1]
it's different from @Component from Plexus, which is
org.codehaus.plexus.component.annotations.Component [2]
Using the same class name in a different package is probably a bad
you're the first one I see who does that: I never imagined to support this
scenario
Then I'd say: it's by design :)
I don't know if adding this feature would be hard or not
Regards,
Hervé
Le jeudi 2 février 2017, 01:02:33 CET Maxim Solodovnik a écrit :
> One additional question,
>
> I'm
Le vendredi 3 février 2017, 10:43:42 CET Robert Scholte a écrit :
> What I expect to happen is that Plexus Component Annotations will be fully
> replaced with JSR330 annotations.
> In that case there will be only 1 @Component annotation, i.e.
> org.apache.maven.plugins.annotations.Component, which
in all the cases I know of , since there is site.xml inheritance for shared
parts, site.xml for modules are not necessary.
Can you share the "standard" site.xml?
Regards,
Hervé
Le vendredi 3 février 2017, 16:31:14 CET Maxim Solodovnik a écrit :
> Actually I have multi-module project
> I have
On Fri, 03 Feb 2017 12:39:56 +0100, Hervé BOUTEMY
wrote:
Le vendredi 3 février 2017, 10:43:42 CET Robert Scholte a écrit :
What I expect to happen is that Plexus Component Annotations will be
fully
replaced with JSR330 annotations.
In that case there will be only 1
Actually I have multi-module project
I have "main site" with some how-tos, announces etc.
and "standard" sites for all sub-modules: info, rat-report, javadocs,
dependencies etc.
Currently I have exactly the same site.xml for all these "standard" sites,
and I don't really like to have 7 copies of
b) is probably possible, but not recommended
When we want to share some configuration between plugins, the usual solution is
to define a convention on a property name: see for example maven.test.skip that
is supported both by maven-compiler-plugin [1], Surefire [2], nar-maven-plugin
in
What I expect to happen is that Plexus Component Annotations will be fully
replaced with JSR330 annotations.
In that case there will be only 1 @Component annotation, i.e.
org.apache.maven.plugins.annotations.Component, which is fine by me.
Also, I expect the community to be more familiar with
On Fri, Feb 3, 2017 at 10:27 AM, Hervé BOUTEMY wrote:
> b) is probably possible, but not recommended
A few words on how this would work, and *why* it is not recommended? I
am not interested in finding a solution for all Maven users, Just
something that works for me and my
On Fri, Feb 3, 2017 at 1:15 AM Hervé BOUTEMY wrote:
> notice:@Component we're using in a Mojo is from Maven Plugin Tools
> org.apache.maven.plugins.annotations.Component [1]
>
Right; I (now :-)) understand this part and all of the things related to it.
The part I didn't
13 matches
Mail list logo