all-IT

With Eclipse is not only very convenient to program Java, but also stands for PHP with the PDT plugin an excellent solution.
If you want to but in his project with general libraries (such as phpunit) work, you must either copy them into his project, or a separate project with its source code to create.

With the Elicpse PTI plugin by PHPSRC there are still a 3rd Possibility. PTI (Eclipse PHP integration tool) is known about the mechanisms Eclipse (update url: http://www.phpsrc.org/eclipse/pti/) PHP libraries as well-known

• PEAR
• PHPUnit
• PHP Code Sniffer and
• External PHP Checker

are available.

This saves a lot of manual work and once again reinforces my opinion that Eclipse is the best development environment (and not just because they charge).

Links:
phpsrc - wiki

update: more links
phphatesme.com - PTI basic configuration

Eclipse is not only very convenient to program Java, but also stands for PHP with the PDT plugin is a great solution. If you want to but with his project ...

gklinkmann written by \ \ tags: eclipse , open source , php

The Eclipse development environment of my choice, I mention again and again (even for those who are now suffering ). Precisely because of its large number of plug-in, it is my Swiss Army knife of programming.

With JadClipse there is now another plugin for the Java decompiler jad can be integrated into Eclipse. The current version (3.4) of the plugin has been rewritten, however, that other backends Decompiler (eg Jode and JD) can be used. About update Url: http://jadclipse.sf.net/update the plugin finds its way in the usual way by Eclipse.

Then you have to make sure that the default editor for JadClipse class files (Preferences> Editors> File Associations> *. Class) is.

For legal reasons, you should of course only decompile your own classes.

Links:
JadClipse - Wiki

The Eclipse development environment of my choice, I mention again and again (even for those who are now suffering). Precisely because of its large number of plug-in, it is my Swiss Army knife ...

gklinkmann written by \ \ tags: eclipse , Java , Open Source

Still, it takes about 1 hour, but then the bezeichnetet Europe as version 3.3 of Eclipse released. Along with this release comes a new version of the plugin collection Callisto . It now contains 21 instead of 10 previously coordinated plugin projects.
This also includes new versions of the Business Intelligence and Reporting Tools (BIRT), Web Tools Project and the Java Development Tools Project.

Since Eclipse is my favorite IDE, I'm going to the new version, of course, download and install. But still it says wait 1 hour. More information is available in two articles by heise and golem .

Still, it takes about 1 hour, but then the bezeichnetet as Europe released version 3.3 of Eclipse. Along with this release comes a new version of the plugin collection ...

gklinkmann written by \ \ tags: eclipse , ide

For now at least not the whole overview of the controller to lose domains and views, it is perhaps time, the IDE support for Groovy and Grails to look at. The IDE of my choice is Eclipse. It is open source, and with its diversity, the plugin Swiss army knife of development environments (albeit a rather large ).

For Groovy and Grails are the following update URL quite a nice plugin with highlighting and a few other amenities.

http://dist.codehaus.org/groovy/distributions/update/

For a pure Groovy project is available in this article on Eclipse Zone .. a pretty good guide with screenshots

The Grails integration with Eclipse, it is of course a section in the excellent documentation of Grails. I have very good experience with the following steps:

• Installation of the Groovy Eclipse plugin, as described above
• Creating your own Workplaces for Grails projects, pointing to the folder where the actual Grails projects are
• Adaptation of Eclipse, as described in the documentation described
• Creating a new Grails project on the command line with grails create-app
• Creating an Eclipse project with the same name of the Grails project. This will be the same with all libraries included in the classpath of Eclipse.

Conclusion: In my favorite IDE Eclipse plugin that Groovy is the best choice to manage Grails projects. Not succeeded so far is the launch of a Grails project from Eclipse. Since the command line but with grails run-app works great and the changes during development are also immediately deployed, it is easy to get over. If someone has a solution for it, I would be very grateful to him anyway.

Update: the latest version of the paper I have to improve maintainability as part of a small tutorial to Grails, and outsourced direct links in the right sidebar.

For now at least not the whole overview of the controller to lose domains and views, it is perhaps time, the IDE support for Groovy and Grails to look at ....

gklinkmann written by \ \ tags: eclipse , grails , ide