On 4 Sep 07, at 11:55 AM 4 Sep 07, Dan Tran wrote:
What are the impacts of plugins with use <extensions> as a way to
override
the default build lifecycle? ie ( pde-maven-plugin, native-maven-
plugin )
There's another use case and that should also be made more clear, but
ideally plugin metadata should say a contribution is being made and
then we can act accordingly. So again another example of how
extensions are generally confusing, I forgot about that use case.
-D
On 9/4/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
+1
-----Original Message-----
<SNIP>
For 2.1 I would like to use providers stated as dependencies which
they are (easy to do in corporate builds), and the rest are core
components. John has been working on some active collections, and I
think they can be finished so that we could clarify how the system is
augmented by 2.1-alpha-2.
Anyone have any problems with this clarification?
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
