Re: [eclipse-dev] Planning Meeting Post-Notes - 2 May 2012

[Daniel Megert <daniel_megert@xxxxxxxxxx>]

> We want the
poms to be committed.  One of the advantages to being based on Maven/Tycho
is that developers can run the build (or a portion of it) on their own
box before making a commit.  Much better than 
> commit-and-pray.

This might work for smaller things, but the SDK build
is quite big and takes long even without running any tests. This will give
you a loooong time to pray ;-).

Dani


eclipse-dev-bounces@xxxxxxxxxxx wrote on 03.05.2012
15:45:01:

> From:
> 
> Brian de Alwis <briandealwis@xxxxxxxxx>
> 
> To:
> 
> "General development mailing list of the Eclipse project."
<eclipse-dev@xxxxxxxxxxx>, 
> 
> Date:
> 
> 03.05.2012 15:45
> 
> Subject:
> 
> Re: [eclipse-dev] Planning Meeting Post-Notes - 2 May 2012
> 
> On 3-May-2012, at 7:05 AM, Daniel Megert wrote:
> > i.e. they could simply be generated on the fly by the builder
for most bundles (I guess). Is the information stored in the pom.xml, more
frequently changed by the builder team or by the committers that own the
source?
> 
> We want the poms to be committed.  One of the advantages to being
based on Maven/Tycho is that developers can run the build (or a portion
of it) on their own box before making a commit.  Much better than
commit-and-pray.
> 
> Brian.[attachment "smime.p7s" deleted by Daniel Megert/Zurich/IBM]
_______________________________________________
> eclipse-dev mailing list
> eclipse-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
> https://dev.eclipse.org/mailman/listinfo/eclipse-dev