It's not an actual problem for us since we make sure that only leaf
modules have the suffix.
It can result in problems if parent modules have the suffix, since
children _may_ no longer be able to resolve the path to the parent since
the property value is usually defined in the parent.
On a related note, children overriding the scala.version.property would
probably also result in a few weird issues.
In other words, it makes sense for maven to log these warnings, but they
are not relevant for us.
On 04/03/2020 10:38, Niels Basjes wrote:
> Hi,
>
> When building Flink I see a LOT of messages from maven that are similar to
> this:
>
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.flink:flink-runtime_2.11:jar:1.11-SNAPSHOT
> [WARNING] 'artifactId' contains an expression but should be a constant. @
> org.apache.flink:flink-runtime_${scala.binary.version}:1.11-SNAPSHOT,
> /home/nbasjes/workspace/Apache/flink/flink-runtime/pom.xml, line 32, column
> 14
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
>
> Apparently using the property ${scala.binary.version} in the artifactId is
> not likes by Maven.
> Right now it just produces a lot of noise during the build.
> How big of a problem is this really?
>
Locked
