It's a set of plexus components that is designed to be embedded. One
form is embedding in Maven in the form of a plugin. So it's not a
plugin, but can be accessed through a Maven plugin. Many plugins use
this strategy where they make a set of reusable plexus components and
then provide a mojo wrapper from which maven can access the
functionality.
On 21-Mar-08, at 6:24 AM, Dennis Lundberg wrote:
Disclaimer: I've never used archetypes before.
I've had a look at http://jira.codehaus.org/browse/MPLUGIN-102
I found the attached example project strange, because the pom
specified
<packaging>maven-plugin</packaging>
The poster references the example pom on this page:
http://maven.apache.org/guides/mini/guide-creating-archetypes.html
The page also states that:
"An archetype is a very simple plugin"
Is that really true? Isn't it just a jar file used by the archetype
plugin?
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
You are never dedicated to something you have complete confidence in.
No one is fanatically shouting that the sun is going to rise tomorrow.
They know it is going to rise tomorrow. When people are fanatically
dedicated to political or religious faiths or any other kind of
dogmas or goals, it's always because these dogmas or
goals are in doubt.
-- Robert Pirzig, Zen and the Art of Motorcycle Maintenance
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
