Re: Allowed characters in GAV and how/where to sanitize?

2018-01-09 Thread Hervé BOUTEMY
notice that Central contains artifacts produced by Maven but also by other tools: I did some analysis myself and found strange things also that are clearly not produced by Maven. Scala for example produces some artifacts that I doubt could be referenced by Maven. Then: what do we call "broken"?

Re: Maven site edit next steps

2018-01-09 Thread Hervé BOUTEMY
thank you Plamen: you helped me find my mistake = the versions order in the GitHub url is not the same as GitWeb (prev...current in GitHub and current&prev in GitWeb...) now the page seems good: http://maven.apache.org/pom-archives/asf-LATEST/ Regards, Hervé Le mardi 9 janvier 2018, 18:59:14

Re: Allowed characters in GAV and how/where to sanitize?

2018-01-09 Thread Robert Scholte
The org.apache.maven.*project*.validation.ModelValidator is the Maven2 validator. In Maven3 it is placed in maven-compat, but from there it calls org.apache.maven.model.validation.ModelValidator The maven-deploy-plugin is still compatible with Maven2, hence it refers to the old validator. B

Re: Maven site edit next steps

2018-01-09 Thread Plamen Totev
Hi, On 1/9/2018 3:25 AM, Hervé BOUTEMY wrote: > > I tried to integrate both [1], with GitWeb as "diff" and GitHub as "commits". > But the GitHub comparison does not work well: then I put it only on HEAD. > > I don't know if this is due to my recent rework of tags for the repo, but > GitHub does n

Re: Allowed characters in GAV and how/where to sanitize?

2018-01-09 Thread Andreas Sewe
Hi Stephen, > In an url path segment space is mapped to + not quite. This holds only for the query part of an URI which is typically encoding according to the application/x-www-form-urlencoded scheme. Elsewhere in a URI, e.g., the path component, a space is simply percent-encoded a %20. > The re

Re: Allowed characters in GAV and how/where to sanitize?

2018-01-09 Thread Stephen Connolly
In an url path segment space is mapped to + The repo manager should be blocking those... likely not doing it’s job. We probably should also barf on : in a version. There is validation on artifactId and groupId when last I checked On Tue 9 Jan 2018 at 09:59, Andreas Sewe wrote: > Hi Maven devel

Allowed characters in GAV and how/where to sanitize?

2018-01-09 Thread Andreas Sewe
Hi Maven developers, doing a large-scale analysis of Maven Central, I've come across a couple of "weird" GAVs like this one: groupId=com.knappsack, artifactId=swagger4spring-web, version=mvn+release:perform [1]. The colon in the version raises the question as to the allowed characters in the diff