[MNG-6912] File based profile activation results in absolute paths in OriginalModel

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.6.3
• Assignee: Unassigned
• Reporter: Arnoud Glimmerveen
• Created: 22/May/20 06:08
• Updated: 26/May/21 07:41
• Resolved: 26/May/21 07:41

Description

If a project has one or more profiles activated using file(s), the OriginalModel that a maven plugin can obtain from the MavenProject, holds the absolute path to these files, rather than the raw value from the pom.xml file.

This is caused by the DefaultModelBuilder using the 'rawModel' to determine the active profiles, which has the side-effect of interpolating the files to absolute paths.

Issue Links

• duplicates: MNG-6802 FileProfileActivator changes FileProfileActivator.exists which lets flattened resolveCiFriendliesOnly depending fail activating profile
• links to: GitHub Pull Request #348