Resolution: Not A Problem
Affects Version/s: 1.0
Fix Version/s: None
Component/s: Standard Rules
The main benefit of profile activation is that a profile is activated by a property set outside of maven. It does not make any sense to active by a property if it is defined in the POM.
If I set the following in my properties section:
This would evaluate the property to "true" and pass the enforcer rule. It makes absolutely no sense. Properties should be evaluated the same way as in the profile activation. POM properties are always present, thus making the hole enforcer thing obsolete.
This issue is related to
|Field||Original Value||New Value|
|Resolution||Not A Bug [ 6 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Project Import||Sun Apr 05 10:06:27 UTC 2015 [ 1428228387238 ]|
|Workflow||jira [ 12721255 ]||Default workflow, editable Closed status [ 12761665 ]|
|Project Import||Sun Apr 05 23:50:18 UTC 2015 [ 1428277818417 ]|
|Workflow||jira [ 12958859 ]||Default workflow, editable Closed status [ 12995770 ]|