So MDEP-708 is a request for a new feature, but that requires a change in 
maven-dependency-analyzer.
Nothing complicated, just a normal process:
Create a Jira issue for maven-dependency-analyzer in the MSHARED project, 
component maven-dependency-analyzer 
Link  MDEP-708 to it, saying it depends on that fix.
(And as you can see: there is a component for maven-dependency-analyzer  [1])


There is a 1:1 mapping for Jira to Git repo (and vice versa), but in case of 
shared libraries, git repositories are linked to components of MSHARED.
MDEP is only about the Maven Dependency Plugin.
For the complete list, see Maven+JIRA+issues+overview[2], or in case or shared 
libraries it's main page[3] (with mapping to both Jira and Git)

thanks,
Robert

[1] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20component%20%3D%20maven-dependency-analyzer
 

[2] https://cwiki.apache.org/confluence/display/MAVEN/Maven+JIRA+issues+overview
[3] https://maven.apache.org/shared/index.html

On 7-8-2020 15:06:40, Elliotte Rusty Harold <[email protected]> wrote:
On Fri, Aug 7, 2020 at 7:39 AM Robert Scholte wrote:
>
> Should MDEP-708 be moved or cloned? It must be part of 
> https://issues.apache.org/jira/projects/MSHARED/versions/12348642
>

I can clone it, but it's a weird one. First, it's a single RFE that
extends across more than one project. Second maven-dependency-analyzer
doesn't have its own component. Its bugs appear arbitrarily in either
MSHARED or MDEP (with different labels in each) depending on who filed
them when:

https://issues.apache.org/jira/browse/MDEP-712?filter=-2&jql=status%20%3D%20Open%20AND%20reporter%20in%20(currentUser())%20order%20by%20created%20DESC

In general, it doesn't appear accurate to assume that git
repos/project map 1:1 to JIRA components. If that's something that
needs to be true, then a PMC member is going to have to invest some
time cleaning this up. Non-PMC members don't have permissions to work
with JIRA at this level.

--
Elliotte Rusty Harold
[email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to