Thank you for the fast reply and pointers. We'll give them a try
today and let you know the results.
I have to add, however, that from what you've written it appears that it is
no longer possible to find out just exactly what all the prerequisites for a WTP
build are. As you stated, there are many more libraries specified from
Orbit than are needed in the project map. Are the precise, minimal
prerequisites required for a WTP build really undefined at this point? Or
more likely simply maintained somewhere else? If the latter, a pointer to
that list would be quite helpful as well.
----- Original Message -----
Sent: Tuesday, May 22, 2007 10:32
Subject: [work] Re: [wtp-dev] Loading
workspace with latest WTP project map isnot working
Todd, I entered this bug to
not lose track of the new limitation.
88550 Load Map Projects won't load http map entries
But here's the background and some
suggestions to perhaps help.
HTTP form of the map entry was added specifically for PDE build, so that
bundles that exist elsewhere can more
easily be retrieved using protocols other than
cvs. In this case, the desire is to "pull" the already
built bundles from the orbit download site.
I think most of us normally recommend those types of
jars/bundles are simply put in your target,
for development. Each orbit build produces a zip file that contains all
See for example,
If you do pull them into your workspace,
there's a few problems. First, there's many more bundles listed there in the
map file than is
used in WTP. And, in
most cases, depending on some preference settings and how the project was
it is not trivial to load
multiple versions into your workspace ... you have to give each project a
name .. .such as to include
it's version number after the project name in Eclipse workspace.
If you did want to still try, say
getting a reduced set into your workspace, each Orbit build produces both an
form of the map file, and a more
traditional CVS version of the map file. So ... you just need to figure out
build was used, say by
date and time, and get the corresponding cvs map file, and use Load Map
Projects (on some limit
set of unique
versions, as used by WTP).
Or .. btw,
you could just get the most recent one ... it would be more correct, if
different at all.
Hope this helps,
P.S. Be sure to document any tips
and tricks you learn, so others can benefit from you leading the way :)
Sent by: wtp-dev-bounces@xxxxxxxxxxx
05/22/2007 08:22 PM
"General discussion of project-wide or architectural
|"General discussion of
project-wide or architectural issues."
|[wtp-dev] Loading workspace with
latest WTP project map is not
trying to set up an internal build of WTP 2.0RC0 and are having trouble
pulling all the projects into the workspace using the map file.
We began by using Eclipse
3.3M7 with all prerequisites as specified on the dependencies page. We
loaded up the latest releng tools plugin from the Eclipse platform (http://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops/S-3.3M2-200609220010/org.eclipse.releng.tools-3.3M2.zip). We then pulled the
the RC0 map file
When we load the projects from
the map, everything proceeds along fine until we receive the following error
from CVS in the form of an error dialog:
Could not connect to
I/O exception occurred:
CreateProcess: ssh -l anonymouse http cvs server error=2
It appears the issue is that
the releng tools don't understand non-CVS entries of the form:
I base that on the error message and the fact that Eclipse
tries to create a CVS repository location with 'http' as the server
I checked the documentation on checking out WTP
(http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.wst.doc.isv/html/check_out_tutorial.html) and the map file still seems to be the recommended practice.
So, given all that, what do we
"not know" or are "doing wrong" that causes the import to fail?
All help appreciated.