[BUILD-169] Update maven-enforcer-plugin to 1.3.1 Created: 21/Oct/14 Updated: 13/Apr/17 Resolved: 22/Oct/14 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | POMs 30 |
| Type: | Task | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Description |
|
For now, we'll probably just add <requirePluginVersions>, which will help fixing |
| Comments |
| Comment by Magnolia International [ 21/Oct/14 ] |
|
The <requirePluginVersions> rule seems to work on-and-off. When a project declares a "new" plugin without a version, the build bails; but when a project uses a plugin indirectly (declared in parent pom, but not used when building the parent pom, such as build-helper-plugin), then we get a mere warning. |
| Comment by Magnolia International [ 21/Oct/14 ] |
|
In fact, when doing mvn -P continuous-integration clean, the rule also seems to be ignored. |
| Comment by Magnolia International [ 22/Oct/14 ] |
|
Figured it out:
|