On 23 Mar 07, at 5:49 PM 23 Mar 07, Brian E. Fox wrote:
True. I don't see then why we wouldn't have a module for each shared
component like we do with plugins. Having a single shared project will
tend to get cluttered with issues and makes it harder to prepare for
releases etc.
I agree, this is
tered with issues and makes it harder to prepare for
releases etc.
-Original Message-
From: Mark Hobson [mailto:[EMAIL PROTECTED]
Sent: Friday, March 23, 2007 5:42 PM
To: Maven Developers List
Subject: Re: Shared component issues
On 23/03/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
I th
PROTECTED]
Sent: Friday, March 23, 2007 5:42 PM
To: Maven Developers List
Subject: Re: Shared component issues
On 23/03/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> I think it is likely that users will end up reporting the issues
against
> plugins that expose shared components (aka
On 23/03/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
I think it is likely that users will end up reporting the issues against
plugins that expose shared components (aka dependency-plugin and
dependency-analyzer) because the users don't know that the shared
components exist. For shared components
I think it is likely that users will end up reporting the issues against
plugins that expose shared components (aka dependency-plugin and
dependency-analyzer) because the users don't know that the shared
components exist. For shared components not exposed directly to the user
through any single plu
