[
https://jira.codehaus.org/browse/MDEP-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondrej Zizka updated MDEP-426:
------------------------------
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.
was:
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 `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.
> Add `ignoreIfNotExists` to dependency:unpack
> --------------------------------------------
>
> Key: MDEP-426
> URL: https://jira.codehaus.org/browse/MDEP-426
> Project: Maven 2.x Dependency Plugin
> Issue Type: New Feature
> Components: unpack
> Affects Versions: 2.8
> Reporter: Ondrej Zizka
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
