Re: Disconnected Development

[Geoff Reedy <ge...@sandia.gov>]

Eric Crahen wrote:
> It would raise the burden on the user a bit, they'd have to add that extra
> url.
> Not a huge deal, but each little obstacle that can be removed is a great
> thing.

You can use the special property 'svn:externals' to share common files 
between projects. Documentation on 'svn:externals' is here:

http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html

I use this to include all of the files necessary for my ivy 
configuration: jars, ant build scripts, and the ivy configuration file. 
  I only need to update these in one place when necessary, and every 
project automatically pulls in the updates whenever they next do an 'svn 
update'.

Using this method would also allow you to dispose of the complicated 
machinery to download the ivy configuration file.

-- Geoff Reedy

Re: Disconnected Development

[Eric Crahen <er...@gmail.com>]

Cool. That will be helpful for svn repositories. I have some that aren't
based in svn or where that feature of svn is not available for me. It still
seems like a useful think for ivy.

On 1/3/07, Xavier Hanin <xa...@gmail.com> wrote:
>
> On 1/3/07, Geoff Reedy <ge...@sandia.gov> wrote:
> >
> > Eric Crahen wrote:
> > > It would raise the burden on the user a bit, they'd have to add that
> > extra
> > > url.
> > > Not a huge deal, but each little obstacle that can be removed is a
> great
> > > thing.
> >
> > You can use the special property 'svn:externals' to share common files
> > between projects. Documentation on 'svn:externals' is here:
> >
> > http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html
>
>
> Thanks for the tip Geoff, very useful and clean!
>
> Xavier
>
> I use this to include all of the files necessary for my ivy
> > configuration: jars, ant build scripts, and the ivy configuration file.
> >   I only need to update these in one place when necessary, and every
> > project automatically pulls in the updates whenever they next do an 'svn
> > update'.
> >
> > Using this method would also allow you to dispose of the complicated
> > machinery to download the ivy configuration file.
> >
> > -- Geoff Reedy
> >
> >
> >
>
>


-- 

- Eric

Re: Disconnected Development

[Xavier Hanin <xa...@gmail.com>]

On 1/3/07, Geoff Reedy <ge...@sandia.gov> wrote:
>
> Eric Crahen wrote:
> > It would raise the burden on the user a bit, they'd have to add that
> extra
> > url.
> > Not a huge deal, but each little obstacle that can be removed is a great
> > thing.
>
> You can use the special property 'svn:externals' to share common files
> between projects. Documentation on 'svn:externals' is here:
>
> http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html


Thanks for the tip Geoff, very useful and clean!

Xavier

I use this to include all of the files necessary for my ivy
> configuration: jars, ant build scripts, and the ivy configuration file.
>   I only need to update these in one place when necessary, and every
> project automatically pulls in the updates whenever they next do an 'svn
> update'.
>
> Using this method would also allow you to dispose of the complicated
> machinery to download the ivy configuration file.
>
> -- Geoff Reedy
>
>
>