[MRM-952] Patch for several issues while processing poms (effective model, expressions resolving, storing to database)

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.2
• Fix Version/s: 1.2-M1
• Component/s: repository interface, repository scanning
• Flags: Patch
• Assignee: Maria Odea B. Ching
• Reporter: Michal Stochmialek
• Created: 18/Sep/08 09:25
• Updated: 05/Apr/15 14:54
• Resolved: 10/Oct/08 22:59

Description

I'm submitting a bigger patch for serveral issues that drived my crazy after installation of archiva in our company.
The patch is for 1.1.1 and 1.1.2 releases.

The patch:

• fixes problems with expression resolving (${pom.version}) in dependencies,
• adds support for parent.{groupId, artifactId, version) properties,
• fixes issues with jdo detachCopy called from ProjectModelToDatabaseListener while creating effective pom,
• fixes inconsistency in key format used in effective model cache,
• add merging parentProject and properties while creating effective pom,
• ArchivaProjectModel.setOrgin("filesystem") was moved to readers (where IMO should be),
• adds few new test cases.

I will be very happy if you apply the patch on the code base. It will save me a bit of work
with merging my changes with new releases in the future.

Issue Links

• is duplicated by: MRM-686 'Unable to find project model' when artifactId contains property placeholders e.g. ${project.parent.artifactId}
• is related to: MRM-615 When scanning, Archiva doesn't resolve properties/variables of POMs in managed repositories
• is related to: MRM-686 'Unable to find project model' when artifactId contains property placeholders e.g. ${project.parent.artifactId}
• is related to: MRM-844 "Unable to create ArchivaArtifact with empty version" in dependency tree.
• is related to: MRM-620 pom.xml that inherit version from parent show up in reports as "has an invalid project model"