diff options
| author | Alexander Kriegisch <Alexander@Kriegisch.name> | 2021-05-07 05:23:14 +0700 |
|---|---|---|
| committer | Alexander Kriegisch <Alexander@Kriegisch.name> | 2021-05-07 05:23:14 +0700 |
| commit | a57efcafcfbab31635048cac9e02bbc55276573c (patch) | |
| tree | 49e7cecf8930dbbef992d1ea3dff896383d7ffb0 /lib | |
| parent | 3134e569917ce3f8c8054fd1b4c05e9bd981a365 (diff) | |
| download | aspectj-a57efcafcfbab31635048cac9e02bbc55276573c.tar.gz aspectj-a57efcafcfbab31635048cac9e02bbc55276573c.zip | |
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>
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/pom.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/pom.xml b/lib/pom.xml index 78e5d8d47..e2a186b38 100644 --- a/lib/pom.xml +++ b/lib/pom.xml @@ -708,7 +708,7 @@ <executions> <execution> <id>enforce-libraries-exist</id> - <phase>process-resources</phase> + <phase>compile</phase> <goals> <goal>enforce</goal> </goals> |