[
https://issues.apache.org/jira/browse/IVY-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462274
]
Eric Crahen commented on IVY-209:
---------------------------------
I agree with Iain.
I have use cases right now where structure is quite important:
I compile native c++ components with headers that I do compile against
I store artifacts like configuration which I do not compile against but will
use in testing / at runtime.
I store artifacts like beanshell/groovy scripts which I do not compile
against but will use in testing / at runtime.
I store artifacts like webapp deployment descriptors which I do not compile
against but will use at runtime.
I store artifacts as they are distributed, Jetty 6.1.*, for example,
provides lib and lib/ext artifacts. Structure not needed to build with
correctly, but nice to preserve.
I store artifacts as they are distributed, proprietary j2ee containers, for
example, provides lib and lib/secure artifacts. Structure is needed to
correctly initialize and acceptance tests with this code. The reason being that
the java security is setup to allow special permissions to jars in the secure
directory.
I store artifacts as they are distributed, proprietary jars, for example,
provides lib and lib/plugin artifacts. Structure actually is needed in this
case due to the nature of the plugin mechanism.
> Enable file directory as artifact.
> ----------------------------------
>
> Key: IVY-209
> URL: https://issues.apache.org/jira/browse/IVY-209
> Project: Ivy
> Issue Type: New Feature
> Components: Core
> Affects Versions: 1.3.1
> Reporter: HB
> Assigned To: Xavier Hanin
>
> For JEE delivery, we need to be able to deliver directory and its content as
> regular artifact.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
