Robert Scholte created MNG-7595:
-----------------------------------
Summary: [REGRESSION] $pom.-expressions in remote pom cause
warnings
Key: MNG-7595
URL: https://issues.apache.org/jira/browse/MNG-7595
Project: Maven
Issue Type: Bug
Affects Versions: 4.0.0-alpha-2
Reporter: Robert Scholte
When depending on
[wagon-http-1.0-beta-6|https://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-http/1.0-beta-6/wagon-http-1.0-beta-6.pom]
you'll get a warning like:
{noformat}
[WARNING] The POM for org.apache.maven.wagon:wagon-http:jar:1.0-beta-6 is
invalid, transitive dependencies (if any) will not be available: 1 problem was
encountered while building the effective model for
C:\Users\rober\.m2\repository\org\apache\maven\wagon\wagon-http\1.0-beta-6\wagon-http-1.0-beta-6.pom
[ERROR] 'dependencies.dependency.groupId' for
${pom.groupId}:wagon-http-shared:jar with value '${pom.groupId}' does not match
a valid coordinate id pattern. @ org.apache.maven.wagon:wagon-http:1.0-beta-6
{noformat}
Even though this is an old artifact, IMO we should not have such a warning for
remote poms, as they cannot be changed. So the question is: do we need to
reconsider the decision to only allow $project.-expressions for the build-pom?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
