[news.eclipse.platform] Re: build map files for ecf ganymede build

[Ed Merks <Ed.Merks@xxxxxxxxx>]

Eugene,

The state of builds is woeful.  It's a black art.  Maybe the 
newly-created, just-announced common build component will help bring 
order to the chaos.   I think things are the way they are, because 
builds are never seen as the top priority even though they should be.  
People are quite happy to butcher up a complete disaster and when it 
finally produces something that looks okay declare victory and move on 
to more important things.  The difficulty of producing builds is a major 
barrier for folks starting new projects at Eclipse and although the EMO 
was asked by the board to look into providing infrastructure for build 
support, the lack of resource has made progress on that haltingly slow...


Eugene Kuleshov wrote:
> Ed Merks wrote:
> > Of course if all the projects used a common build infrastructure then 
> > it gets easier for everyone to have the same set of nice features.  
> > Maybe one day we'll have such a much-needed thing...
>  Ed, the current situation with builds is actually quite scary. I've 
> looked trough several projects released for Ganymede and it is 
> shocking to see what they have in their maps files. I see modules 
> built from HEAD (i.e. no tag), modules that are not using anonymous 
> connection (i.e. :ext:username@) and even modules that are build from 
> non Eclipse CVS. Even Platform have those issues and at minimum it 
> means that those builds are not reproducible.
>
>  regards,
>  Eugene
>
> > Eugene Kuleshov wrote:
> > >  So, we back to the original question how to get the actual map 
> > > files used to build ganymede artifacts. In other words, what 
> > > substitution been used for ganymede build?
> > >
> > >  It would be handy to publish the map files used to produce each 
> > > build like it is done by Platform, EMF, WTP and number of other 
> > > Eclipse projects (see corresponding download pages).
> > >
> > >  Thanks
> > >
> > >  Eugene
> > >
> > >
> > > Scott Lewis wrote:
> > > > Our build does textual substitution to replace the @CVSTag@ with 
> > > > the appropriate tag.
> > > >
> > > > Scott
> > > >
> > > > Eugene Kuleshov wrote:
> > > > >  Thanks Scott. But it doesn't look like valid map file 
> > > > > http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ecf/builds/org.eclipse.ecf.releng.maps/ecf.core.map?revision=1.16.2.25&root=Technology_Project&pathrev=p2_workaround 
> > > > >
> > > > > ----
> > > > >
> > > > > feature@xxxxxxxxxxxxxxxxxxxx=CVS,tag=p2_workaround_1,cvsRoot=:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/technology,path=org.eclipse.ecf/features/org.eclipse.ecf.core-feature 
> > > > >
> > > > >
> > > > > plugin@xxxxxxxxxxxxxxxxxxxxxxxxxxxx=@CVSTag@,:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/technology,,org.eclipse.ecf/plugins/org.eclipse.ecf.core.sharedobject 
> > > > >
> > > > > ...
> > > > > ----
> > > > >
> > > > >  the first feature entry looks ok, but there rest have this 
> > > > > @CVSTag@, which does not match the pde fetch spec at 
> > > > > http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.pde.doc.user/guide/tasks/pde_fetch_phase.htm 
> > > > >
> > > > >
> > > > >  regards,
> > > > >  Eugene