>Do you have aardvark set up as a project in eclipse or trying to build aardvark from within eclipse?
I was running this all outside of Eclipse and experienced this issue.
Thanks for the advice though.
> Sounds like it's an Ivy dependencies issue to me: I've had resolving dependencies take a looooooooong time.
That was the behavior I experienced, so I did assume it was dead in
the water - I left it going for about 20 minutes before killing it.
> You don't need a profiler necessarily. I once tried looking into the long
> resolution time by running vark with the "-v" switch and found that Ivy
> attempts and misses with a crapload of invalid URLs based on the resolver
> chain.
I'll run it again with -v to see what's going on.
> It's the front end I object to: I'd prefer something like ruby gems or apt-get that lets you search and install packages without scrounging around > on the internets looking for the right incantation to stick in an XML file.
Yea they have that down pat. It's one thing that I feel makes it alot
easier for a developer to get interested and involved. Setting up a
verbose xml file to handle things can be cumbersome to getting setup
quickly. You want to play around in a repl or a simple editor, and
easily grab additional functionality through a nice package manager
(Ivy is pretty nice, but friendly to setup it is not).
On Apr 27, 2:10 pm,
bchan...@gmail.com wrote:
Once you have most artifacts in your Ivy cache, however, things tend
> to fly by pretty quickly.
>
> OTOH, I may or may not have tried nuking my Ivy cache, and failed to
> observe the slow resolution time again. So that was the end of that at the
> time. :(
>
> If you find that the resolution is taking inordinately long, such as 20
> minutes, try -v and it may shed some light, and I'd love to collect your
> findings.
>
> On Apr 27, 2011 10:32am, Gus Prevas <
kpre...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Ivy does take a long time to resolve dependencies the first time, but
> > maybe we should slap a profiler on there and see why before we reinvent
> > any more wheels.
> > On Wed, Apr 27, 2011 at 1:21 PM, Carson Gross
carsongr...@gmail.com>
> > wrote:
> > Sounds like it's an Ivy dependencies issue to me: I've had resolving
> > dependencies take a looooooooong time.
> > Anyone want to work on packrat (a package manager for gosu)?
> > Cheers,
> > Carson
> > On Apr 27, 2011, at 9:48 AM, Chris Gow wrote:
> > JP:
> > Do you have aardvark set up as a project in eclipse or trying to build
> > aardvark from within eclipse? I think I had the same problem yesterday as
> > well. I originally created an eclipse project for aardvark (a while back)
> > and did nothing with it for a while then when Brian pushed his changes
> > yesterday I pulled them in (using the git eclipse plugin). I tried to
> > build from outside of eclipse and after 20 minutes of downloading stuff I
> > killed the process (I had actually forgotten about it). I removed the
> > project and pulled Brian's changes again, this time using the command
> > line version of git and did a build again. This time it worked. I know
> > its a shot in the dark, but I thought I would mention it.
> > hth
> > Chris