Re: fixing the list of artifacts in maven-metadata.xml

[Anders Hammar]

This is very often an issue. I know for sure that Nexus can fix this so you
could ask Sonatype via Jira. That would rebuild old data.

For future releases I believe this is the correct way of fixing this in
m-deploy-p:
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#updateReleaseInfo

/Anders

On Tue, Mar 6, 2018 at 8:06 AM, Hervé BOUTEMY  wrote:

> Hi,
>
> In Jansi, there is an issue with the list of artifacts versions: some old
> artifacts published on Central are not listed in the metadata (I don't know
> why/when they disappeared).
> Here is the maven-metadata.xml [1] which lists versions 1.12 to 1.17
> But the directory contains also versions 1.2.1to 1.11
>
> This causes issues for people using version ranges (g, I hate version
> ranges for dependencies).
>
> Then I have a stupid simple question that I don't know the answer: how to
> fix
> the issue?
> Can it be fixed during a future release by tweaking local metadata.xml?
> Should it be fixed at repository manager level? (Jansi is using OSSRH)
> During a
> release or independently of a release?
> Should it be fixed by a Jira issue to Sonatype? MVNCENTRAL or OSSRH [3]?
>
> Regards,
>
> Hervé
>
> [1] http://central.maven.org/maven2/org/fusesource/jansi/
> jansi/maven-metadata.xml
>
> [2] http://central.maven.org/maven2/org/fusesource/jansi/jansi/
>
> [3] http://central.sonatype.org/pages/help.html
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

fixing the list of artifacts in maven-metadata.xml

[Hervé BOUTEMY]

Hi,

In Jansi, there is an issue with the list of artifacts versions: some old 
artifacts published on Central are not listed in the metadata (I don't know 
why/when they disappeared).
Here is the maven-metadata.xml [1] which lists versions 1.12 to 1.17
But the directory contains also versions 1.2.1to 1.11

This causes issues for people using version ranges (g, I hate version 
ranges for dependencies).

Then I have a stupid simple question that I don't know the answer: how to fix 
the issue?
Can it be fixed during a future release by tweaking local metadata.xml?
Should it be fixed at repository manager level? (Jansi is using OSSRH) During a 
release or independently of a release?
Should it be fixed by a Jira issue to Sonatype? MVNCENTRAL or OSSRH [3]?

Regards,

Hervé

[1] 
http://central.maven.org/maven2/org/fusesource/jansi/jansi/maven-metadata.xml

[2] http://central.maven.org/maven2/org/fusesource/jansi/jansi/

[3] http://central.sonatype.org/pages/help.html

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: MNG-6370

[Robert Scholte]

Looks like it should be very easy to write a unittest for this.
Please do so as well.

thanks,
Robert

On Tue, 06 Mar 2018 01:47:23 +0100, Michael Osipov   
wrote:



Who seconds MNG-6370 for 3.5.4?

A simple bug fix, all ITs pass locally here.

Michael

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: MNG-6370

[Hervé BOUTEMY]

+1

Regards,

Hervé

Le mardi 6 mars 2018, 01:47:23 CET Michael Osipov a écrit :
> Who seconds MNG-6370 for 3.5.4?
> 
> A simple bug fix, all ITs pass locally here.
> 
> Michael
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.20.1

[Hervé BOUTEMY]

built from sources (with classic "mvn -Prun-its verify" & Java 8) and got 2 
failing unit tests:
Failed tests:   
checkFileNamesWithUnicode(org.apache.maven.surefire.its.UnicodeTestNamesIT): 
Did not find expected message in log
  
shouldRunTwoSuitesInParallel(org.apache.maven.surefire.its.jiras.Surefire1177TestngParallelSuitesIT):
 
log pattern does not match nTimes(..)

Unicode tests si already known, and I don't know for the second issue

I don't see this as a blocker

+1

Regards,

Hervé

Le samedi 3 mars 2018, 12:42:48 CET Tibor Digana a écrit :
> Hi,
> 
> We solved 33 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927
> rsion=12341630
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status
> +%3D+Open+ORDER+BY+priority+DESC
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1402/
> https://repository.apache.org/content/repositories/maven-1402/org/apache/mav
> en/surefire/surefire/2.21.0/surefire-2.21.0-source-release.zip
> 
> Source release checksum(s):
> surefire-2.21.0-source-release.zip sha1:
> 6927024eefa0b8c80dee70efa014f1f421d7844b
> 
> Staging site:
> http://maven.apache.org/surefire-archives/surefire-LATEST/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> Cheers
> Tibor



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: MNG-6370

[Olivier Lamy]

+1

On 6 March 2018 at 10:47, Michael Osipov  wrote:

> Who seconds MNG-6370 for 3.5.4?
>
> A simple bug fix, all ITs pass locally here.
>
> Michael
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

MNG-6370

[Michael Osipov]

Who seconds MNG-6370 for 3.5.4?

A simple bug fix, all ITs pass locally here.

Michael

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] maven pull request #161: [MNG-6370] Fix typo in list filtering ConcurrencyDe...

[slachiewicz]

GitHub user slachiewicz opened a pull request:

https://github.com/apache/maven/pull/161

[MNG-6370] Fix typo in list filtering ConcurrencyDependencyGraph.getU…

…nfinishedProjects

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/slachiewicz/maven fix/MNG-6370

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven/pull/161.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #161


commit 683504fdcd0d901a06c9b49463175d9076299925
Author: Sylwester Lachiewicz 
Date:   2018-03-05T21:24:14Z

[MNG-6370] Fix typo in list filtering 
ConcurrencyDependencyGraph.getUnfinishedProjects




---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: jira contributor status?

[Sean Busbey]

Hi Robert!

Would you mind if we continue the review on MJAVADOC-444?

Per the guidance on that page you mentioned, I'd like to avoid sending multiple 
messages here and I have questions about the need and form for tests in this 
specific case. If you don't mind, I'd quote your response from here on the jira 
and then provide follow up.

One small matter of clarification, I was talking specifically about the JIRA 
project role of contributor (or its equivalent if the Maven project uses some 
bespoke set of jira project configurations). I'm not looking to apply the 
patch, merely place the jira into the common status used to indicate "there's a 
patch here that should be looked at"; often times such status also triggers 
automated testing that's needed prior to formal review. Apologies if the Maven 
project does not use such status or tooling.


On 2018/03/02 15:32:20, "Robert Scholte"  wrote: 
> hi Sean,
> 
> thank you for the patch, which already makes you a contributor.
> To be able to apply patches you need to be a Maven committer.
> If you want to become a committer, please read the Guide Commmitter  
> School[1]
> In case of your patch for MJAVADOC-444, you have to focus on #2 and  
> further.
> 
> thanks,
> Robert
> 
> [1] https://maven.apache.org/guides/development/guide-committer-school
> 
> On Fri, 02 Mar 2018 15:36:15 +0100, Sean Busbey  wrote:
> 
> > Hi!
> >
> > Could someone give me contributor status in jira so I can assign  
> > MJAVADOC-444 to myself and put it in patch available status?
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven 3.5.3

[Stephen Connolly]

+1

I'll tally up the votes this evening and push the release

On 4 March 2018 at 16:01, Stephane Nicoll  wrote:

> I already cast my +1 but, +1 to release as is.
>
> S.
>
> On Fri, Mar 2, 2018 at 8:55 PM,  wrote:
>
> > the issue is a multi-threading issue on Windows Jansi, then this affects
> > people on Windows who try to use parallel build.
> >
> > I can commit on Jansi but not do a release: I can see this if a quick
> > 1.17.1 is feasible...
>


Hervé could you add the details of this issue to the draft release notes?
Or even just somebody describe the details here and I will update the
release notes this evening myself.




> >
> > Regards,
> >
> > Hervé
> >
> > - Mail original -
> > De: "Stephen Connolly" 
> > À: "Maven Developers List" 
> > Envoyé: Vendredi 2 Mars 2018 09:12:09
> > Objet: Re: [VOTE] Release Apache Maven 3.5.3
> >
> > On Fri 2 Mar 2018 at 07:57, Sylwester Lachiewicz 
> > wrote:
> >
> > > Hi,
> > > yes i was able to reproduce both errors (Dan and Guillaume) and fixes
> are
> > > commited to JAnsi.
> > > If someone one to retest - please build JAnsi from master.
> > >
> > > Fix #107 also shoud help with reseting colors after Ctrl-C.
> > >
> > > https://github.com/fusesource/jansi/issues/110
> > > https://github.com/fusesource/jansi/issues/107
> > >
> >
> > @Hervé wdyt should we release as is and we can 3.5.4 when jansi has a new
> > release or shall we drop, wait and respin?
> >
> >
> > > Regards,
> > > Sylwester
> > >
> > > czw., 1 mar 2018 o 19:45 użytkownik Dan Tran 
> > napisał:
> > >
> > > > Hi all
> > > >
> > > > Sylwester Lachiewicz provided a fix for jansi 1.18-SNAPSHOT  which
> > > resolves
> > > > my issue.  I am not able to reproduce antrun issue
> > > >
> > > >
> > > > -Dan
> > > >
> > > > On Thu, Mar 1, 2018 at 5:00 AM, Stephane Nicoll <
> > > stephane.nic...@gmail.com
> > > > >
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > Thanks,
> > > > > S.
> > > > >
> > > > > On Sat, Feb 24, 2018 at 11:01 PM, Stephen Connolly <
> > > > > stephen.alan.conno...@gmail.com> wrote:
> > > > >
> > > > > > On 24 February 2018 at 22:00, Stephen Connolly <
> > > > > > stephen.alan.conno...@gmail.com> wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > We solved 22 issues:
> > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > > > > version=12341428=Text=12316922
> > > > > > >
> > > > > > > There are 381 issues left in JIRA for Maven core:
> > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%
> > > > > > > 3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> > > > > > > 20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> > > > > > >
> > > > > > > Staging repo:
> > > > > > > https://repository.apache.org/content/repositories/maven-1401/
> > > > > > >
> > > > > > > The distributable binaries and sources can be found here:
> > > > > > > https://repository.apache.org/content/repositories/maven-
> > > > > > > 1401/org/apache/maven/apache-maven/3.5.3/
> > > > > > >
> > > > > > > Specifically the zip, tarball and source archives can be found
> > > here:
> > > > > > > https://repository.apache.org/content/repositories/maven-
> > > > > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.
> > 3-bin.zip
> > > > > > > https://repository.apache.org/content/repositories/maven-
> > > > > > >
> > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.
> 3-bin.tar.gz
> > > > > > > https://repository.apache.org/content/repositories/maven-
> > > > > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.
> > 3-src.zip
> > > > > > > https://repository.apache.org/content/repositories/maven-
> > > > > > >
> > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.
> 3-src.tar.gz
> > > > > > >
> > > > > > > The release artifacts are staged for distribution in:
> > > > > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.3
> > > > > > >
> > > > > > > Source release checksum(s):
> > > > > > > apache-maven-3.5.3-src.tar.gz sha1:
> > 60905d8b8b025b091f456ec25ad60d
> > > > > > da56c26ad5
> > > > > > > sha256:
> > > 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd10
> > > > > 7e19
> > > > > > > apache-maven-3.5.3-src.zip: sha1:
> a9be51d571165261dfb2e0c8ecc6b4
> > > > > > f1c4c96766
> > > > > > > sha256:
> > > 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7cc
> > > > > bd57
> > > > > > >
> > > > > > > Git tag:
> > > > > > > https://git-wip-us.apache.org/repos/asf?p=maven.git;a=
> commit;h=
> > > > > > > 3383c37e1f9e9b3bc3df5050c29c8aff9f295297
> > > > > > >
> > > > > > > Staging site:
> > > > > > > https://maven.apache.org/components/ref/3-LATEST/
> > > > > > >
> > > > > > > Vote open for 72 hours.
> > > > > > >
> > > > > > > [ ] +1
> > > > > > > [ ] +0
> > > > > > > [ ] -1
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > >