Re: [cbi-dev] Bug 376586 - migrate repo and product poms to eclipsebuild

[David M Williams <david_williams@xxxxxxxxxx>]

I've make a more specific comment in the
bug, but I will make general question here to make sure more people see
it (and participate in that bug discussion, if appropriate) ... 

I'm wondering exactly what it
is you need from "eclipsebuilder"? Obviously these p2.inf files
for product definitions. What else? 

I would have thought ... forgive my ignorance if already been covered elsewhere
... that we'd end up WITHOUT an "eclipsebuilder" project, per
se? It is so PDE specific, and wonder if the goal should be to have a "tychoEclipseBuidler"
or something to replace it? 

 




From:      
 Thanh Ha <thanh.ha@xxxxxxxxxxx>
To:      
 cbi-dev@xxxxxxxxxxx,

Date:      
 08/04/2012 01:50 AM
Subject:    
   Re: [cbi-dev]
Bug 376586 - migrate repo and product poms        to
       eclipsebuilder
Sent by:    
   cbi-dev-bounces@xxxxxxxxxxx

---

If I understood correctly I should be using the master
branch of eclipsebuilder for both R3 and R4 streams. I guess I'll have
to re-apply the patch then since I applied it to the R4_HEAD branch at
the moment.

The patch is missing the p2.inf files too actually so I created Bug 386605
[1] to track getting these pulled into the build for the correct products.

Thanks,


Thanh

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=386605



On 03/08/2012 8:02 PM, David M Williams wrote:
Yes, we use 'master' of eclipsebuilder.  I am
not sure what you use that 
for, exactly, but the current design is that we use the master version
of 
that project to build all releases (3.8x, 4.2x, and 4.3) and any stream
specific things are not stored there, but stored in the maps project, in
a 
folder call "configuration" which, for which there are the three
main 
(current branches) R3_8_maintenance, R4_2_maintenance, and master. During
our build initialization part of that configuration is  "overlayed"
on top 
of eclipsebuilder to make the run stream specific. For example, see 

http://git.eclipse.org/c/platform/eclipse.platform.releng.maps.git/tree/org.eclipse.releng/configuration/eclipseBuilderOverlays/eclipse/buildConfigs

HTH
 




From:   Thanh Ha <thanh.ha@xxxxxxxxxxx>
To:     Common-build Developers discussion <cbi-dev@xxxxxxxxxxx>,
Date:   08/03/2012 04:29 PM
Subject:        [cbi-dev] Bug 376586 - migrate repo
and product poms to 
eclipsebuilder
Sent by:        cbi-dev-bounces@xxxxxxxxxxx



Hi Everyone,

I've pushed some changes to CBI to build the product files in 
eclipsebuilder. So far I've only push the changes to the R4 branch. 

The eclipsebuilder Juno_RC4_R4 branch is based off of R4_HEAD however I
noticed it hasn't been committed to in about 4 months so I'm not sure if
it's the right branch. I hope someone from the platform team can confirm
which branch we should be using for this.

You can now find the SDK packaged zips at:

 
eclipse.platform.releng.eclipsebuilder/eclipse/buildConfigs/sdk/builder/target/products

and the buildConfigs directory has a few other products that are building
now including:

    - platform
    - platform.sdk
    - rcp
    - rcp.config
    - rcp.sdk


Some things I did have to comment out of rcp.config/build.properties are
all the root.* lines which we will need to look into getting them 
building, I created Bug 386599 [1] to track this.


Thanh

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=386599
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev





_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev