ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <j...@apache.org>
Subject [jira] Commented: (IVYDE-105) Retrieve after resolve feature does not clean target directory first
Date Wed, 23 Jul 2008 16:16:38 GMT

    [ https://issues.apache.org/jira/browse/IVYDE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616141#action_12616141
] 

Nicolas Lalevée commented on IVYDE-105:
---------------------------------------

bq. I do not know if the same component is used in ant and IvyDE for this task but i have
some artifact of type 'resource' (not 'jar' or 'source') is retrieving in my WEB-INF/lib,
not just 'jar' type artifact.

Today it is only possible to retrieve the same artifact that are added to IvyDE's classpath
conatiner.
You could probably try to have theses "resource" contributed to the classpath. In the "Advanced
Tab", in the field "Accepted types", put "jar,resource". But maybe Eclipse could be unhappy
with it, I don't know. It is doesn't work you should open a jira issue yes.

> Retrieve after resolve feature does not clean target directory first
> --------------------------------------------------------------------
>
>                 Key: IVYDE-105
>                 URL: https://issues.apache.org/jira/browse/IVYDE-105
>             Project: IvyDE
>          Issue Type: New Feature
>    Affects Versions: 2.0.0.alpha1
>         Environment: Eclipse 3.4
>            Reporter: Sébastien Launay
>            Assignee: Nicolas Lalevée
>             Fix For: 2.0
>
>
> I use the 'Retrieve after resolve' feature in order to populate the directory web/WEB-INF/lib
> in my project using pattern 'web/WEB-INF/lib/[artifact]-[revision].[ext]'.
> This directory is used by the servlet engine in order to load librairies, but the directory
can
> contain multiple artifact of the same module (mylib-1.0.jar and mylib-1.1.jar) or old
dependencies
> if you update your ivy.xml and then resolve again.
> I know that removing files based on a pattern is dangerous and not trivial.
> Removing files below the longest path without '[' may be a good alternative
> (with an optional check box "Clean directory").
> Another solution is to keep the previous retrieved artifacts and removing them if still
> present just before the new retrieve.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message