I think that would help.
Today the classpath issues seem greater with reporter (AbstractReporter)
plugins than plain Mojo plugins.
Regards,
Garvin LeClaire
[EMAIL PROTECTED]
John Casey wrote:
I think this issue would go away if we could write a plugin-facilities
api that gave easy access to the things plugins need to do in most
cases. In other words, publish a formal, public api for Maven for the
plugin developer. While it'd be nice to have full design docs for all
of Maven, in 90% of cases this wouldn't help the plugin developer...it
would only serve to create a new haystack to poke through (this one in
HTML rather than Java). If we can be a little more selective this, and
provide a plugin-oriented api for common tasks like resolving
artifacts, building projects, etc. then document that, we'd probably
alleviate the problems for 90% of users.
-john
On May 2, 2008, at 4:50 PM, Garvin LeClaire wrote:
I find I have to search in a lot of places and dig deep into the
code to find out information when writing plugins.
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
rss: http://feeds.feedburner.com/ejlife/john
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
