[MNG-7051] Optionally skip non-existing profiles

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Implemented
• Fix Version/s: 4.0.0-alpha-2, 4.0.0
• Component/s: Profiles
• Assignee: Martin Kanters
• Reporter: Maarten Mulders
• Created: 09/Dec/20 09:19
• Updated: 20/Oct/22 08:11
• Resolved: 02/Feb/21 07:26

Description

For Maven 4, the behaviour of the -P command line option will change:

• -P apache-release will activate the apache-release profile. If such a profile cannot be found, the build will break.
• -P ?apache-release will activate the apache-release profile. If such a profile cannot be found, the build will continue but log a warning.

Note that this breaks the current behaviour of Maven 3 in two ways:

1. -P apache-release will currently log a warning and not break the build. That behaviour can be restored by adding the ?.
2. A profile that has an identifier that not valid (i.e., contains anything else than a - z, A to Z, 0 - 9, -, _ or .) will break the build.

Issue Links

• blocks: MNG-7029 Remove super POM "release-profile" release profile
• causes: MNG-7107 Relax recently introduced profile id validation
• causes: MNG-7052 Do not allow symbols as first character of identifiers in the POM
• is related to: MNG-7011 consistent profile/module exclusion
• is related to: MNG-6511 Option -pl ! foo should not fail if foo does not exist
• is related to: MNG-6862 Wrong command line analysis for joined profile activation
• relates to: MNG-7052 Do not allow symbols as first character of identifiers in the POM
• supercedes: MNG-7211 [WARNING] The requested profile "ABCDEF" could not be activated because it does not exist.
• links to: GitHub Pull Request #87
• links to: GitHub Pull Request #102
• links to: GitHub Pull Request #225
• links to: GitHub Pull Request #429
• links to: GitHub Pull Request #452
• links to: GitHub Pull Request #453