eclipse

Configuring Eclipse For Drupal CVS friendly patch creation

From http://drupal.org/node/75242:

You should only need to set these if you are use Windows. These settings ensure that if you upload files to Drupal.org, or create patches to upload they are in the standardized format (UTF-8, Unix line endings, and CVS -kkv mode).

Make the following changes under Window - Preferences:

#1 Expand the left-hand menu to General - Workspace
* Set Text file encoding to UTF-8.
* Set New text file line delimiter to Unix
#2 Expand the left-hand menu to Team - CVS
* Click on the Files and Folders tab.

NetBeans 6.5 vs PDT for Drupal Development

I have been using Eclipse for years, and have gotten pretty comfortable with PDT. But there are a bunch of little things that irritate me about it, so I recently checked out NetBeans 6.5. Initially I was very excited, but NetBeans' inability to produce patches that can get pass the Drupal testbot is a deal-killer for me. Anyway, here are my notes:

Pros

* Working javascript browser (yay!)
* Right click to folder to find/search (went away in most recent PDT)
* SVN built in
* Simpler plugin manager.
* Better viewing of patch files

Eclipse PDT 2.0 is out

Eclipse PDT 2.0 is out.
http://www.eclipse.org/pdt/release-notes/pdt2_0.php
Looks like it has new features for PHP OOP, which could be handy if some of the bolder plans for Drupal 7 come to pass. Anyone found anything exciting about it yet?

Downloaded it here:
http://www.eclipse.org/pdt/downloads/

Eclipse PDT 1.0 Released.

Lots of exciting releases lately.

  • Eclipse PDT 1.0 – the last couple of release candidates have been really solid. I haven’t had a chance to checkout the XDebug integration yet.
  • jQuery UI – along with the new jQuery 1.2.1 release, this new UI library has the possibility of revolutionizing Drupal.

Eclipse PDT RC3

Well, according to my my page tracker, lots of people are interested in using Eclipse PDT and Xdebug, so I thought I would give a quick report on upgrading to PDT RC3. *Note:* I see the "XDebug plug-in v0.2.0 is out":https://bugs.eclipse.org/bugs/show_bug.cgi?id=169408. At the moment, I am still using v0.1.3
*Update:* Looks like I can't keep using v0.1.3. Upgrading to Java6 has triggered this error when debugging: "An internal error occurred during: 'Computing hasChildren'.":http://dev.eclipse.org/newslists/news.eclipse.tools.php/msg01362.html
I just downloaded v0.2.1, dropped the two jars into the eclipse plugins director, deleted the old jars, started up PDT again, and so far so good.

Eclipse and Module Management - Almost there

Eclipse is a solid tool for creating Drupal modules, but I haven't figured out anyway to use it to create releases. Eclipse comes with a CVS plug in that allows you to checkout the contributions/modules, add your new module and commit it all, no problem. But when it comes time to branch your release(as described here: http://drupal.org/node/17570), simply trying to do: "cvs tag -b DRUPAL-5 modules/mymodule" seems to be impossible. Eclipse is not willing to branch with out also tagging the version you are branching from, and the Drupal contrib release system rejects these verison tags.

Setting up Eclipse PDT and XDebug

Update (since a lot of people still seem to be coming to this page): The latest version of PDT is 1.0.2, which works with Eclipse 3.3, and it is excellent. The Xdebug plugin is now part of the core package, and the instructions on how to use it are part of the standard help.

I decide to move into the word of real-time debugging today. I have been using the PHPEclipse plug in, but I could not find a 5.1.4 version of the debugger it uses. Fortunately, I was able to get the eclipse PDT (formally PhpIDE) working with XDebug.

Syndicate content