[juliemyeclipse]

I just upgraded MyEclipse from 8.0 to 8.6 , and getting :
‘version’ contains an expression but should be a constant. .

We have two modules , Module #2 depends on #1, both #1 and #2 are referencing ${version} in the parent pom. All have been working before this push.

The problem we have is the same as : http://jira.codehaus.org/browse/MNG-4715. It sounds like Maven 3.x caused the problem, that makes sense to me because my own maven is 2.0.10 and build successfully via command line.

Here is the Maven version i found in ME 8.6 : Maven4myEclipse->Installations -> Maven -> Embedded(3.0-SNAPSHOT/0.10.0.me201003101716).

I’m presuming Maven version is 3.0.x on ME 8.6.

I’ve tired to add my own Maven 2.0.10 as external , but it doesn’t take the effect – the same error. Any workaround? thx.

[juliemyeclipse]

Just found out this is a Known Incompatibilities with Maven 2.
https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
“For the sake of reproducible builds, Maven 3.x no longer supports usage of these metaversions in the POM. As a result, users will need to replace occurrences of these metaversions with a concrete version.”

We have to think about the upgrade because of Incompatibilities .

[juliemyeclipse]

I switched to Eclipse 3.6.1 , build passed with the same warnings . – ‘version’ contains an expression but should be a constant.

However, MyEclipse failed build ( the build classpath is not resolved by Maven dependencies for Module #2) .

Eclipse gave us time to think/fix the incompatibilities, I like it better.

[Author]

Posts