Jason, 2009/3/19 Jason van Zyl <[email protected]>: > One annotation is for Plexus components specifically and that is > @plexus.requirement or @Requirement if you're doing annotations. > > The other is specifically for Maven plugins. The component metadata for your > own types, like our Maven plugins, have their own component descriptors > which are mutated on the fly inside Plexus.
OK, got it now! :-) > But for a Maven plugin that also contains other Plexus components you need > to use @plexus.requirement/@Requirement with your Plexus components and > @component in your Mojo-based classes. Maven plugins may often not contain > any Plexus components so the use of the type of annotations is completely > partitioned. Take a look at Maven trunk if you want to see examples of the > annotations used for Plexus components. Does it depend what I'm trying to resolve? I have a utility class that I wanted to give a Log object and used the @component Javadoc tag. This worked, but Log belongs to Maven. Core question is: does @component resolve *any* Plexus component when run within the Maven context, or only Maven specific components? Concerning real Java5+ annotations: I can't use them for the moment since our build system has to remain Java 1.4 compliant. Thanks for the answer! Ringo --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
