gnodet commented on issue #11367:
URL: https://github.com/apache/maven/issues/11367#issuecomment-3504895878
> I eventually identified the root cause: our Artifactory instance (7.98.13
Server) does not recognize the `subprojects` tag in the `build` pom:
>
> ```
> {
> "errors" : [ {
> "status" : 409,
> "message" : "Failed to read POM for '...-build.pom': Unrecognised tag:
'subprojects' (position: START_TAG seen ...</packaging> <subprojects>...
@1:633) ."
> } ]
> }
> ```
>
> I'm not sure whether recent Artifactory versions are compatible with the
new Maven model.
>
> In Maven 4 documentation:
>
> > Version 4.1.0 adds some new elements and attributes, while others are
marked as deprecated.
> > To not break the ecosystem, this version is only available for the build
POM, while the consumer POM will still use version 4.0.0.
>
> However, it appears that version 4.1.0 breaks `mvn deploy` on Artifactory
servers.
The consumer POM is 4.0.0. The build POM does not have to be validated by
Artifactory imho. Or, they need to support 4.1.0 model.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
