You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by "Foreman, Alex (IT)" <Al...@morganstanley.com> on 2007/05/23 14:36:00 UTC

Using a HDD as the local repository

I have a file system which already has many of the artifacts inside it.

Eg:
/var/tmp/repo/[organisazion]/[module]/[revision]/[artifact].[ext]

I currently have a resolver:
<ivysettings>
        <conf defaultResolver="msdist" />
        <resolvers>
                    <filesystem name="localdisk">
                            <artifact
pattern="/var/tmp/repo/[organisazion]/[module]/[revision]/common/lib/[ar
tifact].[ext]" />
                    </filesystem>
        </resolvers>
</ivysettings>

The problem is that when I have a project that uses for instance 'apache
commons-lang 2.1' It resolves the file perfectly in my FileSystem
resolver and copies it to my local ivy repo ~/.ivy/cache...  I do not
want to copy the files.  I want it to use the files where they are and
just point to them.

How is this possible.

I have RTFM and tried hacking around but nothing so far has worked out.

Many thanks,

Alex Foreman
--------------------------------------------------------

NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.

Re: Using a HDD as the local repository

Posted by Jing Xue <ji...@digizenstudio.com>.
Quoting "Foreman, Alex \(IT\)" <Al...@morganstanley.com>:
[snip]
> The problem is that when I have a project that uses for instance 'apache
> commons-lang 2.1' It resolves the file perfectly in my FileSystem
> resolver and copies it to my local ivy repo ~/.ivy/cache...  I do not
> want to copy the files.  I want it to use the files where they are and
> just point to them.
>
> How is this possible.
[snip]

In my relatively simple setup, I have the CacheResolver as the first  
in the chain, and don't keep a separate file system repo that mirrors  
the public ones. That saves the copying. For some reason the  
CacheResolver isn't documented though.

HTH
-- 
Jing Xue



Re: Using a HDD as the local repository

Posted by Xavier Hanin <xa...@gmail.com>.
On 5/23/07, Foreman, Alex (IT) <Al...@morganstanley.com> wrote:
>
> I have a file system which already has many of the artifacts inside it.
>
> Eg:
> /var/tmp/repo/[organisazion]/[module]/[revision]/[artifact].[ext]
>
> I currently have a resolver:
> <ivysettings>
>         <conf defaultResolver="msdist" />
>         <resolvers>
>                     <filesystem name="localdisk">
>                             <artifact
> pattern="/var/tmp/repo/[organisazion]/[module]/[revision]/common/lib/[ar
> tifact].[ext]" />
>                     </filesystem>
>         </resolvers>
> </ivysettings>
>
> The problem is that when I have a project that uses for instance 'apache
> commons-lang 2.1' It resolves the file perfectly in my FileSystem
> resolver and copies it to my local ivy repo ~/.ivy/cache...  I do not
> want to copy the files.  I want it to use the files where they are and
> just point to them.
>
> How is this possible.


Historically Ivy heavily relies on its cache, but this is something that we
have planned to review for next version, to make Ivy cache more flexible
(check and vote for IVY-399).

With current version, what is possible is to avoid the copy of artifacts,
but you will still have ivy files copied in your cache. To do you have to
use the useOrigin='true' attribute on your resolve and post resolve tasks
(like cachepath or cachefileset, if you really want to avoid any copy).

HTH,

Xavier

I have RTFM and tried hacking around but nothing so far has worked out.
>
> Many thanks,
>
> Alex Foreman
> --------------------------------------------------------
>
> NOTICE: If received in error, please destroy and notify sender. Sender
> does not intend to waive confidentiality or privilege. Use of this email is
> prohibited when received in error.
>



-- 
Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/