About Mojo

  1. Why was the Mojo project created?
  2. How can we communicate?
  3. What is the sandbox?
  4. Where is the sandbox?
Why was the Mojo project created?

Well, this allows a bunch of people, not necessarily involved with the Maven project, to come along and build some plugins. They are free to look after just that plugin, though I hope that they'll get involved in the community of people here and work on other plugins as well as help maintain the common infrastructure like the site.

Maven plugins may also be developed here because they are not compatible with the Apache license. Plugin authors may choose to use other licenses (BSD, GPL, MPL ...) to license their work or may be forced to because of the nature of the plugin and its dependencies. These plugin authors are responsible for working with their plugins license but the mailing lists are a great place to get help if people get confused on what can or can not be done within the mojo project.

[top]
How can we communicate?
  • Use the mailing list where possible as more people can get involved and so an archive is available.
  • If it is specific to a plugin, prefix the subject with the plugin name, e.g. [jalopy].
  • Use IRC (irc://irc.codehaus.org on #maven) for realtime discussion. Try and summarise and send it to the list if there was some decisions were made there.
[top]
What is the sandbox?

The sandbox is used to "incubate" new plugins. Sandbox plugins will not be released to the repositories and if you are interrested in trying it out you will probably have to build it from source.

All new code should be put in the sandbox so we can make sure that the plugin uses the correct code style, that is has proper documentation and generally has the expected quality.

[top]
Where is the sandbox?

Most plugins have sites published and linked from the Mojo Plugin List. Others can be found in the SVN repository.

[top]