I think that there might be an advantage in declaring the maven
plugins to be an independent top-level that we release after a release
of the core product, (and perhaps release in-between as needed).
There's a pattern to maven plugin projects at maven.apache.org or the
Mojo project at codehaus,
On Monday, December 12, 2011 8:11:43 AM Benson Margulies wrote:
I think that there might be an advantage in declaring the maven
plugins to be an independent top-level that we release after a release
of the core product, (and perhaps release in-between as needed).
There's a pattern to maven
I'll answer your question with a question.
Could the maven plugins be in the build last, so that they could have
the same sort of integration tests as all the maven plugins at Maven
and Mojo? If so, I completely withdraw my idea. If not, I guess I
can't make a really good argument, and the tests
On Monday, December 12, 2011 11:41:34 AM Benson Margulies wrote:
I'll answer your question with a question.
Could the maven plugins be in the build last, so that they could have
the same sort of integration tests as all the maven plugins at Maven
and Mojo?
Well, no. We need the plugins
On Tue Dec 13 00:56:21 2011, Daniel Kulp wrote:
On Monday, December 12, 2011 11:41:34 AM Benson Margulies wrote:
I'll answer your question with a question.
Could the maven plugins be in the build last, so that they could have
the same sort of integration tests as all the maven plugins at Maven
