gnodet commented on PR #1298: URL: https://github.com/apache/maven/pull/1298#issuecomment-1795431208
> > > This does not look wrong. What is the motivation behind this? > > > > > > The problem seems to be that sonatype oss release validation fail staging repositories deployed with Maven 4. The issue is there is now more than one .pom file in the repo. > > That really feels like fixing the symptom... It is. Maybe we should just do nothing and let Sonatype fix on their side ? > > > How will the attached artifact looked like if then main POM is still `foo.pom`? > > > > > > `foo-build-pom.xml` ? > > This names is reasonable since it is the original one with a classifier. Does `foo.build-pom` makes sense, too? Yes, I don't have a clear opinion. I wonder if the `-` in `build-pom` used as a classifier could cause parsing problems, as `-` is used to separate the artifactId from the classifier in `foo-build-pom.xml`... Is that why you suggested `foo.build-pom` ? I think the best would still be the current state, i.e. `foo-build.pom` ... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
