Browse Source

Move Enforcer Plugin to 'compile' phase in 'lib'

There is a strange effect in Maven builds: Depending on which profiles
are active when building the project - even seemingly unrelated ones
like 'create-docs' or 'clean-libs' - the execution order of plugins in
the 'process-resources' phase can vary. Specifically, Build Helper vs.
Enforcer in module 'lib', which both were in the same phase, can
sometimes be executed in lexical order, which I expected, or the other
way around, which makes the build fail if the existence of the marker
file is checked by Enforcer before Build Helper even had a chance to
create it. Probably, this is because Build Helper is defined inside a
profile and Enforcer outside of any.

Therefore, the safest way to ensure correct ordering of the two is to
place Enforcer in a later phase, in this case 'compile'.

Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
tags/V1_9_7_M2
Alexander Kriegisch 3 years ago
parent
commit
a57efcafcf
1 changed files with 1 additions and 1 deletions
  1. 1
    1
      lib/pom.xml

+ 1
- 1
lib/pom.xml View File

@@ -708,7 +708,7 @@
<executions>
<execution>
<id>enforce-libraries-exist</id>
<phase>process-resources</phase>
<phase>compile</phase>
<goals>
<goal>enforce</goal>
</goals>

Loading…
Cancel
Save