Kedar Mhaswade wrote:
> Hi hg,
>
> This is a request with good intentions, so why would I disagree?
>
> But shouldn't build system *of a modular product* be designed such
> that a wrong commit in module "m" does not affect anyone other than those
> who depend on latest version of "m"?
>
> I understand we are not there yet, but that should be our goal.
Yes, that's our goal, but the goal can't achieved by build team alone.
Developers have to first modularize their components. Until then, we
should have a monolithic build system to avoid all the build problems we
are having today.
Thanks,
Sahoo
>
> Regards,
> Kedar
>
> Harsha Godugu wrote:
>> v3 Committers,
>>
>> I'm sure you must be very busy in your own little development world
>> and hence trying to push your code into v3 sources in a rush. Please
>> take some time to run the appropriate tests for your module before
>> committing the code into the trunk. Since maven local repo. is
>> always questionable, would you always build and run tests with a
>> fresh local (private) repo. This greatly helps in avoiding broken
>> builds and saves a lot of time for your peers who are also sweating
>> equally.
>>
>> thanks for reading so far,
>> -hg
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
>