Home » Archived » Eclipse Communications Framework (ECF) » build map files for ecf ganymede build
| |
| Re: build map files for ecf ganymede build [message #623835 is a reply to message #623833] |
Fri, 04 July 2008 05:35   |
 Eugene Kuleshov
Messages: 504
Registered: July 2009 |
Senior Member |
|
|
Thanks Scott. But it doesn't look like valid map file
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ecf/bui lds/org.eclipse.ecf.releng.maps/ecf.core.map?revision=1.16.2 .25&root=Technology_Project&pathrev=p2_workaround
----
feature@org.eclipse.ecf.core=CVS,tag=p2_workaround_1,cvsRoot=:pserver:anonymous@dev.eclipse.org :/cvsroot/technology,path=org.eclipse.ecf/features/org.eclip se.ecf.core-feature
plugin@org.eclipse.ecf.sharedobject=@CVSTag@,:pserver:anonymous@dev.eclipse.org :/cvsroot/technology,,org.eclipse.ecf/plugins/org.eclipse.ec f.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
Scott Lewis wrote:
> They are all in the org.eclipse.ecf.releng.maps project:
>
> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ecf/bui lds/org.eclipse.ecf.releng.maps/?root=Technology_Project
>
>
> The one to care about WRT Ganymede build is the ecf.core.map.
>
> We've been using the p2_workaround branch (because of the 6 ecf
> plugins now in SDK), the p2_workaround_1 tag.
>
> Scott
>
> Eugene Kuleshov wrote:
>> Hi,
>>
>> I wonder if someone can point me to the build map files for ecf
>> ganymede build? They are not published at ECF download page.
>>
>> Thanks
>>
>> Eugene
>>
|
|
|
| Re: build map files for ecf ganymede build [message #623837 is a reply to message #623835] |
Fri, 04 July 2008 06:00 |
Scott Lewis
Messages: 1038
Registered: July 2009 |
Senior Member |
|
|
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/bui lds/org.eclipse.ecf.releng.maps/ecf.core.map?revision=1.16.2 .25&root=Technology_Project&pathrev=p2_workaround
>
> ----
>
> feature@org.eclipse.ecf.core=CVS,tag=p2_workaround_1,cvsRoot=:pserver:anonymous@dev.eclipse.org :/cvsroot/technology,path=org.eclipse.ecf/features/org.eclip se.ecf.core-feature
>
>
> plugin@org.eclipse.ecf.sharedobject=@CVSTag@,:pserver:anonymous@dev.eclipse.org :/cvsroot/technology,,org.eclipse.ecf/plugins/org.eclipse.ec f.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
>
>
> Scott Lewis wrote:
>> They are all in the org.eclipse.ecf.releng.maps project:
>>
>> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ecf/bui lds/org.eclipse.ecf.releng.maps/?root=Technology_Project
>>
>>
>> The one to care about WRT Ganymede build is the ecf.core.map.
>>
>> We've been using the p2_workaround branch (because of the 6 ecf
>> plugins now in SDK), the p2_workaround_1 tag.
>>
>> Scott
>>
>> Eugene Kuleshov wrote:
>>> Hi,
>>>
>>> I wonder if someone can point me to the build map files for ecf
>>> ganymede build? They are not published at ECF download page.
>>>
>>> Thanks
>>>
>>> Eugene
>>>
|
|
|
| Re: build map files for ecf ganymede build [message #623842 is a reply to message #623837] |
Fri, 04 July 2008 06:30 |
Eugene Kuleshov
Messages: 504
Registered: July 2009 |
Senior Member |
|
|
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/bui lds/org.eclipse.ecf.releng.maps/ecf.core.map?revision=1.16.2 .25&root=Technology_Project&pathrev=p2_workaround
>>
>> ----
>>
>> feature@org.eclipse.ecf.core=CVS,tag=p2_workaround_1,cvsRoot=:pserver:anonymous@dev.eclipse.org :/cvsroot/technology,path=org.eclipse.ecf/features/org.eclip se.ecf.core-feature
>>
>>
>> plugin@org.eclipse.ecf.sharedobject=@CVSTag@,:pserver:anonymous@dev.eclipse.org :/cvsroot/technology,,org.eclipse.ecf/plugins/org.eclipse.ec f.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
>>
>>
>> Scott Lewis wrote:
>>> They are all in the org.eclipse.ecf.releng.maps project:
>>>
>>> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ecf/bui lds/org.eclipse.ecf.releng.maps/?root=Technology_Project
>>>
>>>
>>> The one to care about WRT Ganymede build is the ecf.core.map.
>>>
>>> We've been using the p2_workaround branch (because of the 6 ecf
>>> plugins now in SDK), the p2_workaround_1 tag.
>>>
>>> Scott
>>>
>>> Eugene Kuleshov wrote:
>>>> Hi,
>>>>
>>>> I wonder if someone can point me to the build map files for ecf
>>>> ganymede build? They are not published at ECF download page.
>>>>
>>>> Thanks
>>>>
>>>> Eugene
>>>>
|
|
|
| Re: build map files for ecf ganymede build [message #623844 is a reply to message #623842] |
Fri, 04 July 2008 12:04 |
Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Eugene,
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...
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/bui lds/org.eclipse.ecf.releng.maps/ecf.core.map?revision=1.16.2 .25&root=Technology_Project&pathrev=p2_workaround
>>>
>>> ----
>>>
>>> feature@org.eclipse.ecf.core=CVS,tag=p2_workaround_1,cvsRoot=:pserver:anonymous@dev.eclipse.org :/cvsroot/technology,path=org.eclipse.ecf/features/org.eclip se.ecf.core-feature
>>>
>>>
>>> plugin@org.eclipse.ecf.sharedobject=@CVSTag@,:pserver:anonymous@dev.eclipse.org :/cvsroot/technology,,org.eclipse.ecf/plugins/org.eclipse.ec f.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
>>>
>>>
>>> Scott Lewis wrote:
>>>> They are all in the org.eclipse.ecf.releng.maps project:
>>>>
>>>> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ecf/bui lds/org.eclipse.ecf.releng.maps/?root=Technology_Project
>>>>
>>>>
>>>> The one to care about WRT Ganymede build is the ecf.core.map.
>>>>
>>>> We've been using the p2_workaround branch (because of the 6 ecf
>>>> plugins now in SDK), the p2_workaround_1 tag.
>>>>
>>>> Scott
>>>>
>>>> Eugene Kuleshov wrote:
>>>>> Hi,
>>>>>
>>>>> I wonder if someone can point me to the build map files for ecf
>>>>> ganymede build? They are not published at ECF download page.
>>>>>
>>>>> Thanks
>>>>>
>>>>> Eugene
>>>>>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: build map files for ecf ganymede build [message #623846 is a reply to message #623844] |
Fri, 04 July 2008 14:22 |
Eugene Kuleshov
Messages: 504
Registered: July 2009 |
Senior Member |
|
|
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/bui lds/org.eclipse.ecf.releng.maps/ecf.core.map?revision=1.16.2 .25&root=Technology_Project&pathrev=p2_workaround
>>>>
>>>> ----
>>>>
>>>> feature@org.eclipse.ecf.core=CVS,tag=p2_workaround_1,cvsRoot=:pserver:anonymous@dev.eclipse.org :/cvsroot/technology,path=org.eclipse.ecf/features/org.eclip se.ecf.core-feature
>>>>
>>>>
>>>> plugin@org.eclipse.ecf.sharedobject=@CVSTag@,:pserver:anonymous@dev.eclipse.org :/cvsroot/technology,,org.eclipse.ecf/plugins/org.eclipse.ec f.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
>>>>
|
|
|
| Re: build map files for ecf ganymede build [message #623848 is a reply to message #623846] |
Fri, 04 July 2008 15:35 |
Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
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/bui lds/org.eclipse.ecf.releng.maps/ecf.core.map?revision=1.16.2 .25&root=Technology_Project&pathrev=p2_workaround
>>>>>
>>>>> ----
>>>>>
>>>>> feature@org.eclipse.ecf.core=CVS,tag=p2_workaround_1,cvsRoot=:pserver:anonymous@dev.eclipse.org :/cvsroot/technology,path=org.eclipse.ecf/features/org.eclip se.ecf.core-feature
>>>>>
>>>>>
>>>>> plugin@org.eclipse.ecf.sharedobject=@CVSTag@,:pserver:anonymous@dev.eclipse.org :/cvsroot/technology,,org.eclipse.ecf/plugins/org.eclipse.ec f.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
>>>>>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| |
| Re: build map files for ecf ganymede build [message #623852 is a reply to message #623848] |
Fri, 04 July 2008 16:39 |
Scott Lewis
Messages: 1038
Registered: July 2009 |
Senior Member |
|
|
Ed and Eugene,
+1 for state of builds being woeful.
+1 for resources having anything to do with projects working together
instead of as independent units...because IMHO as long as the projects
operate independently (by necessity rather than choice in most cases),
what we have will be the result.
BTW, just for the record...ECF does have a reproducible build...although
reproducing it is not nearly as easy as it might/could be (which I
suspect is true for Platform, EMF, etc.).
Scott
Ed Merks wrote:
> 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/bui lds/org.eclipse.ecf.releng.maps/ecf.core.map?revision=1.16.2 .25&root=Technology_Project&pathrev=p2_workaround
>>>>>>
>>>>>> ----
>>>>>>
>>>>>> feature@org.eclipse.ecf.core=CVS,tag=p2_workaround_1,cvsRoot=:pserver:anonymous@dev.eclipse.org :/cvsroot/technology,path=org.eclipse.ecf/features/org.eclip se.ecf.core-feature
>>>>>>
>>>>>>
>>>>>> plugin@org.eclipse.ecf.sharedobject=@CVSTag@,:pserver:anonymous@dev.eclipse.org :/cvsroot/technology,,org.eclipse.ecf/plugins/org.eclipse.ec f.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
>>>>>>
|
|
|
| Re: build map files for ecf ganymede build [message #623854 is a reply to message #623850] |
Fri, 04 July 2008 17:07 |
Eugene Kuleshov
Messages: 504
Registered: July 2009 |
Senior Member |
|
|
Scott Lewis 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?
> I thought I pretty much said already...@CVStag@ is the desired CVS tag
> :). We've been using p2_workaround_1 as the version of the map files
> themselves.
>
> If you want to reuse the actual scripts that do this, they are
> available in <ecf>/builds/org.eclipse.ecf.releng.server (along with
> instructions for setting up/running, etc).
>> 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).
> Since all build materials (other than map files) are available in the
> org.eclipse.ecf.releng.server project, making them more accessible has
> not been a priority for us relative to getting the actual Ganymede
> build done. If you or others want to contribute resources to do it,
> we will happily help.
All I am asking is to publish map file corresponding to the ecf
builds. See for example platform download page at:
http://download.eclipse.org/eclipse/downloads/drops/R-3.4-20 0806172000/index.php
and their maps file linked from the above page:
http://download.eclipse.org/eclipse/downloads/drops/R-3.4-20 0806172000/directory.txt
Basically that would allow to get the code for given binary build, to
allow to see the source or debug/fix given issues.
But if you are saying that maps files can't be published I will have
to live with that. It is just even you can't say what code been used to
build binaries for Ganymede, since there is no tag and just some
randomly named branch, which can't be used to represent the locked down
version of the code. So, the end result is that code is not auditable.
regards,
Eugene
|
|
| | | |
| |
  |
Goto Forum:
Current Time: Tue Apr 23 15:03:07 GMT 2024
Powered by FUDForum. Page generated in 0.04342 seconds |
] 
Search
Help
Register
Login
Home
