@Component works for sure. We're still within the Maven Plugin Context, so
better use the Plugin Annotations.
And yes, you can refer to both Plexus @Component instances and JSR330
@Named instance.
Robert
On Wed, 01 Feb 2017 21:01:10 +0100, Laird Nelson <[email protected]>
wrote:
Thanks; yeah, I understand--maybe I don't actually--that there are
certain
Maven plugin annotations that get converted into the XML descriptor. But
what about line 52 and following in the link you sent:
1. @Component( role = MyComponentExtension.class,
2. hint = "..." )
3. private MyComponent component;
Shouldn't that be replaced with JSR-330? Very confused; sorry!
Best,
Laird
On Wed, Feb 1, 2017 at 11:59 AM Robert Scholte <[email protected]>
wrote:
No, plugin annotation are used to generate a plugin descriptor, i.e.
META-INF/maven/plugin.xml
At runtime this file is used to initialize the plugin, whereas the
specified components are injected with sisu/guice
Robert
On Wed, 01 Feb 2017 20:52:19 +0100, Laird Nelson <[email protected]>
wrote:
> Thanks. But isn't _that_, in turn, replaced by JSR-330? This is what
> I'm
> confused about.
>
> On Wed, Feb 1, 2017 at 11:26 AM Robert Scholte <[email protected]>
> wrote:
>
>> This is what is used nowadays:
>>
>>
https://maven.apache.org/components/plugin-tools/maven-plugin-tools-annotations/index.html
>>
>> Robert
>>
>> On Wed, 01 Feb 2017 19:21:09 +0100, Laird Nelson <[email protected]>
>> wrote:
>>
>> > I apologize in advance for the inarticulate nature of this
question.
>> >
>> > I have this faint sense that Sisu and Guice are at the core of
Maven
>> > these
>> > days, with a Plexus layer on top.
>> >
>> > This makes me think that perhaps I should be using different
>> annotations
>> > in
>> > my maven plugins than @Component etc.
>> >
>> > Is this (
>> >
>>
https://maven.apache.org/guides/plugin/guide-java-plugin-development.html)
>> > still the official guide for writing Maven plugins? If I wanted to
>> > inject
>> > some named Plexus component, is there some guide showing how to do
>> that?
>> >
>> > Thanks,
>> > Best,
>> > Laird
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
