Just wanted to express my opinion about new plugins.Good call! XDoclet2's strategy is to delegate plugin development, maintenance and distribution to 3rd party vendors/projects. This increases the probability of plugins keeping up to date with the product they relate to, and lets the core team focus on the core. XDoclet2 will only maintain a very very sparse set of plugins.
I don't think that we should add more plugins to maven, unless they are really "core plugins".
I think we have quite a lot of dead plugins and many broken plugins,
I like more the idea of having this plugin elsewhere, so original plugin authors can take responsibility.
Knowing Aslak's skills I have no doubt that Maven team can give him access right to CVS repository to let him maintain this plugin but I want to discuss general policy regarding this subject.
I think Aslak has a lot of experience with such problems from XDoclet project. Simply any plugin which is based on external libraries is very sensitive to any changes in those libraries. For example Hibernate, Torque, JBoss plugins will be broken once there is minor change in those project. Keeping all plugin up to date in enormous work.
From the other hand I feel that Maven should have a catalog of known"foreign" plugins ( in form both of web site, and machine readable file format (XML ?), so any plugin can be downloaded automatically)
This will not only improve quality of code which is kept in our CVS repository, but also will increase the number of people which can actively work on plugins and having cvs access rights, so also plugin will be better.
What you think?
I think Maven could benefit from a similar strategy, as could many other projects/products.
However, there is a crucial thing that needs to be in place before this can be truly effective: Transparency for the users. They shouldn't have to trawl the web for plugins and documentation in a gazillion different places. It should be centralised.
That means some service where plugins (and documentation) can be registered, and some mechanism that can actually retrieve them from wherever they live (not only at ibiblio, but anywhere!)
This is a concept that applies to a lot of different platforms: Maven, XDoclet, Ant, IDEs, you name it. Put in other words, the aforementioned "containers" should be able to locate and access "components". And there should be a nice way for plugin developers for various platforms to register their plugin.
What I'm thinking about here is a lookup-service that runs as a server, and can be used by various platforms. Some kind of web service thingy, but not quite. I'd like to hear people's thought about this and whether you think a new project should be sparked off somewhere to implement (and possibly host) such services.
Michal
-----Original Message----- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 8:54 PM To: 'Maven Developers List' Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Simian Plugin (fully documented and ready to use)
Hi Aslak,
I love the idea of CPD/Simian. However, before we can commit anything here we would need agreement from redhillconsulting.com that we can put the simian jar in the Maven remote repository on ibiblio.
If we don’t get this agreement, we could still store this plugin in the SF mavne-plugins project and users would need to download the simian jar and put it manually in their local repository.
Thanks -Vincent
)-----Original Message----- From: Aslak Hellesøy [mailto:[EMAIL PROTECTED] Sent: 24 June 2003 13:58 To: Maven Developers List Cc: [EMAIL PROTECTED] Subject: Simian Plugin (fully documented and ready to use)
It seems Maven's JIRA still doesn't notify this list, so here I go...
Simian (http://www.redhillconsulting.com.au/products/simian/index.html
is a great little tool that detects duplicate source code. Very muchfaster.
like PMD's CPD (http://pmd.sourceforge.net/cpd.html), but a _lot_
somethingI have written a Maven report plugin for Simian that I'd like to contribute to Maven. Have a look at some sample reports:
http://www.picocontainer.org/simian-report.html http://www.nanocontainer.org/simian-report.html
It would be really nice to have the Simian Report included in the
standard reports, as it reveals refactoring candidates and is
every sound project should have!
It's all in JIRA: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-516
Cheers, Aslak
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------- Klikaj!!! I skorzystaj!!! >>> http://link.interia.pl/f1739
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
