[
https://issues.apache.org/jira/browse/IVY-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702354#action_12702354
]
Brian Matzon commented on IVY-1021:
-----------------------------------
how does all of this go down with ivy:install?
[ivy:install] :: installing apache#log4j#trunk;1.2.15 ::
[ivy:install] :: resolving dependencies ::
[ivy:install] found apache#log4j#trunk;1.2.15 in external
[ivy:install] :: downloading artifacts to cache ::
[ivy:install] downloading
http://repo1.maven.org/maven2/log4j/log4j/1.2.15/log4j-1.2.15.jar ...
[ivy:install] ..................
[ivy:install] . (382kB)
[ivy:install] .. (0kB)
[ivy:install] [SUCCESSFUL ] apache#log4j#trunk;1.2.15!log4j.jar (2187ms)
[ivy:install] downloading
http://repo1.maven.org/maven2/log4j/log4j/1.2.15/log4j-1.2.15-sources.jar ...
[ivy:install] ................ (380kB)
[ivy:install] .. (0kB)
[ivy:install] [SUCCESSFUL ] apache#log4j#trunk;1.2.15!log4j.jar(source)
(1484ms)
[ivy:install] :: installing in local ::
[ivy:install] published log4j to
ivy/local/apache/log4j/trunk/log4j-1.2.15.jar
BUILD FAILED
build.xml:68: impossible to install apache#log4j#trunk;1.2.15:
java.io.IOException: file copy not done from
ivy\cache\apache\log4j\trunk\sources\log4j-1.2.15-sources.jar to
ivy\local\apache\log4j\trunk\log4j-1.2.15.jar: destination already exists and
overwrite is false
highly annoying
> add flag or exclude option to ivy:install to avoid source or javadoc packages
> -----------------------------------------------------------------------------
>
> Key: IVY-1021
> URL: https://issues.apache.org/jira/browse/IVY-1021
> Project: Ivy
> Issue Type: Improvement
> Components: Ant
> Affects Versions: 2.0
> Environment: ivy > beta 2 is affected
> Reporter: Brian Matzon
> Priority: Critical
>
> Changes comitted in IVY-325 results in ivy:install to install source and
> javadoc files. This is all fine, except if people dont use [type] in their
> pattern it will fail because its trying to download multiple files with the
> same name (but different type).
> This is a change in behavior since 2.0 beta2.
> it would be nice to either add a flag to avoid this behavior or add and
> exclude/include section, like the dependencies.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
