Hi,
I created a SourceForge project to host non-core
Maven plugins. It is called "maven-plugins" and you
can reach it at http://maven-plugins.sourceforge.net,
or if you want the SourceForge page,
http://www.sourceforge.net/projects/maven-plugins .
The project has a basic homepage (thanx Maven for
allowing projects' docs to be build so quickly!)
The goal beneath this project is to centralize the
development of Maven plugins. I am conscious that
those plugins should live under Maven's umbrella, as
I am conscious that Maven should be a Jakarta top
project.
Maven reached a point where everything is a plugin,
which means that everything is independant and can
live without other plugins. Maven provides *default*
plugins used to build & test the project, generate
docs about it, etc.
Though, people started developing plugins for Maven
that couldn't be included in Maven's core plugins
base, because they didn't fit all users' needs.
Moreover, Jakarta is not very keen on hosting GPL or
other viral Licenses jars or code on its servers, as
this may lead to a License nightmare.
This leads to a situation where people develop good
plugins but can't publish them.
This was the main reason for the creation of this
project. This project will gather all the plugins
that people need (and want), without affecting
Maven's core.
The organization of the project is as follows:
- the project is a Maven project, so that you can
generate the website from it (I started the process
that will allow each plugin docs to be linked to the
main page). The project docs will include HOWTOs to
make Maven plugins, and tips & tricks that Maven
plugin developers use everyday.
- each plugin is under maven-plugins/${plugin.name},
so that if you want to create a Python plugin, you
will name it maven-plugins/python/. Each plugin is a
Maven project in itself, just like current Maven
plugins are Maven projects.
Every plugin will have a mechanism that allows it to
be easily installed, independently from the project
itself.
I am also conscious that people started to make
individual projects for plugins they develop (I am
thinking about the JUNITPP plugin developped by
Siegfried Goeschl), but I think that we can gather
more developers and users if we host all plugins
under a single project. The knowledge base needed
to build Jelly scripts (and thus, Maven plugins)
could be shared by all plugin developers without
having to crawl over dozens of projects.
The project currently hosts 2 plugins: Wiki and RPM.
The Wiki plugin generates a UseModWiki
<http://www.usemod.com/cgi-bin/wiki.pl> Perl Script
that has the same look and fell as the site (including
the navigation bar on the left).
This plugin works for me, please try it and tell me
what's going wrong. :-) (I need that at work, so
please don't blame me if you think that's useless !)
The RPM plugin will generate RPM distributions. This
is not fully functional yet, as I have to face some
problems with RPM (for instance, RPM doesn't accept
version numbers with "-" characters in them).
I developped those plugins at home, with my home cvs
public server. So, those plugins are available on a
separate server, but I will never be able to have
a bandwith comparable to SourceForge or Apache,
which is why I included them in the SourceForge project.
I would like the project to host plugins like:
- JUNITPP
- PMD
- JRefactory
- a UML generation plugin (we need to find a good
opensource tool that does that in a way easy enough
to integrate with Ant and (preferably) Jelly)
- a kind of "site" plugin managing user-generated
reports and links in the navigation bar.
- a "python" plugin that compiles Python scripts to
Java (this programming language integrates well with
Java and allows programmers to make "proof of concept"
Java applications efficiently)
- any plugin ready to be published at any stage
(beta, etc.)
- anything that comes to your mind and can be useful
in a project management tool!
Optionnally, the project could host this kind of
plugins:
- a 3D project visualization tool that allows us to
navigate inside the project's informations and edit
files when we point our finder on them.
- an Artificial Intelligence plugin that debugs an
application for us, generates real javadoc comments,
and suggests better ways of programming.
- a Coffee Maker plugin that manages a coffee machine
and makes us the best coffee we ever drank, remembering
our very personal tastes (1 or 2 sugars ? how many
teaspoons of coffee ?)
Of course those latter plugins are completely optionnal
and can wait a year or two ! ;-)
In the future, when Maven is a Jakarta top project,
and when it can have a kind of subproject for
plugins (which should happen really soon, before the
1.0 release I hope), the whole project will move to
Jakarta if accepted. Otherwise, it will live as an
independent project, which is cool.
By that time it should hopefully be ready enough to
be integrated as-is to Jakarta.
For now, every Maven developer who gives me its
SourceForge Id will be immediately integrated to the
project as a developer. Other developers will be
integrated following Apache mechanisms (contributions,
votes, etc.) so that it is consistent when we move
back to Jakarta.
Sorry for that very long mail ;-)
Please feel free to give comments/criticisms.
Thanks,
St�phane
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais !
Yahoo! Mail : http://fr.mail.yahoo.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
