Details
-
Bug
-
Status: Reopened
-
Major
-
Resolution: Unresolved
-
None
-
None
-
Windows, Solaris
Maven version 2.0.4
Description
Variables are not replaced into installed pom file.
Here is a sample pom file
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.xxx.root</groupId> <artifactId>root</artifactId> <packaging>pom</packaging> <version>${prop.version}</version> <name>My Project</name> ... <properties> <prop.version>3.0.20</prop.version> </properties> </project>
The installed pom is into ${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
Attachments
Attachments
Issue Links
- depends upon
-
MINSTALL-50 provide property filtering on .pom files placed in local repo
- Closed
- duplicates
-
MNG-4369 Maven does not expand expressions while installing artifacts locally
- Closed
- is related to
-
MNG-3057 properties not expanded in generated POMs when building A/B/C nested projects
- Closed
-
MNG-624 automatic parent versioning
- Closed
-
MNG-3267 replacing variables in version, groupId or artifactId when POM is installed/deployed
- Closed
- relates to
-
MNG-4223 Resolve expressions in POM artifact coordinates
- Closed
-
MNG-4161 possibility to omit version in dependency of same project (and fill in on install/deploy)
- Closed