Lloyd L Chambers wrote:
> Bobby,
>
> No, clobber does *not* remove glassfish_dependencies; if you do a
> 'maven bootstrap-all' after a 'clobber', you'll see that none of the
> binaries are downloaded again.
No this is not true, maven checks for the checksum, and if new binary is
available or version has changed, it downloads it automatically if
"offline" mode (maven -o) is not used.
thanks
Dinesh
> Yes, there are glitches in the build, and I empathize with your
> plight--I've been there myself. :)
>
> Lloyd
>
> On Feb 8, 2007, at 11:39 AM, Bobby Bissett - Javasoft wrote:
>
>> Small question about this part:
>>
>>> maven clobber
>>> rm -rf ../glassfish_dependencies
>>
>>
>> Doesn't the clobber do that second step?
>>
>> The troubling part is that, after my server got into a weird state,
>> doing a clean/clobber/checkout/etc did not restore it to a working
>> state. It makes me think there is some issue in the build process,
>> as it seems there should be no state left over after I run those
>> commands.
>>
>> Is there any known reason that doing each step separately is
>> different than doing them together? In other words, could it be a
>> problem that I do "maven -E checkout bootstrap-all build configure-
>> runtime" as one call rather than separate maven steps?
>>
>> After another "rm -rf *" I'll checkout and do each step separately
>> and see what that gets me.
>>
>> Thanks,
>> Bobby
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>