[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pdt-dev] Eclipse PDT

Michal,

 

A few notes.

 

1. I found switching to âEclipse for Committersâ to be quite helpful. I deleted all of my old Eclipse installations and installed âEclipse for Committersâ. This appears to have solved some problems. See http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/oxygen/3a/eclipse-committers-oxygen-3a-linux-gtk-x86_64.tar.gz

 

2. I used your new PSF file. No problems. Very helpful.

 

3. I created all of the release dependent AST and scanner components by running a Debug configuration. This worked well and created the missing AST and scanner components.

 

4. I was not able to run without the additional plug-ins. I tried to do so and had numerous errors. For example, many projects were missing (and needed) the DLTK plug-ins. I installed all of the additional plug-ins and the compilation problems went away.

 

Overall, these changes were a large plus. At this point I can easily debug PDT.

 

Thank you

 

Peter Schaeffer

 

From: pdt-dev-bounces@xxxxxxxxxxx [mailto:pdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Michal Niewrzal
Sent: Sunday, May 6, 2018 3:48 PM
To: PDT Developers
Subject: Re: [pdt-dev] Eclipse PDT

 

Hi,

 

I think because initial problems you go too deep into the configuration. If you will follow new steps from https://wiki.eclipse.org/PDT/Contributing#Importing_the_PDT_projects then you should be able to run/configure PDT much faster.

 

Also, let me clarify few things:

* For developing PDT we recommend "Eclipse IDE for Eclipse Committers", package "Eclipse for PHP Developers" is what we are developing as PDT team :)

* Use pdt-dev.psf to import projects, I fixed it and now all projects should be imported correctly

* You don't need to install additional plugins to "Eclipse IDE for Eclipse Committers", just use Target Platform described in Contributing page. It will download all required plugins.

* Github version of PDT is just a copy of PDT repo, its ok at the beginning but main repo is under http://git.eclipse.org/gitroot/pdt/org.eclipse.pdt.git

 

Regards,

Michal

 

niedz., 6 maj 2018 o 21:56 Peter Schaeffer <peter_schaeffer@xxxxxxxxx> napisaÅ(a):

Hi,

 

I have made a bit of progress with this. Just a bit. But some progress nonetheless. A few notes (steps).

 

1. I downloaded and installed the standard Oxygen 3a PHP Eclipse mplementation from https://www.eclipse.org/downloads/packages/eclipse-php-developers/oxygen3a. Note that I had no intention of actually using any of this code (at this point). My only intent was to copy the plugins directory to a safe place (which I did). The only jar I really needed was org.eclipse.php.core_5.3.0.201803070838.jar. However, I did not know that at the time.

 

2. I then deleted the entire Oxygen 3a PHP Eclipse install (but kept the saved plugins directory).

 

3. I downloaded and installed the standard Oxygen 3a RCP/RAP Eclipse implementation from https://www.eclipse.org/downloads/packages/eclipse-rcp-and-rap-developers/oxygen3a.

 

4. I then added two additional sites from installing software. They were

 

http://download.eclipse.org/technology/dltk/updates-dev/latest-nightly

http://download.eclipse.org/tools/orbit/downloads/drops/R20180330011457/repository

 

Note that the second link is for the Oxygen 3a Eclipse version of the Orbit tools.

 

5. I then installed all of the components listed below. This list was obtained from the PDT/Contributing page (https://wiki.eclipse.org/PDT/Contributing#Working_with_PDT_source_code_in_Eclipse).

  • Dynamic Languages Toolkit - Core Frameworks SDK
  • Dynamic Languages Toolkit - Core Lucene Index Frameworks SDK
  • Dynamic Languages Toolkit - Mylyn Integration
  • DLTK Core Tests
  • Eclipse Web Developer Tools
  • Apache Commons Exec Plug-in
  • TM Terminal
  • BIRT Framework
  • Zest SDK
  • Parallel Tools Platform
  • Eclipse/Gerrit integration (aka EGerrit)

6. The first four are from the DLTK site. The Apache Commons Exec Plug-in is from the Orbit site. Note that it is imperative that actual executable jar be installed for the Apache Commons Exec Plug-in. Some of the versions of this plug-in are actually the source, not the executable class files. The other six components were obtained from http://download.eclipse.org/releases/oxygen.

7. At this point I added a git repository (repository https://github.com/eclipse/pdt) and imported branch 5.3 (Stable). This produced a long list of PHP projects (roughly 60), most of where were clean. A few had compilation errors. I was able to fix all of the compilation errors, by adding the saved plugin (org.eclipse.php.core_5.3.0.201803070838.jar) as an external jar. Now I had all of the PHP projects imported and zero errors.

8. At this point I disabled the API baseline as described by the https://wiki.eclipse.org/PDT/Contributing#Working_with_PDT_source_code_in_Eclipse web page. This worked well.

9. At this point I tried to âSelect current Target Platformâ as described by the https://wiki.eclipse.org/PDT/Contributing#Working_with_PDT_source_code_in_Eclipse web page. This step failed. Numerous compilation errors showed up (probably because many plug-ins were excluded). I switched back to the âRunning Platform (Active)â and the compilation errors went away.

10. I tried the approach described under âRunning and debugging PDTâ on the PDT/Contributing web page. I created a new Run -> Debug Configuration for a new Eclipse Application. I tried launching the new Debug Configuration. This step did create a new copy of Eclipse with PHP âinstalledâ. I tried to configure the new PHP copy of Eclipse. I had numerous failures. This approach this did not work.

11. I then created a new completely separate copy of Oxygen 3a Eclipse for PHP using separate folders for everything (plug-ins, the workspace, etc.). Ideally the PHP copy of Eclipse should have been created using a different userid. I didnât use a separate userid, which meant that the .eclipse, .p2, and .tooling folders were shared between the PHP copy of Eclipse and the RCP/RAP copy of Eclipse.

12. I then modified the eclipse.ini file of the PHP copy of Eclipse by adding one line after âvmargs line. The new line is

-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y

The new line causes the PHP copy of Eclipse to hang waiting for a debug connection during initialization.

13. I then created a Remote Java Application Debug Configuration in the RCP/RAP copy of Eclipse and ran it (the Remote Java Application Debug Configuration). This caused the PHP copy of Eclipse to finish initialization and run. Perhaps more relevantly, breakpoints set using RCP/RAP copy Eclipse stopped the PHP copy of Eclipse as need be.

I still have more work to do (source is missing in many cases). However, at least the basics are now working.

Thank you

Peter Schaeffer

From: Peter Schaeffer [mailto:peter_schaeffer@xxxxxxxxx]
Sent: Saturday, May 5, 2018 12:51 PM
To: 'PDT Developers'
Cc: 'Michele Locati'
Subject: RE: [pdt-dev] Eclipse PDT

 

Hi,

 

I have a few quick questions.

 

1. Do you folks use git?

2 What git branch are you on?

3. The missing AST scanners seem to be caused by .gitignore files. Has anyone else seen this?

 

Thank you

 

Peter Schaeffer

 

From: Peter Schaeffer [mailto:peter_schaeffer@xxxxxxxxx]
Sent: Friday, May 4, 2018 6:06 PM
To: 'PDT Developers'
Cc: 'Michele Locati'
Subject: RE: [pdt-dev] Eclipse PDT

 

Hi,

 

I have tried quite a bit to get the PDT development environment installed under Eclipse. No luck so far.

 

One (big) problem was my fault. I installed the source version of the Apache Commons Exec plugin rather than the executable version of the Apache Commons Exec Plugin. That caused everything that depended on the Apache Commons Exec plugin to not compile.

 

I fixed that problem by installing the correct version of the Apache Commons Exec plugin. However, lots of code still won't compile.

 

So far I have found that quite a few of the PDT components don't have a .project file. Why is not clear. I have temporarily gotten around this problem by creating my own PSF file with the failing components removed. This helped. However, plenty of components still donât compile. See below.

 

Thank you

 

Peter Schaeffer

 

Error! Filename not specified.

 

-----Original Message-----
From: pdt-dev-bounces@xxxxxxxxxxx [mailto:pdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Michele Locati
Sent: Friday, May 4, 2018 3:15 AM
To: PDT Developers
Subject: Re: [pdt-dev] Eclipse PDT

 

Hi Peter,

 

when I started to contribute to PDT (a few months ago) I spent a lot

of time understanding how to do that, and updated

https://wiki.eclipse.org/PDT/Contributingaccordingly.

By the way it seems that something changed recently: that page

requires to be updated again (but sincerely I don't know how ;).

 

PS: IMHO that the Contributing page is the most important one for the

PDT project.

 

--

Michele

 

 

2018-05-04 6:09 GMT+02:00 Peter Schaeffer <peter_schaeffer@xxxxxxxxx>:

> Hi Folks,

> A few weeks ago I had a problem with PDT. See the links below for a

> description.

> https://bugs.eclipse.org/bugs/show_bug.cgi?id=533928

> https://stackoverflowcom/questions/49965546/xdebug-problems-with-eclipse-php-pdt#49965546

> https://www.eclipse.org/forums/index.php/f/85/

> https://www.eclipseorg/forums/index.php/t/1092935/

> As you can see, I posted the problem in a few places but didnât get much of

> a response. I really wasnât that surprised. The problem is pretty deep.

> Then I had a idea. Perhaps I could figure the problem out from the PDT

> source code and contribute the fix (assuming that itâs a bug rather than a

> configuration error on my part) back to you folks.

> My next step was to try to install the PDT development environment.

> Basically, I followed the instructions over at PDT/Contributing

> (https://wiki.eclipse.org/PDT/Contributing) but did not end with a working

> environment. See the images below.

> I was able to make a bit more progress by removing a few entries from the

> PSF file However, I still ended up with lots or errors.

> What is the correct approach for doing this?

> Thank you

> Peter Schaeffer

> _______________________________________________

> pdt-dev mailing list

> pdt-dev@xxxxxxxxxxx

> To change your delivery options, retrieve your password, or unsubscribe from

> this list, visit

> https://dev.eclipse.org/mailman/listinfo/pdt-dev

_______________________________________________

pdt-dev mailing list

pdt-dev@xxxxxxxxxxx

To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/pdt-dev

_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/pdt-dev