[MNG-6802] FileProfileActivator changes FileProfileActivator.exists which lets flattened resolveCiFriendliesOnly depending fail activating profile

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.2, 3.6.2
• Fix Version/s: 3.8.5, 4.0.0-alpha-2, 4.0.0
• Component/s: Profiles
• Assignee: Michael Osipov
• Reporter: Stefan Cordes
• Created: 13/Nov/19 10:42
• Updated: 20/Oct/22 08:11
• Resolved: 06/Jan/22 18:07

Description

In my pom.xml I have

 

...
 <profile> 
    <profile> 
       <id>cas-mule4-app</id> 
    <activation> 
       <file> 
          <exists>mule-artifact.json</exists> 
       </file>
    </activation> 
...

 

which worked fine.

After switching to ci-friendly pom.xml with revision and flatten the published .flattened-pom.xml contains absolute path:

 

    <profile>
      <id>cas-mule4-app</id>
      <activation>
        <file>
          <exists>D:\jenkins\workspace\mulestac-multibranch_mule4-DWHLMU7ZMPDNCYK6LVMSYLB6GODEIQS7CUNRQQVSISU47ME72PRQ\mule-artifact.json</exists>
        </file>
      </activation>

 

(which is the temporary path of our jenkins container)

and so other projects using that pom.xml as parent will fail to activate the profile.

 

This came in with MNG-1775 or a related issue via adding

        // replace activation value with interpolated value
        if ( missing )
        {
            file.setMissing( path );
        }
        else
        {
            file.setExists( path );
        }

in org.apache.maven.model.profile.activation.FileProfileActivator.

 

Issue Links

• is caused by: MNG-5612 effective pom should not contain file-based profile activation fully interpolated but with limited interpolation like seen during profile activation
• is duplicated by: MNG-6912 File based profile activation results in absolute paths in OriginalModel
• links to: GitHub Pull Request #347
• links to: GitHub Pull Request #649