Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
1.0
-
None
-
None
Description
We frequently use property placeholders in our poms to have generic POM templates,
e.g.
<project>
<parent>
<groupId>be.javaserver.tst</groupId>
<artifactId>eCommonOrderHandling</artifactId>
<version>2.8-SNAPSHOT</version>
</parent>
<artifactId>${project.parent.artifactId}-module-sTst8128</artifactId>
</project>
283836 [SocketListener0-0] WARN org.apache.maven.archiva.consumers.DatabaseUnprocessedArtifactConsumer:update-db-project - File eCommonOrderHandling-module-sTst8128-1.5-20080131.102935-1.pom has an invalid project model [groupId:be.javaserver.tst|artifactId:${project.parent.artifactId}-module-sTst8128|version:1.5
-20080131.102935-1|packaging:jar]: The model artifactId [${project.parent.artifactId}-module-sTst8128] does not match the artifactId portion of the filename:
eCommonOrderHandling-module-sTst8128
284107 [SocketListener0-0] WARN org.apache.maven.archiva.consumers.DatabaseUnprocessedArtifactConsumer:update-db-project - Invalid or corrupt pom.
Project model not added to database - be.javaserver.tst:${project.parent.artifactId}-module-sTst8128:1.5-20080131.102935-1
Attachments
Issue Links
- duplicates
-
MRM-816 Resolution parameters in URL are not expanded
- Closed
-
MRM-952 Patch for several issues while processing poms (effective model, expressions resolving, storing to database)
- Closed
- is related to
-
MRM-816 Resolution parameters in URL are not expanded
- Closed
-
MRM-620 pom.xml that inherit version from parent show up in reports as "has an invalid project model"
- Closed
- relates to
-
MRM-615 When scanning, Archiva doesn't resolve properties/variables of POMs in managed repositories
- Closed
-
MRM-952 Patch for several issues while processing poms (effective model, expressions resolving, storing to database)
- Closed