[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: Re: Re: Re: Re: Re: [wtp-dev] Run WDT/sourceediting, questions - help!
|
You can refresh the branch information
from the context menu of the "Branches" node under the webtools
repository in the CVS Repositories view. Be sure to select all of
the projects you're interested in so that it populates the branches in
the view. Alternately, just select the project's folders you're interested
in and use the "Check Out As" context menu. The third page
in the wizard will allow you to refresh the same information and check
out the tag/branch you're interested in directly.
Regards,
---
Nitin Dahyabhai
Eclipse WTP Source Editing
IBM Rational
stanimir petrov <cristal_reaver@xxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx
07/09/2009 11:58 AM
Please respond to
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx> |
|
To
| "General discussion of project-wide
or architectural issues." <wtp-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| Re: Re: Re: Re: Re: Re: [wtp-dev] Run
WDT/sourceediting, questions - help! |
|
I cannot find this R3_1_maintence branch. :(
-------- Оригинално писмо --------
От: Christopher Jaun
Относно: Re: Re: Re: Re: Re: [wtp-dev] Run WDT/sourceediting, questions
- help!
До: "General discussion of project-wide or architectural issues."
Изпратено на: Сряда, 2009, Юли 8 21:02:18 EEST
If you go to the WTP CVS and look in HEAD you should see
the various JSDT and SSE plugins listed. Right-click on the ones you need
and do a check out.
Now you might be seeing some errors if you are not checking out the correct
branches. Currently HEAD is being used for WTP 3.2 development for Source
editing. If your target build is WTP 3.1 then you'll want to check plugins
out of the R3_1_maintence branch. This could be why you are seeing missing
classes or other errors.
Chris
stanimir petrov <cristal_reaver@xxxxxx>
stanimir petrov <cristal_reaver@xxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx
07/07/2009 10:25 AM
Please respond to
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx> |
|
To
|
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
|
Re: Re: Re: Re: Re: [wtp-dev] Run WDT/sourceediting, questions - help! |
|
Yes i read this tutorial, but the project tree structure is not the same.
Now there is package plugins, which contains packages of the plugins. When
i checkout them separate there are missing classes, problalbly from another
plugin package.
-------- Оригинално писмо --------
От: Christopher Jaun
Относно: Re: Re: Re: Re: [wtp-dev] Run WDT/sourceediting, questions
- help!
До: "General discussion of project-wide or architectural issues."
Изпратено на: Вторник, 2009, Юли 7 16:46:30 EEST
Here is documentation on checking out source code, setting
up your target, and launching a runtime.
http://www.eclipse.org/webtools/community/tutorials/DevelopingWTP/DevelopingWTP.html
The document is a few years old, so some of the dialogs may have changed
a bit, but most of it should be correct.
Thanks,
Chris
stanimir petrov <cristal_reaver@xxxxxx>
stanimir petrov <cristal_reaver@xxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx
07/07/2009 08:30 AM
Please respond to
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx> |
|
To
|
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
|
Re: Re: Re: Re: [wtp-dev] Run WDT/sourceediting, questions - help! |
|
Thank you very much
Although i need to extend the WTP/source editing functionality. We also
intend to buy commersial license for it, so we can customize and make changes
in the WTP/source editing code. That's why i need to set up their plugin
projects and add/change things.
I setuped the plugins as separate projects but there are missing classes,
i suppose because of the separation.
Please can you clarify where can i checkout the projects separately?
-------- Оригинално писмо --------
От: Christopher Jaun
Относно: Re: Re: Re: [wtp-dev] Run WDT/sourceediting, questions
- help!
До: "General discussion of project-wide or architectural issues."
Изпратено на: Вторник, 2009, Юли 7 01:09:01 EEST
It sounds like you are trying to implement some plugins
to extend the existing WTP/Source editing functionality. If that is the
case then you can take the following steps....
1. Download a full WTP build and set it as your Target Platform in the
preferences of the development Eclipse you are using.
2. If you need them check out any plugins from CVS as individual plugin
projects. However, these plugins should already be included in your target,
so this is not required. You only need to do this if you want to look at
the code or patch something in the existing code.
3. For your new functionality create a new plugin project in your workspace.
Add your custom code and extensions there.
4. Launch a runtime workspace using the Run menu or the icon in the toolbar.
The default runtime workbench will be a combination of all the plugins
in your target and those in your workspace. As you make changes and want
to test them just launch a new runtime.
There is a lot of documentation in the eclipse help system and on the eclipse
website about plugin development, so I would suggest looking there for
more information.
Thanks,
Chris
stanimir petrov <cristal_reaver@xxxxxx>
stanimir petrov <cristal_reaver@xxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx
07/03/2009 04:31 AM
Please respond to
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx> |
|
To
|
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
|
Re: Re: Re: [wtp-dev] Run WDT/sourceediting, questions - help! |
|
Ok, and when i want to test my changes to ui for example, how to start
new instance of eclipse with loaded my changed plug in. And if i have changes
in the other plug in projects for example in the core or debug, how can
i run them in one place, without building jars for every plugin and overriding
them in another eclipse folder. I am sorry for the question, this is my
first plug in project and i did not find anywhere how to do this.
-------- Оригинално писмо --------
От: Nitin Dahyabhai
Относно: Re: Re: [wtp-dev] Run WDT/sourceediting, questions - help!
До: "General discussion of project-wide or architectural issues."
Изпратено на: Четвъртък, 2009, Юли 2 19:27:50 EEST
Actually, all of the folders under sourceediting/pluginsare meant to be
individual projects in your workspace. Try checkingthem out as different
projects to start with.
Regards,
---
Nitin Dahyabhai
Eclipse WTP Source Editing
IBM Rational
stanimir petrov <cristal_reaver@xxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx
07/02/2009 04:09 AM
Please respond to
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx> |
|
To
| "General discussion of project-wideor architectural
issues." <wtp-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| Re: Re: [wtp-dev] Run WDT/sourceediting,questions - help! |
|
Thank you very much
I thought so, but i checkout the wtp/sourceediting and i set up it as plugin
project. I must select the needed plugins in the new instance from hereWindows
> Preferences... > Plug-in Development > Target Platform
But i cannot get it how can i add the not build in jars plugins to thetarget
platform. How can i add a set of plugins to the running new instance?
>-------- Оригинално писмо --------
>От: Nitin Dahyabhai
>Относно: Re: [wtp-dev] Run WDT/sourceediting, questions - help!
>До: wtp-dev@xxxxxxxxxxx
>Изпратено на: Сряда, 2009, Юли 1 23:52:14 EEST
>Dimitar,
>You'll have to keep them as separate plug-ins, otherwise you'll haveto
>change the source code in numerous places to support their extension
>points being declared in a different plug-in than they are currently.I'm
>not sure which overview tab you mean, but it's possible to launch withany
>set of plug-ins you choose.
>
>As for the different _javascript_ plug-ins, org.eclipse.wst._javascript_.*
>were the plug-ins used in WTP 2.0 and earlier, and are no longer
>maintained. WTP 3.0 and later include the org.eclipse.wst.jsdt.*
>plug-ins, which provides more full-featured _javascript_ support andis
>under active development. To illustrate the difference at its mostbasic
>level, org.eclipse.wst._javascript_.* contained no validation of _javascript_
>at all.
>
>Regards,
>---
>Nitin Dahyabhai
>Eclipse WTP Source Editing
>IBM Rational
>
>
>
>
>stanimir petrov
>Sent by: wtp-dev-bounces@xxxxxxxxxxx
>07/01/2009 05:38 AM
>Please respond to
>"General discussion of project-wide or architectural issues."
>
>
>
>To
>wtp-dev@xxxxxxxxxxx
>cc
>
>Subject
>[wtp-dev] Run WDT/sourceediting, questions - help!
>
>
>
>
>
>
> Hi guys
>
>My team is intending to use the WDT/sourceediting module of your pojector
>eventualy extend it. We need to build an studio for _javascript_, html,css,
>xml and so on. It will have custom things consernt to the product,which
>we are developing.
>But before contact the eclipse board to ask for the license agreementor
>making our studio open source, we want to make some tests and builds.
>
>So i search the net and your mail list, but i didn't find anything
>intresting for how to build the project.
>I have checkout the module WDT/sourceediting from your cvs. There aremany
>source folders and packages.
>I found that the implementation of the plugins are actualy in plugins
>folder, devided in many plugins.
>My questions are:
>1)How can i run/bulid all the wanting plugins as one i.e. there are
>org.eclipse.wst.jsdt.ui, org.eclipse.wst.jsdt.core,
>org.eclipse.wst.jsdt.debug and so on. How to run all
>org.eclipse.wst.jsdt.* in new instance of eclipse to test. I can runmay
>be one plugin from the overview tab from "Launch an Eclpise application"
>button, but this may be loads only the selected plugin.
>2)There are org.eclipse.wst.jsdt.* and org.eclipse.wst._javascript_.*
>packages. What is the difference and which i can use for _javascript_.
>
>tnx in adnanced
>Dimitar
>
> _______________________________________________
>wtp-dev mailing list
>wtp-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
>_______________________________________________
>wtp-dev mailing list
>wtp-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/wtp-dev
> _______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev