Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Auto Closed
-
2.8
-
None
-
None
Description
The dependency:unpack goal is often used to manage various files like (test) resources throughout a multimodule project.
For example, to create a working directory, several artifacts may be unpacked into a workdir/.
To configure this it is convenient to set up the goal in the root module.
This works fine, except two things:
1) The root module itself would fail (as the deps don't exist yet)
2) The modules with the resources depend on themselves, i.e. creating a cyclic dependency.
It would be very convenient if this was handled somehow.
My suggestion to add a ignoreIfNotExists flag, which would just write an INFO log message and continue in case that the dependency doesn't exist yet.
That way, users wouldn't have to explicitely enable the execution of the unpack goal for every single direct submodule.
Thanks for considering.