I'm hitting a weird edge use case with Maven curious why it's behaving
the way it does.
I'm defining a property in my parent project like so:
properties
some.property.version1.0.0.0/some.property.version
/properties
Now, in a module, I set a version of a dependency for a plugin like
You sir are good! I'd give 5 stars on this if I could. I did refactor the
parent module's artifactId and hadn't updated it in the module. I guess it
was referring to the older version still stored in the local repository.
Updating the parent artifactId did the trick. Thanks for the fast reply
this should not happen: there is some little mistake somewhere
I just created a little test project to confirm this should not display any
warning:
https://github.com/hboutemy/property-test
can you share such little project so we can see where is the mistake or
misunderstanding?
Regards,
Hi,
This makes me wonder if the right parent is used, so please double check
the groupId, artifactId and version.
If both parent and module are part of the same multi-module, be sure that
the relativePath is correct (defaults to ../pom.xml)
You could also use mvn
The Apache Maven team is pleased to announce the release of the Maven
Project Info Reports Plugin, version 2.8.
This module generates browsable HTML pages from Java source code.
http://maven.apache.org/plugins/maven-project-info-reports-plugin/
You should specify the version in your project's
