Details
-
Bug
-
Resolution: Answered
-
Low
-
None
-
5.2
-
None
Description
We use the "Maven Dependencies Processor" for automatic dependency resolution and it works fine, as long as all artifacts/pom files are locally available.
If we execute the Maven Dependencies Processor as first task on a bamboo agent which has a completely empty repository it is not able to download the required pom files.
Or is this behavior expected and the dependencies processor should always be executed last?
How to reproduce :
- create a plan with a maven project checkout
- add the maven dependencies processor
- wipe the repository on the agent and run the plan
- it fails
- execute any random maven task BEFORE the processor, e.g. "mvn compile" so that the repository is full
- run the maven dependencies processor again and it works