Home » Language IDEs » ServerTools (WTP) » Setting up a workspace for WTP Development
| Setting up a workspace for WTP Development [message #146800] |
Thu, 10 November 2005 16:13  |
Eclipse User |
|
|
|
Originally posted by: scott.anderson.genuitec.com
I looked all through the project documentation for an answer to this
question and apologize in advance if I missed it.
What I'd like to do is set up a workspace connected to the WTP repository so
I can build, launch and debug WTP locally. When I looked at the repository,
I noticed that each component has a rather deep hierarchy to get to their
plugins.
My question is simply what's the best way to quickly setup a buildable
workspace for WTP? Is everyone expected to navigate the CVS hierarchy and
individually select every plugin and feature? Is there a list somewhere of
which ones are required? Is there a team project set or some other
mechanism that will allow me to create such a debuggable workspace quickly?
Any help would be greatly appreciated.
Thanks in advance,
--Scott
|
|
| |
| Re: Setting up a workspace for WTP Development [message #146841 is a reply to message #146805] |
Fri, 11 November 2005 13:07  |
| Eclipse User |
|
|
|
Originally posted by: scott.anderson.genuitec.com
Jochen,
Thanks for responding with these steps so quickly! I really appreciate it.
I'll give this a try by Monday at the latest and follow up with any
additional questions or clarifications then.
Best regards,
--Scott
"Jochen Krause" <jkrause@innoopract.de> wrote in message
news:dl0jr0$irm$1@news.eclipse.org...
> How to check out the WTP plugins from CVS
>
> It is recommended to check out the plugins via the releng tools.
> The advantage is to have plugin versions that correspond to CVS tags,
> which you can specify if you are talking about your intallation (-bugs).
>
> First, download the current releng tools version (you will find it at the
> bottom of the download pages for eclipse project builds).
>
> For example 3.2 M3 - look at the bottom of the page:
> http://download.eclipse.org/eclipse/downloads/drops/S-3.2M3- 200511021600/index.php
>
> Then you will need the map files of the webtools build that you plan to
> load into your workspace. A link to the map file is included on all
> download pages at the top of the page, e.g for the Nov 5 IBuild:
> http://download.eclipse.org/webtools/downloads/drops/I-I2005 1105-200511051946/directory.txt
>
> Create a new simple project in your workspace. Create a new file with an
> .map extension. Paste the content from the above mentioned map file into
> this file.
>
> Right-click on the .map file in your workspace. Select: Team - Load Map
> Projects. (If you copyed all map files entries into the file, it may take
> a little while to check out all projects).
>
> Done! You should now have checked out all WTP plugins into your workspace.
>
> Hope this helps
>
> Jochen
>
>
> Scott Anderson wrote:
>> I looked all through the project documentation for an answer to this
>> question and apologize in advance if I missed it.
>>
>> What I'd like to do is set up a workspace connected to the WTP repository
>> so I can build, launch and debug WTP locally. When I looked at the
>> repository, I noticed that each component has a rather deep hierarchy to
>> get to their plugins.
>>
>> My question is simply what's the best way to quickly setup a buildable
>> workspace for WTP? Is everyone expected to navigate the CVS hierarchy
>> and individually select every plugin and feature? Is there a list
>> somewhere of which ones are required? Is there a team project set or
>> some other mechanism that will allow me to create such a debuggable
>> workspace quickly? Any help would be greatly appreciated.
>>
>> Thanks in advance,
>> --Scott
|
|
|
| Re: Setting up a workspace for WTP Development [message #146942 is a reply to message #146805] |
Mon, 14 November 2005 10:52 |
| Eclipse User |
|
|
|
Originally posted by: scott.anderson.genuitec.com
Jochen,
I had a chance to try it out using the 1.0M8 map and everything worked just
great! Thank you very much for the assistance.
I just have one more question: is there a map available for whatever is
considered "HEAD" or the current working build for the dev team? How does
the dev team know what's "current" for all the projects?
Thanks again,
--Scott
"Jochen Krause" <jkrause@innoopract.de> wrote in message
news:dl0jr0$irm$1@news.eclipse.org...
> How to check out the WTP plugins from CVS
>
> It is recommended to check out the plugins via the releng tools.
> The advantage is to have plugin versions that correspond to CVS tags,
> which you can specify if you are talking about your intallation (-bugs).
>
> First, download the current releng tools version (you will find it at the
> bottom of the download pages for eclipse project builds).
>
> For example 3.2 M3 - look at the bottom of the page:
> http://download.eclipse.org/eclipse/downloads/drops/S-3.2M3- 200511021600/index.php
>
> Then you will need the map files of the webtools build that you plan to
> load into your workspace. A link to the map file is included on all
> download pages at the top of the page, e.g for the Nov 5 IBuild:
> http://download.eclipse.org/webtools/downloads/drops/I-I2005 1105-200511051946/directory.txt
>
> Create a new simple project in your workspace. Create a new file with an
> .map extension. Paste the content from the above mentioned map file into
> this file.
>
> Right-click on the .map file in your workspace. Select: Team - Load Map
> Projects. (If you copyed all map files entries into the file, it may take
> a little while to check out all projects).
>
> Done! You should now have checked out all WTP plugins into your workspace.
>
> Hope this helps
>
> Jochen
>
>
> Scott Anderson wrote:
>> I looked all through the project documentation for an answer to this
>> question and apologize in advance if I missed it.
>>
>> What I'd like to do is set up a workspace connected to the WTP repository
>> so I can build, launch and debug WTP locally. When I looked at the
>> repository, I noticed that each component has a rather deep hierarchy to
>> get to their plugins.
>>
>> My question is simply what's the best way to quickly setup a buildable
>> workspace for WTP? Is everyone expected to navigate the CVS hierarchy
>> and individually select every plugin and feature? Is there a list
>> somewhere of which ones are required? Is there a team project set or
>> some other mechanism that will allow me to create such a debuggable
>> workspace quickly? Any help would be greatly appreciated.
>>
>> Thanks in advance,
>> --Scott
|
|
| | |
| Re: Setting up a workspace for WTP Development [message #147370 is a reply to message #146942] |
Wed, 16 November 2005 19:43 |
| Eclipse User |
|
|
|
You can get HEAD if you delete the tags from the map file e.g.
plugin@org.eclipse.ui.externaltools=,:pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse
will checkout from head.
Jochen
Scott Anderson wrote:
> Jochen,
>
> I had a chance to try it out using the 1.0M8 map and everything worked just
> great! Thank you very much for the assistance.
>
> I just have one more question: is there a map available for whatever is
> considered "HEAD" or the current working build for the dev team? How does
> the dev team know what's "current" for all the projects?
>
> Thanks again,
> --Scott
>
>
> "Jochen Krause" <jkrause@innoopract.de> wrote in message
> news:dl0jr0$irm$1@news.eclipse.org...
>
>>How to check out the WTP plugins from CVS
>>
>>It is recommended to check out the plugins via the releng tools.
>>The advantage is to have plugin versions that correspond to CVS tags,
>>which you can specify if you are talking about your intallation (-bugs).
>>
>>First, download the current releng tools version (you will find it at the
>>bottom of the download pages for eclipse project builds).
>>
>>For example 3.2 M3 - look at the bottom of the page:
>> http://download.eclipse.org/eclipse/downloads/drops/S-3.2M3- 200511021600/index.php
>>
>>Then you will need the map files of the webtools build that you plan to
>>load into your workspace. A link to the map file is included on all
>>download pages at the top of the page, e.g for the Nov 5 IBuild:
>> http://download.eclipse.org/webtools/downloads/drops/I-I2005 1105-200511051946/directory.txt
>>
>>Create a new simple project in your workspace. Create a new file with an
>>.map extension. Paste the content from the above mentioned map file into
>>this file.
>>
>>Right-click on the .map file in your workspace. Select: Team - Load Map
>>Projects. (If you copyed all map files entries into the file, it may take
>>a little while to check out all projects).
>>
>>Done! You should now have checked out all WTP plugins into your workspace.
>>
>>Hope this helps
>>
>>Jochen
>>
>>
>>Scott Anderson wrote:
>>
>>>I looked all through the project documentation for an answer to this
>>>question and apologize in advance if I missed it.
>>>
>>>What I'd like to do is set up a workspace connected to the WTP repository
>>>so I can build, launch and debug WTP locally. When I looked at the
>>>repository, I noticed that each component has a rather deep hierarchy to
>>>get to their plugins.
>>>
>>>My question is simply what's the best way to quickly setup a buildable
>>>workspace for WTP? Is everyone expected to navigate the CVS hierarchy
>>>and individually select every plugin and feature? Is there a list
>>>somewhere of which ones are required? Is there a team project set or
>>>some other mechanism that will allow me to create such a debuggable
>>>workspace quickly? Any help would be greatly appreciated.
>>>
>>>Thanks in advance,
>>>--Scott
>
>
>
|
|
| | |
| Re: Setting up a workspace for WTP Development [message #147608 is a reply to message #147514] |
Thu, 17 November 2005 19:08 |
| Eclipse User |
|
|
|
David Williams wrote:
> On Wed, 16 Nov 2005 13:35:21 -0500, Darryl L. Miles
> <darryl@netbauds.net> wrote:
>
>
>> I am now in a situation that I have MAP files from two specific I-builds
>> and my workspace is already loaded with the CVS tags for the old I-build.
>>
>
> I can't follow all the "ins and outs" of this thread, but there is a few
> simple things to emphasize. 1. Once you have in your workspace, don't
> forget you can
> simply use "replace..." with head (or what ever) version.
>
> 2. There's nothing too strict about the map files. you can import a map
> file, or directory.txt file
> from a build's download page, edit it to include some sub set you want
> (or delete what you dont' want).
> and then use same "load from map" action.
>
> HTH
Thanks but... if I want to replace with HEAD (or whatever version) I
have to do this manually for upto 247 projects after I have manually
worked out the exact CVS TAG I need to pull for each indiviual project
and manually worked out which projects are dependancies.
But this is exactly whats described a MAP file.
The dependancies issue could be dealt with like the Eclipse core do by
publishing multiple map files. But I appreciate that currently WTP
intra-component dependancies are not 100% clean so its not going to work
just yet, thats ok by me.
Importing a MAP file means I have to delete the existing WTP project in
my workspace that I may have worked on. If you load another MAP file
the first thing it wants to do is delete the WTP project that already
exists. I don't want to do this. I'd loose my work.
It also means a complete CSV checkout of the entire module from scratch
when thats not necessary. Seems like increasing your server load when I
only need to pull the patches since last weeks I build.
What I want to do is be able to go from one I-build MAP file to another
each week, so that I can recompile / link my code against the newer
I-build before continuing development of it.
Currently it looks like I just have to pick an I-build version and stick
with it, because its just too much manual work to keep up.
Darryl
|
|
|
| Re: Setting up a workspace for WTP Development [message #147624 is a reply to message #147608] |
Thu, 17 November 2005 20:20 |
| Eclipse User |
|
|
|
On Thu, 17 Nov 2005 19:08:29 -0500, Darryl L. Miles <darryl@netbauds.net=
> wrote:
> What I want to do is be able to go from one I-build MAP file to anothe=
r each week, so that I can recompile / link my code
> against the newer I-build before continuing development of it.
>Currently it looks like I just have to pick an I-build version and stic=
k with it, because its just too much manual work to
> keep up.
Does using PDE Targets help accomplish what you want to do?
I know many who use a PDE target which had Eclipse 3.1.1,
all the prereq's, (EMF, GEF, etc.), and "the latest"
I-build from WTP.
Then all they have in their workspace (from head, typically) are the
plugins they have had to modify/patch and/or their own new plugins.
From week to week they upgrade their I-build "target" to make sure
still "in synch".
PDE is pretty good about using the "right" plugins for the "build path"
.... workspace first, even if in target, but if removed from workspace,
it'll use the target version.
Some of this is described in
http://www.eclipse.org/webtools/community/tutorials/Developi ngWTP/Develo=
pingWTP.html
if you haven't seen that yet.
|
|
|
| Re: Setting up a workspace for WTP Development [message #147631 is a reply to message #147608] |
Thu, 17 November 2005 20:37 |
| Eclipse User |
|
|
|
On Thu, 17 Nov 2005 19:08:29 -0500, Darryl L. Miles <darryl@netbauds.net=
> wrote:
> The dependancies issue could be dealt with like the Eclipse core do by=
publishing multiple map files. But I appreciate
> that currently WTP intra-component dependancies are not 100% clean so =
its not going to work just yet, thats ok by me.
>
We do have mutliple map files. They are in the
releng project, just like the base Eclipse.
The names of the files, such as wst-common-core.map,
wst-common-ui.map, etc, are meant to correspond to the
same names as outlined in
http://www.eclipse.org/webtools/development/arch_and_design/ subsystems/S=
ubsystemsAndFeatures.html
with the same dependancies as outlined in that document.
(And, there's probably a few "bugs" in that description, where
things are not quite right, or out of date, but should be close).
Hope this helps
|
|
|
| Re: Setting up a workspace for WTP Development [message #148148 is a reply to message #147608] |
Mon, 21 November 2005 09:13 |
| Eclipse User |
|
|
|
Darryl,
Would you be interested in a project set of the WTP plugins (no
features) at HEAD, with or without tests? That is typically what I uses
for the reasons you cite. There is a risk that you can pick up
unreleased changes and there will be errors in the build. Of late, some
simple local changes have been enough to keep things working if a
correction to such an error didn't arrive in a timely fashion.
Cheers,
Larry
Darryl L. Miles wrote:
> David Williams wrote:
>
>> On Wed, 16 Nov 2005 13:35:21 -0500, Darryl L. Miles
>> <darryl@netbauds.net> wrote:
>>
>>
>>> I am now in a situation that I have MAP files from two specific I-builds
>>> and my workspace is already loaded with the CVS tags for the old
>>> I-build.
>>>
>>
>> I can't follow all the "ins and outs" of this thread, but there is a few
>> simple things to emphasize. 1. Once you have in your workspace, don't
>> forget you can
>> simply use "replace..." with head (or what ever) version.
>>
>> 2. There's nothing too strict about the map files. you can import a
>> map file, or directory.txt file
>> from a build's download page, edit it to include some sub set you want
>> (or delete what you dont' want).
>> and then use same "load from map" action.
>>
>> HTH
>
>
> Thanks but... if I want to replace with HEAD (or whatever version) I
> have to do this manually for upto 247 projects after I have manually
> worked out the exact CVS TAG I need to pull for each indiviual project
> and manually worked out which projects are dependancies.
>
> But this is exactly whats described a MAP file.
>
> The dependancies issue could be dealt with like the Eclipse core do by
> publishing multiple map files. But I appreciate that currently WTP
> intra-component dependancies are not 100% clean so its not going to work
> just yet, thats ok by me.
>
>
>
> Importing a MAP file means I have to delete the existing WTP project in
> my workspace that I may have worked on. If you load another MAP file
> the first thing it wants to do is delete the WTP project that already
> exists. I don't want to do this. I'd loose my work.
>
> It also means a complete CSV checkout of the entire module from scratch
> when thats not necessary. Seems like increasing your server load when I
> only need to pull the patches since last weeks I build.
>
>
>
> What I want to do is be able to go from one I-build MAP file to another
> each week, so that I can recompile / link my code against the newer
> I-build before continuing development of it.
>
> Currently it looks like I just have to pick an I-build version and stick
> with it, because its just too much manual work to keep up.
>
>
> Darryl
|
|
|
Goto Forum:
Current Time: Sun Apr 20 09:45:11 EDT 2025
Powered by FUDForum. Page generated in 0.04385 seconds |
Home