You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Binil Thomas (JIRA)" <ji...@codehaus.org> on 2005/10/23 14:33:11 UTC

[jira] Created: (MNG-1290) What is a Mojo?

What is a Mojo?
---------------

         Key: MNG-1290
         URL: http://jira.codehaus.org/browse/MNG-1290
     Project: Maven 2
        Type: Bug
  Components: documentation  
    Versions: 2.0    
 Reporter: Binil Thomas


On http://maven.apache.org/developers/mojo-api-specification.html page titled "Mojo API", I see :

<snip>
Starting with Maven 2.0, plugins can be written in Java or any of a number of scripting languages. Additionally, Maven tries to stay out of the way of the programmer with its new Mojo API. This opens up the opportunity for many Mojos to be reused outside of Maven, or bridged into Maven from external systems like Ant.
</snip>

The first line states a fact - that Maven plugins can now be written in plain Java. The second line doesnt suggest anything to me besides the irritating name-dropping "Mojo API". The third line adds further confusion by the usage "many Mojos" planting the supiscion that this things called "Mojo" might be more than an API!

Two paragraph later, I see:
<snip>
As mentioned before, each Plugin - or packaged set of Mojos ..
</snip>

Ah! so thats it - Mojo is what constitues a Maven plugin - and there might be some API to write these. 

It would have been much less intimidating had this fact be stated upfront.

A note here - the term "plugin" was did not need any introduction to me - because it is a widely one used in the software scene. At this point I don't even know what a Maven plugin can do - yet I have a vague notion that a plugin might be something that enhances the out-of-the-box behaviour of Maven.

The same familiarity does not apply to the term "Mojo" - I am guessing here, but I think the Maven team invented the term. If so, kindly desrcibe it fully instead of confusing the reader.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Updated: (MNG-1290) What is a Mojo?

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-1290?page=all ]

John Casey updated MNG-1290:
----------------------------

      Assign To: John Casey
    Description: 
On http://maven.apache.org/developers/mojo-api-specification.html page titled "Mojo API", I see :

<snip>
Starting with Maven 2.0, plugins can be written in Java or any of a number of scripting languages. Additionally, Maven tries to stay out of the way of the programmer with its new Mojo API. This opens up the opportunity for many Mojos to be reused outside of Maven, or bridged into Maven from external systems like Ant.
</snip>

The first line states a fact - that Maven plugins can now be written in plain Java. The second line doesnt suggest anything to me besides the irritating name-dropping "Mojo API". The third line adds further confusion by the usage "many Mojos" planting the supiscion that this things called "Mojo" might be more than an API!

Two paragraph later, I see:
<snip>
As mentioned before, each Plugin - or packaged set of Mojos ..
</snip>

Ah! so thats it - Mojo is what constitues a Maven plugin - and there might be some API to write these. 

It would have been much less intimidating had this fact be stated upfront.

A note here - the term "plugin" was did not need any introduction to me - because it is a widely one used in the software scene. At this point I don't even know what a Maven plugin can do - yet I have a vague notion that a plugin might be something that enhances the out-of-the-box behaviour of Maven.

The same familiarity does not apply to the term "Mojo" - I am guessing here, but I think the Maven team invented the term. If so, kindly desrcibe it fully instead of confusing the reader.

  was:
On http://maven.apache.org/developers/mojo-api-specification.html page titled "Mojo API", I see :

<snip>
Starting with Maven 2.0, plugins can be written in Java or any of a number of scripting languages. Additionally, Maven tries to stay out of the way of the programmer with its new Mojo API. This opens up the opportunity for many Mojos to be reused outside of Maven, or bridged into Maven from external systems like Ant.
</snip>

The first line states a fact - that Maven plugins can now be written in plain Java. The second line doesnt suggest anything to me besides the irritating name-dropping "Mojo API". The third line adds further confusion by the usage "many Mojos" planting the supiscion that this things called "Mojo" might be more than an API!

Two paragraph later, I see:
<snip>
As mentioned before, each Plugin - or packaged set of Mojos ..
</snip>

Ah! so thats it - Mojo is what constitues a Maven plugin - and there might be some API to write these. 

It would have been much less intimidating had this fact be stated upfront.

A note here - the term "plugin" was did not need any introduction to me - because it is a widely one used in the software scene. At this point I don't even know what a Maven plugin can do - yet I have a vague notion that a plugin might be something that enhances the out-of-the-box behaviour of Maven.

The same familiarity does not apply to the term "Mojo" - I am guessing here, but I think the Maven team invented the term. If so, kindly desrcibe it fully instead of confusing the reader.

    Fix Version: 2.0.1
    Environment: 

> What is a Mojo?
> ---------------
>
>          Key: MNG-1290
>          URL: http://jira.codehaus.org/browse/MNG-1290
>      Project: Maven 2
>         Type: Bug
>   Components: documentation - general
>     Versions: 2.0
>     Reporter: Binil Thomas
>     Assignee: John Casey
>      Fix For: 2.0.1

>
>
> On http://maven.apache.org/developers/mojo-api-specification.html page titled "Mojo API", I see :
> <snip>
> Starting with Maven 2.0, plugins can be written in Java or any of a number of scripting languages. Additionally, Maven tries to stay out of the way of the programmer with its new Mojo API. This opens up the opportunity for many Mojos to be reused outside of Maven, or bridged into Maven from external systems like Ant.
> </snip>
> The first line states a fact - that Maven plugins can now be written in plain Java. The second line doesnt suggest anything to me besides the irritating name-dropping "Mojo API". The third line adds further confusion by the usage "many Mojos" planting the supiscion that this things called "Mojo" might be more than an API!
> Two paragraph later, I see:
> <snip>
> As mentioned before, each Plugin - or packaged set of Mojos ..
> </snip>
> Ah! so thats it - Mojo is what constitues a Maven plugin - and there might be some API to write these. 
> It would have been much less intimidating had this fact be stated upfront.
> A note here - the term "plugin" was did not need any introduction to me - because it is a widely one used in the software scene. At this point I don't even know what a Maven plugin can do - yet I have a vague notion that a plugin might be something that enhances the out-of-the-box behaviour of Maven.
> The same familiarity does not apply to the term "Mojo" - I am guessing here, but I think the Maven team invented the term. If so, kindly desrcibe it fully instead of confusing the reader.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Updated: (MNG-1290) What is a Mojo?

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-1290?page=all ]

John Casey updated MNG-1290:
----------------------------

    Fix Version:     (was: 2.0.1)
                 2.0.2

> What is a Mojo?
> ---------------
>
>          Key: MNG-1290
>          URL: http://jira.codehaus.org/browse/MNG-1290
>      Project: Maven 2
>         Type: Bug
>   Components: documentation - general
>     Versions: 2.0
>     Reporter: Binil Thomas
>     Assignee: John Casey
>      Fix For: 2.0.2

>
>
> On http://maven.apache.org/developers/mojo-api-specification.html page titled "Mojo API", I see :
> <snip>
> Starting with Maven 2.0, plugins can be written in Java or any of a number of scripting languages. Additionally, Maven tries to stay out of the way of the programmer with its new Mojo API. This opens up the opportunity for many Mojos to be reused outside of Maven, or bridged into Maven from external systems like Ant.
> </snip>
> The first line states a fact - that Maven plugins can now be written in plain Java. The second line doesnt suggest anything to me besides the irritating name-dropping "Mojo API". The third line adds further confusion by the usage "many Mojos" planting the supiscion that this things called "Mojo" might be more than an API!
> Two paragraph later, I see:
> <snip>
> As mentioned before, each Plugin - or packaged set of Mojos ..
> </snip>
> Ah! so thats it - Mojo is what constitues a Maven plugin - and there might be some API to write these. 
> It would have been much less intimidating had this fact be stated upfront.
> A note here - the term "plugin" was did not need any introduction to me - because it is a widely one used in the software scene. At this point I don't even know what a Maven plugin can do - yet I have a vague notion that a plugin might be something that enhances the out-of-the-box behaviour of Maven.
> The same familiarity does not apply to the term "Mojo" - I am guessing here, but I think the Maven team invented the term. If so, kindly desrcibe it fully instead of confusing the reader.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MNG-1290) What is a Mojo?

Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-1290?page=comments#action_49090 ] 

Vincent Massol commented on MNG-1290:
-------------------------------------

 Hi Thomas,
 
We need to put that up on the site (probably in http://maven.apache.org/glossary.html) but just FYI:
 
 - Mojo = a java class implementing the org.apache.maven.plugin.Mojo interface. This is the base class to implement a goal in Maven2.
- Goal = what you call from the command line to execute a build action. For example: "compiler:compile", "site:site", "clean:clean", etc.
 - Plugin = a set of Mojos packaged in a jar


> What is a Mojo?
> ---------------
>
>          Key: MNG-1290
>          URL: http://jira.codehaus.org/browse/MNG-1290
>      Project: Maven 2
>         Type: Bug
>   Components: documentation
>     Versions: 2.0
>     Reporter: Binil Thomas

>
>
> On http://maven.apache.org/developers/mojo-api-specification.html page titled "Mojo API", I see :
> <snip>
> Starting with Maven 2.0, plugins can be written in Java or any of a number of scripting languages. Additionally, Maven tries to stay out of the way of the programmer with its new Mojo API. This opens up the opportunity for many Mojos to be reused outside of Maven, or bridged into Maven from external systems like Ant.
> </snip>
> The first line states a fact - that Maven plugins can now be written in plain Java. The second line doesnt suggest anything to me besides the irritating name-dropping "Mojo API". The third line adds further confusion by the usage "many Mojos" planting the supiscion that this things called "Mojo" might be more than an API!
> Two paragraph later, I see:
> <snip>
> As mentioned before, each Plugin - or packaged set of Mojos ..
> </snip>
> Ah! so thats it - Mojo is what constitues a Maven plugin - and there might be some API to write these. 
> It would have been much less intimidating had this fact be stated upfront.
> A note here - the term "plugin" was did not need any introduction to me - because it is a widely one used in the software scene. At this point I don't even know what a Maven plugin can do - yet I have a vague notion that a plugin might be something that enhances the out-of-the-box behaviour of Maven.
> The same familiarity does not apply to the term "Mojo" - I am guessing here, but I think the Maven team invented the term. If so, kindly desrcibe it fully instead of confusing the reader.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Updated: (MNG-1290) What is a Mojo?

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-1290?page=all ]

John Casey updated MNG-1290:
----------------------------

    Assign To:     (was: John Casey)

> What is a Mojo?
> ---------------
>
>          Key: MNG-1290
>          URL: http://jira.codehaus.org/browse/MNG-1290
>      Project: Maven 2
>         Type: Bug

>   Components: Documentation:  General
>     Versions: 2.0
>     Reporter: Binil Thomas
>      Fix For: documentation

>
>
> On http://maven.apache.org/developers/mojo-api-specification.html page titled "Mojo API", I see :
> <snip>
> Starting with Maven 2.0, plugins can be written in Java or any of a number of scripting languages. Additionally, Maven tries to stay out of the way of the programmer with its new Mojo API. This opens up the opportunity for many Mojos to be reused outside of Maven, or bridged into Maven from external systems like Ant.
> </snip>
> The first line states a fact - that Maven plugins can now be written in plain Java. The second line doesnt suggest anything to me besides the irritating name-dropping "Mojo API". The third line adds further confusion by the usage "many Mojos" planting the supiscion that this things called "Mojo" might be more than an API!
> Two paragraph later, I see:
> <snip>
> As mentioned before, each Plugin - or packaged set of Mojos ..
> </snip>
> Ah! so thats it - Mojo is what constitues a Maven plugin - and there might be some API to write these. 
> It would have been much less intimidating had this fact be stated upfront.
> A note here - the term "plugin" was did not need any introduction to me - because it is a widely one used in the software scene. At this point I don't even know what a Maven plugin can do - yet I have a vague notion that a plugin might be something that enhances the out-of-the-box behaviour of Maven.
> The same familiarity does not apply to the term "Mojo" - I am guessing here, but I think the Maven team invented the term. If so, kindly desrcibe it fully instead of confusing the reader.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Updated: (MNG-1290) What is a Mojo?

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-1290?page=all ]

John Casey updated MNG-1290:
----------------------------

    Fix Version:     (was: 2.0.3)
                 documentation

> What is a Mojo?
> ---------------
>
>          Key: MNG-1290
>          URL: http://jira.codehaus.org/browse/MNG-1290
>      Project: Maven 2
>         Type: Bug

>   Components: documentation - general
>     Versions: 2.0
>     Reporter: Binil Thomas
>     Assignee: John Casey
>      Fix For: documentation

>
>
> On http://maven.apache.org/developers/mojo-api-specification.html page titled "Mojo API", I see :
> <snip>
> Starting with Maven 2.0, plugins can be written in Java or any of a number of scripting languages. Additionally, Maven tries to stay out of the way of the programmer with its new Mojo API. This opens up the opportunity for many Mojos to be reused outside of Maven, or bridged into Maven from external systems like Ant.
> </snip>
> The first line states a fact - that Maven plugins can now be written in plain Java. The second line doesnt suggest anything to me besides the irritating name-dropping "Mojo API". The third line adds further confusion by the usage "many Mojos" planting the supiscion that this things called "Mojo" might be more than an API!
> Two paragraph later, I see:
> <snip>
> As mentioned before, each Plugin - or packaged set of Mojos ..
> </snip>
> Ah! so thats it - Mojo is what constitues a Maven plugin - and there might be some API to write these. 
> It would have been much less intimidating had this fact be stated upfront.
> A note here - the term "plugin" was did not need any introduction to me - because it is a widely one used in the software scene. At this point I don't even know what a Maven plugin can do - yet I have a vague notion that a plugin might be something that enhances the out-of-the-box behaviour of Maven.
> The same familiarity does not apply to the term "Mojo" - I am guessing here, but I think the Maven team invented the term. If so, kindly desrcibe it fully instead of confusing the reader.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


RE: [jira] Created: (MNG-1290) What is a Mojo?

Posted by Vincent Massol <vm...@pivolis.com>.

> -----Original Message-----
> From: Brett Porter [mailto:brett@apache.org]
> Sent: dimanche 23 octobre 2005 20:11
> To: Maven Developers List
> Subject: Re: [jira] Created: (MNG-1290) What is a Mojo?
> 
> There's every chance he's not subscribed to the dev list.

Thanks. Added to JIRA.

[snip]

-Vincent


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: [jira] Created: (MNG-1290) What is a Mojo?

Posted by Brett Porter <br...@apache.org>.
There's every chance he's not subscribed to the dev list.

Vincent Massol wrote:
> Hi Thomas,
> 
> We need to put that up on the site (probably in
> http://maven.apache.org/glossary.html) but just FYI:
> 
> - Mojo = a java class implementing the org.apache.maven.plugin.Mojo
> interface. This is the base class to implement a goal in Maven2.
> 
> - Goal = what you call from the command line to execute a build action. For
> example: "compiler:compile", "site:site", "clean:clean", etc.
> 
> - Plugin = a set of Mojos packaged in a jar
> 
> Hope it helps,
> -Vincent
> 
> 
>>-----Original Message-----
>>From: Binil Thomas (JIRA) [mailto:jira@codehaus.org]
>>Sent: dimanche 23 octobre 2005 14:33
>>To: dev@maven.apache.org
>>Subject: [jira] Created: (MNG-1290) What is a Mojo?
>>
>>What is a Mojo?
>>---------------
>>
>>         Key: MNG-1290
>>         URL: http://jira.codehaus.org/browse/MNG-1290
>>     Project: Maven 2
>>        Type: Bug
>>  Components: documentation
>>    Versions: 2.0
>> Reporter: Binil Thomas
>>
>>
>>On http://maven.apache.org/developers/mojo-api-specification.html page
>>titled "Mojo API", I see :
>>
>><snip>
>>Starting with Maven 2.0, plugins can be written in Java or any of a number
>>of scripting languages. Additionally, Maven tries to stay out of the way
>>of the programmer with its new Mojo API. This opens up the opportunity for
>>many Mojos to be reused outside of Maven, or bridged into Maven from
>>external systems like Ant.
>></snip>
>>
>>The first line states a fact - that Maven plugins can now be written in
>>plain Java. The second line doesnt suggest anything to me besides the
>>irritating name-dropping "Mojo API". The third line adds further confusion
>>by the usage "many Mojos" planting the supiscion that this things called
>>"Mojo" might be more than an API!
>>
>>Two paragraph later, I see:
>><snip>
>>As mentioned before, each Plugin - or packaged set of Mojos ..
>></snip>
>>
>>Ah! so thats it - Mojo is what constitues a Maven plugin - and there might
>>be some API to write these.
>>
>>It would have been much less intimidating had this fact be stated upfront.
>>
>>A note here - the term "plugin" was did not need any introduction to me -
>>because it is a widely one used in the software scene. At this point I
>>don't even know what a Maven plugin can do - yet I have a vague notion
>>that a plugin might be something that enhances the out-of-the-box
>>behaviour of Maven.
>>
>>The same familiarity does not apply to the term "Mojo" - I am guessing
>>here, but I think the Maven team invented the term. If so, kindly desrcibe
>>it fully instead of confusing the reader.
>>
>>--
>>This message is automatically generated by JIRA.
>>-
>>If you think it was sent incorrectly contact one of the administrators:
>>   http://jira.codehaus.org/secure/Administrators.jspa
>>-
>>For more information on JIRA, see:
>>   http://www.atlassian.com/software/jira
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>For additional commands, e-mail: dev-help@maven.apache.org
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


RE: [jira] Created: (MNG-1290) What is a Mojo?

Posted by Vincent Massol <vm...@pivolis.com>.
Hi Thomas,

We need to put that up on the site (probably in
http://maven.apache.org/glossary.html) but just FYI:

- Mojo = a java class implementing the org.apache.maven.plugin.Mojo
interface. This is the base class to implement a goal in Maven2.

- Goal = what you call from the command line to execute a build action. For
example: "compiler:compile", "site:site", "clean:clean", etc.

- Plugin = a set of Mojos packaged in a jar

Hope it helps,
-Vincent

> -----Original Message-----
> From: Binil Thomas (JIRA) [mailto:jira@codehaus.org]
> Sent: dimanche 23 octobre 2005 14:33
> To: dev@maven.apache.org
> Subject: [jira] Created: (MNG-1290) What is a Mojo?
> 
> What is a Mojo?
> ---------------
> 
>          Key: MNG-1290
>          URL: http://jira.codehaus.org/browse/MNG-1290
>      Project: Maven 2
>         Type: Bug
>   Components: documentation
>     Versions: 2.0
>  Reporter: Binil Thomas
> 
> 
> On http://maven.apache.org/developers/mojo-api-specification.html page
> titled "Mojo API", I see :
> 
> <snip>
> Starting with Maven 2.0, plugins can be written in Java or any of a number
> of scripting languages. Additionally, Maven tries to stay out of the way
> of the programmer with its new Mojo API. This opens up the opportunity for
> many Mojos to be reused outside of Maven, or bridged into Maven from
> external systems like Ant.
> </snip>
> 
> The first line states a fact - that Maven plugins can now be written in
> plain Java. The second line doesnt suggest anything to me besides the
> irritating name-dropping "Mojo API". The third line adds further confusion
> by the usage "many Mojos" planting the supiscion that this things called
> "Mojo" might be more than an API!
> 
> Two paragraph later, I see:
> <snip>
> As mentioned before, each Plugin - or packaged set of Mojos ..
> </snip>
> 
> Ah! so thats it - Mojo is what constitues a Maven plugin - and there might
> be some API to write these.
> 
> It would have been much less intimidating had this fact be stated upfront.
> 
> A note here - the term "plugin" was did not need any introduction to me -
> because it is a widely one used in the software scene. At this point I
> don't even know what a Maven plugin can do - yet I have a vague notion
> that a plugin might be something that enhances the out-of-the-box
> behaviour of Maven.
> 
> The same familiarity does not apply to the term "Mojo" - I am guessing
> here, but I think the Maven team invented the term. If so, kindly desrcibe
> it fully instead of confusing the reader.
> 
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
>    http://jira.codehaus.org/secure/Administrators.jspa
> -
> For more information on JIRA, see:
>    http://www.atlassian.com/software/jira
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org