You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Brian Matzon (JIRA)" <ji...@apache.org> on 2009/01/28 10:30:59 UTC
[jira] Created: (IVY-1021) add flag or exclude option to
ivy:install to avoid source or javadoc packages
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.
[jira] Commented: (IVY-1021) add flag or exclude option to
ivy:install to avoid source or javadoc packages
Posted by "Alex Taggart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700988#action_12700988 ]
Alex Taggart commented on IVY-1021:
-----------------------------------
Thanks Maarten! Between the presence of the JIRA entry, and the lack of response to a query to the ivy-users mailing list (http://www.nabble.com/How-to-exclude-source-and-javadoc-download-td20808519.html#a21379869), I had thought this an unsolved problem.
> 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.
[jira] Commented: (IVY-1021) add flag or exclude option to
ivy:install to avoid source or javadoc packages
Posted by "Thiam Teck (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751379#action_12751379 ]
Thiam Teck commented on IVY-1021:
---------------------------------
Hi Maarten, I am still a beginner in using Ivy.
After some google, the default attifact pattern I found is "[module]/[type]s/[artifact]-[revision].[ext]"
Do you mind to share with us on how to remove the [classifier] token from the artifact pattern of the ibiblio resolver?
> 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.
[jira] Commented: (IVY-1021) add flag or exclude option to
ivy:install to avoid source or javadoc packages
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700971#action_12700971 ]
Maarten Coene commented on IVY-1021:
------------------------------------
Maybe a workaround for the ivy:install task problem could be to override the default maven2 patterns Ivy uses and don't specify the [classifier] token inside them. This way, Ivy won't find the sources/javadoc artifacts and will not try to download/install them...
Maarten
> 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.
[jira] Commented: (IVY-1021) add flag or exclude option to
ivy:install to avoid source or javadoc packages
Posted by "Alex Taggart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700912#action_12700912 ]
Alex Taggart commented on IVY-1021:
-----------------------------------
This one issue is keeping us on Ivy 2.0.0-beta2 (or more accurately, the breaking change from IVY-325).
It is a huge waste of time updating many hundreds of <dependency/> nodes spread across many dozens of ivy.xml files to only pull the jars, or waste inordinate amounts of bandwidth (and thus time) pulling down entirely useless javadoc and source JARs/ZIPs into my applications' lib.
> 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.
[jira] Commented: (IVY-1021) add flag or exclude option to
ivy:install to avoid source or javadoc packages
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700964#action_12700964 ]
Maarten Coene commented on IVY-1021:
------------------------------------
You can easily avoid these sources/javadocs from being downloaded by restricting the type to "jar" when calling the ivy:resolve task...
> 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.
[jira] Commented: (IVY-1021) add flag or exclude option to
ivy:install to avoid source or javadoc packages
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702363#action_12702363 ]
Maarten Coene commented on IVY-1021:
------------------------------------
I think you could workaround it by either:
- add the [classifier] token to the artifact patterns of your local resolver; or
- remove the [classifier] token from the artifact pattern of the ibiblio resolver
> 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.
[jira] Resolved: (IVY-1021) add flag or exclude option to
ivy:install to avoid source or javadoc packages
Posted by "Gilles Scokart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gilles Scokart resolved IVY-1021.
---------------------------------
Resolution: Fixed
Fix Version/s: trunk
Assignee: Gilles Scokart
There is a type attribute to the install task since a long time, but it was not documented (nor tested).
The documentation is now updated on the trunk.
> 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
> Assignee: Gilles Scokart
> Priority: Critical
> Fix For: trunk
>
>
> 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.
[jira] Commented: (IVY-1021) add flag or exclude option to
ivy:install to avoid source or javadoc packages
Posted by "Brian Matzon (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (IVY-1021) add flag or exclude option to
ivy:install to avoid source or javadoc packages
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene updated IVY-1021:
-------------------------------
Fix Version/s: 2.2.0-RC1
(was: trunk)
> 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
> Assignee: Gilles Scokart
> Priority: Critical
> Fix For: 2.2.0-RC1
>
>
> 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.