Dinesh,
Will it make sense to add the update to the bootstrap target as well? What if
there are new dependencies between several modules that the developer builds or
a fix for the build.xml itself?
thanks,
-marina
Dinesh Patil wrote:
> Bill Shannon wrote:
>
>> Anissa Lam wrote:
>>
>>> If you are doing 'bootstrap-all', it should have worked. Have you
>>
>>
>>
>> It didn't. Want to debug it?
>>
>>> update glassfish/bootstrap directory itself BEFORE doing
>>> bootstrap-all.
>>> Remember, if you do 'cd glassfish/bootstrap; maven checkout
>>> bootstrap-all build configure-runtime', the bootstrap directory
>>> will NOT be updated, and thus you will still be building with the
>>> OLD version of staged jar.
>>
>>
>>
>> Here's what I do:
>>
>> cd glassfish/bootstrap
>> maven clean
>> rm -rf ../../publish/*
>> maven checkout bootstrap-all build
>>
>> If that's not what I'm supposed to be doing to get a clean build
>> every time, what *should* I be doing? Do I need to do a "cvs update"
>> as the second step? I would've thought "maven checkout" would do that.
>
>
> bootstrap-all updates bootstrap module also to update any binary
> dependencies. bootstrap doesn't update as its not required for this goal.
> thanks
> Dinesh
>
>> ---------------------------------------------------------------------
>> 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
>