Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.11.3

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.11.3

Robert Scholte-8
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 <[hidden email]> 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
[hidden email]

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

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.11.3

Elliotte Rusty Harold
Let's try this one more time. I updated Jira and regenerated the
release notes. Nothing else has changed:

Hi,

We solved 3 issues:

[MSHARED-949] - dependency:analyze should recommend narrower scope
where possible
[MSHARED-948] - Update link to Jira
[MSHARED-932] - Remove JMock dependency

There are still five issues left in JIRA:
https://issues.apache.org/jira/browse/MSHARED-916?jql=project%20%3D%20MSHARED%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20maven-dependency-analyzer


Staging repo:
https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/
https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/maven-dependency-analyzer-1.11.3-source-release.zip

Source release checksum(s):
maven-dependency-analyzer-1.11.3-source-release.zip sha512:
84a13538660dd877e6ab7b626778267b4ddf06581752235e8e4e282306a6c896e7d737795a81fd05a804e77fa685ddf4891b20c73561bbc741ab671b5ccf75b8

Staging site:
https://maven.apache.org/shared-archives/maven-dependency-analyzer-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1


On Wed, Aug 5, 2020 at 4:31 PM Elliotte Rusty Harold <[hidden email]> wrote:

>
> Hi,
>
> We solved 2 issues:
>     * [MSHARED-932] Remove JMock dependency
>     * [MDEP-708] dependency:analyze should recommend narrower scope
> where possible
>
> There are still five issues left in JIRA:
> https://issues.apache.org/jira/browse/MSHARED-916?jql=project%20%3D%20MSHARED%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20maven-dependency-analyzer
>
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/
> https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/maven-dependency-analyzer-1.11.3-source-release.zip
>
> Source release checksum(s):
> maven-dependency-analyzer-1.11.3-source-release.zip sha512:
> 84a13538660dd877e6ab7b626778267b4ddf06581752235e8e4e282306a6c896e7d737795a81fd05a804e77fa685ddf4891b20c73561bbc741ab671b5ccf75b8
>
> Staging site:
> https://maven.apache.org/shared-archives/maven-dependency-analyzer-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>
> --
> Elliotte Rusty Harold
> [hidden email]



--
Elliotte Rusty Harold
[hidden email]

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

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.11.3

Karl Heinz Marbaise-3
Hi,

+1 from me (binding)

Kind regards
Karl Heinz Marbaise
On 17.08.20 16:44, Elliotte Rusty Harold wrote:

> Ping. Can I get two more +1's on this? Once this is out, we'll be
> ready to release a new maven-dependency-plugin that reintroduces the
> verbose option for dependency:tree for the first time since Maven 2.
>
> On Mon, Aug 10, 2020 at 10:19 AM Elliotte Rusty Harold
> <[hidden email]> wrote:
>>
>> Let's try this one more time. I updated Jira and regenerated the
>> release notes. Nothing else has changed:
>>
>> Hi,
>>
>> We solved 3 issues:
>>
>> [MSHARED-949] - dependency:analyze should recommend narrower scope
>> where possible
>> [MSHARED-948] - Update link to Jira
>> [MSHARED-932] - Remove JMock dependency
>>
>> There are still five issues left in JIRA:
>> https://issues.apache.org/jira/browse/MSHARED-916?jql=project%20%3D%20MSHARED%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20maven-dependency-analyzer
>>
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/
>> https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/maven-dependency-analyzer-1.11.3-source-release.zip
>>
>> Source release checksum(s):
>> maven-dependency-analyzer-1.11.3-source-release.zip sha512:
>> 84a13538660dd877e6ab7b626778267b4ddf06581752235e8e4e282306a6c896e7d737795a81fd05a804e77fa685ddf4891b20c73561bbc741ab671b5ccf75b8
>>
>> Staging site:
>> https://maven.apache.org/shared-archives/maven-dependency-analyzer-LATEST/
>>
>> Guide to testing staged releases:
>> https://maven.apache.org/guides/development/guide-testing-releases.html
>>
>> Vote open for at least 72 hours.
>>
>> [ ] +1
>> [ ] +0
>> [ ] -1
>>
>>
>> On Wed, Aug 5, 2020 at 4:31 PM Elliotte Rusty Harold <[hidden email]> wrote:
>>>
>>> Hi,
>>>
>>> We solved 2 issues:
>>>      * [MSHARED-932] Remove JMock dependency
>>>      * [MDEP-708] dependency:analyze should recommend narrower scope
>>> where possible
>>>
>>> There are still five issues left in JIRA:
>>> https://issues.apache.org/jira/browse/MSHARED-916?jql=project%20%3D%20MSHARED%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20maven-dependency-analyzer
>>>
>>>
>>> Staging repo:
>>> https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/
>>> https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/maven-dependency-analyzer-1.11.3-source-release.zip
>>>
>>> Source release checksum(s):
>>> maven-dependency-analyzer-1.11.3-source-release.zip sha512:
>>> 84a13538660dd877e6ab7b626778267b4ddf06581752235e8e4e282306a6c896e7d737795a81fd05a804e77fa685ddf4891b20c73561bbc741ab671b5ccf75b8
>>>
>>> Staging site:
>>> https://maven.apache.org/shared-archives/maven-dependency-analyzer-LATEST/
>>>
>>> Guide to testing staged releases:
>>> https://maven.apache.org/guides/development/guide-testing-releases.html
>>>
>>> Vote open for at least 72 hours.
>>>
>>> [ ] +1
>>> [ ] +0
>>> [ ] -1
>>>
>>>
>>> --
>>> Elliotte Rusty Harold
>>> [hidden email]
>>
>>
>>
>> --
>> Elliotte Rusty Harold
>> [hidden email]
>
>
>

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

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.11.3

Sylwester Lachiewicz
In reply to this post by Elliotte Rusty Harold
+1(non binding)

pon., 17 sie 2020, 17:12 użytkownik Olivier Lamy <[hidden email]> napisał:

> +1
>
> On Mon, 17 Aug 2020 at 10:45 pm, Elliotte Rusty Harold <[hidden email]
> >
> wrote:
>
> > Ping. Can I get two more +1's on this? Once this is out, we'll be
> >
> > ready to release a new maven-dependency-plugin that reintroduces the
> >
> > verbose option for dependency:tree for the first time since Maven 2.
> >
> >
> >
> > On Mon, Aug 10, 2020 at 10:19 AM Elliotte Rusty Harold
> >
> > <[hidden email]> wrote:
> >
> > >
> >
> > > Let's try this one more time. I updated Jira and regenerated the
> >
> > > release notes. Nothing else has changed:
> >
> > >
> >
> > > Hi,
> >
> > >
> >
> > > We solved 3 issues:
> >
> > >
> >
> > > [MSHARED-949] - dependency:analyze should recommend narrower scope
> >
> > > where possible
> >
> > > [MSHARED-948] - Update link to Jira
> >
> > > [MSHARED-932] - Remove JMock dependency
> >
> > >
> >
> > > There are still five issues left in JIRA:
> >
> > >
> >
> https://issues.apache.org/jira/browse/MSHARED-916?jql=project%20%3D%20MSHARED%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20maven-dependency-analyzer
> >
> > >
> >
> > >
> >
> > > Staging repo:
> >
> > >
> >
> https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/
> >
> > >
> >
> https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/maven-dependency-analyzer-1.11.3-source-release.zip
> >
> > >
> >
> > > Source release checksum(s):
> >
> > > maven-dependency-analyzer-1.11.3-source-release.zip sha512:
> >
> > >
> >
> 84a13538660dd877e6ab7b626778267b4ddf06581752235e8e4e282306a6c896e7d737795a81fd05a804e77fa685ddf4891b20c73561bbc741ab671b5ccf75b8
> >
> > >
> >
> > > Staging site:
> >
> > >
> >
> https://maven.apache.org/shared-archives/maven-dependency-analyzer-LATEST/
> >
> > >
> >
> > > Guide to testing staged releases:
> >
> > >
> https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > >
> >
> > > Vote open for at least 72 hours.
> >
> > >
> >
> > > [ ] +1
> >
> > > [ ] +0
> >
> > > [ ] -1
> >
> > >
> >
> > >
> >
> > > On Wed, Aug 5, 2020 at 4:31 PM Elliotte Rusty Harold <
> [hidden email]>
> > wrote:
> >
> > > >
> >
> > > > Hi,
> >
> > > >
> >
> > > > We solved 2 issues:
> >
> > > >     * [MSHARED-932] Remove JMock dependency
> >
> > > >     * [MDEP-708] dependency:analyze should recommend narrower scope
> >
> > > > where possible
> >
> > > >
> >
> > > > There are still five issues left in JIRA:
> >
> > > >
> >
> https://issues.apache.org/jira/browse/MSHARED-916?jql=project%20%3D%20MSHARED%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20maven-dependency-analyzer
> >
> > > >
> >
> > > >
> >
> > > > Staging repo:
> >
> > > >
> >
> https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/
> >
> > > >
> >
> https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/maven-dependency-analyzer-1.11.3-source-release.zip
> >
> > > >
> >
> > > > Source release checksum(s):
> >
> > > > maven-dependency-analyzer-1.11.3-source-release.zip sha512:
> >
> > > >
> >
> 84a13538660dd877e6ab7b626778267b4ddf06581752235e8e4e282306a6c896e7d737795a81fd05a804e77fa685ddf4891b20c73561bbc741ab671b5ccf75b8
> >
> > > >
> >
> > > > Staging site:
> >
> > > >
> >
> https://maven.apache.org/shared-archives/maven-dependency-analyzer-LATEST/
> >
> > > >
> >
> > > > Guide to testing staged releases:
> >
> > > >
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > > >
> >
> > > > Vote open for at least 72 hours.
> >
> > > >
> >
> > > > [ ] +1
> >
> > > > [ ] +0
> >
> > > > [ ] -1
> >
> > > >
> >
> > > >
> >
> > > > --
> >
> > > > Elliotte Rusty Harold
> >
> > > > [hidden email]
> >
> > >
> >
> > >
> >
> > >
> >
> > > --
> >
> > > Elliotte Rusty Harold
> >
> > > [hidden email]
> >
> >
> >
> >
> >
> >
> >
> > --
> >
> > Elliotte Rusty Harold
> >
> > [hidden email]
> >
> >
> >
> > ---------------------------------------------------------------------
> >
> > To unsubscribe, e-mail: [hidden email]
> >
> > For additional commands, e-mail: [hidden email]
> >
> >
> >
> > --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>