Vincent Massol wrote:
>Yes, Jason explained to me what Mojos are. So ideally we would have:
>
>mojos/ (java beans equivalent to Ant tasks and not tied to plexus nor maven)
>
>
right - but implement the Plugin interface and contribute to a
descriptor through some metadata
>plexus/ (focus only on
Maczka Michal wrote:
>With exception for versioning it is all already implemented in plexus and
>just needs to be exposed.
>
>
If you look at the code before emailing, you'll save yourself a lot of
time. The plugin manager already uses plexus configuration to some
extent and has comments to move
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 13, 2005 12:30 AM
> To: Maven Developers List
> Subject: Re: [M2] Plugins vs Mojo vs Plexus components?
>
>
> This is really a name confusion. The plexus things being u
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mercredi 13 avril 2005 00:30
> To: Maven Developers List
> Subject: Re: [M2] Plugins vs Mojo vs Plexus components?
>
> This is really a name confusion. The plexus things being used, for
This is really a name confusion. The plexus things being used, for the
most part, just being used as additional libraries, as is
maven-archiver. eg plexus-compiler, plexus-archiver. Mojos are goals or
tasks within a plugin.
The only time plexus the container comes into it is when you see an
expres
Hi,
I see that several m2 plugins in maven-components/maven-*-plugin/** are
using other java components located directly in maven-components/ such as
maven-archiver, maven-archetype, etc. What are those projects? Are they
Mojos? Of not, are they meant to become mojos in the future?
Also some of t
