You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Mark Hobson <ma...@gmail.com> on 2007/03/23 22:17:29 UTC
Shared component issues
Hi there,
Where's the best place to raise JIRA issues against shared components?
The pom points to MNG, but there's no 'Shared Components' component
in that JIRA project. Would it be best to create a JIRA component or
a new JIRA project with components per shared component?
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Shared component issues
Posted by Mark Hobson <ma...@gmail.com>.
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 a problem with the MOJO JIRA project - it makes it
hard to set the version information against issues since the versions
would have to be the union of all plugin versions.
On 23/03/07, Jason van Zyl <ja...@maven.org> wrote:
> Want me to make a JIRA project for the shared components?
If you think that's the best way, although I tend to agree with Brian
regarding a JIRA project per shared component. If you're doing the
latter then I just need one for maven-dependency-analyzer now.
Thanks,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Shared component issues
Posted by Jason van Zyl <ja...@maven.org>.
Want me to make a JIRA project for the shared components?
Jason.
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.
>
>
> -----Original Message-----
> From: Mark Hobson [mailto:markhobson@gmail.com]
> Sent: Friday, March 23, 2007 5:42 PM
> To: Maven Developers List
> Subject: Re: Shared component issues
>
> On 23/03/07, Brian E. Fox <br...@reply.infinity.nu> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Shared component issues
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
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:markhobson@gmail.com]
Sent: Friday, March 23, 2007 5:42 PM
To: Maven Developers List
Subject: Re: Shared component issues
On 23/03/07, Brian E. Fox <br...@reply.infinity.nu> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Shared component issues
Posted by Mark Hobson <ma...@gmail.com>.
On 23/03/07, Brian E. Fox <br...@reply.infinity.nu> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Shared component issues
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
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.
-----Original Message-----
From: Mark Hobson [mailto:markhobson@gmail.com]
Sent: Friday, March 23, 2007 5:17 PM
To: Maven Developers List
Subject: Shared component issues
Hi there,
Where's the best place to raise JIRA issues against shared components?
The pom points to MNG, but there's no 'Shared Components' component
in that JIRA project. Would it be best to create a JIRA component or
a new JIRA project with components per shared component?
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org