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.
-----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 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 plugin, the answer isn't as clear. That's fine when users report issues, but it'd be nice to be able to either move or link the issue to another within the shared component. There's development that can be done within the shared component where it wouldn't necessarily make sense to raise patches against the plugin. Also, it would provide changelogs for shared components. Mark --------------------------------------------------------------------- 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]
