[
https://issues.apache.org/jira/browse/MNG-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-6802:
-------------------------------
Affects Version/s: 3.2.2
3.6.2
> FileProfileActivator changes FileProfileActivator.exists which lets flattened
> resolveCiFriendliesOnly depending fail activating profile
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-6802
> URL: https://issues.apache.org/jira/browse/MNG-6802
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.2.2, 3.6.2
> Reporter: Stefan Cordes
> Priority: Major
>
> In my pom.xml I have
>
> {noformat}
> ...
> <profile>
> <profile>
> <id>cas-mule4-app</id>
> <activation>
> <file>
> <exists>mule-artifact.json</exists>
> </file>
> </activation>
> ...{noformat}
>
> which worked fine.
> After switching to ci-friendly pom.xml with revision and flatten the
> published .flattened-pom.xml contains absolute path:
>
> {noformat}
> <profile>
> <id>cas-mule4-app</id>
> <activation>
> <file>
>
> <exists>D:\jenkins\workspace\mulestac-multibranch_mule4-DWHLMU7ZMPDNCYK6LVMSYLB6GODEIQS7CUNRQQVSISU47ME72PRQ\mule-artifact.json</exists>
> </file>
> </activation>
> {noformat}
>
> (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
> {noformat}
> // replace activation value with interpolated value
> if ( missing )
> {
> file.setMissing( path );
> }
> else
> {
> file.setExists( path );
> }
> {noformat}
> in org.apache.maven.model.profile.activation.FileProfileActivator.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
