Yeah, i have no problem adding a repo to pull the -SNAPSHOT artifacts
down if they're online somewhere. I think most people will run these
after creating a local build but I can see where some might want to run
them against, say, a nightly. At this point it's largely academic
either way since I've yet to procure permission to migrate the tests off
of ant and on to maven. I have a script that does most of the work but
there's still a fair bit of grunt work to do to churn through all of the
tests.
On 6/21/11 6:04 PM, Bobby Bissett wrote:
> On 6/21/11 5:38 PM, Justin Lee wrote:
>> Well, when a developer builds a GlassFish distro to test, all the
>> necessary artifacts will be in ~/.m2 already.
>
> Except in my case. :)
>
> Since the tests reference the 3.1 snapshot, and I only have 3.1.1 and
> 3.2 bits in my local repo, I ran into the trouble. I agree that a
> developer probably will have the correct bits present (if we change
> the tests to reference 3.1.1/3.2), but I don't see the harm in adding
> the repository element to grab it if missing.
>
> After all, it's one of my hobbies to go to coffee shops, clean out my
> repo, and build glassfish to hog the wifi network. (Am kidding.)
>
> Cheers,
> Bobby
>