[OWASP-ESAPI] Updating to PDT 2.1
Andrew van der Stock
vanderaj at owasp.org
Wed Aug 26 19:10:40 EDT 2009
Ooops - wrong mail list. it really is about the PHP project. I have no
check in rights to the J2EE project anyways.
I think we have an answer as many folks use different IDEs to develop
ESAPI for PHP - we're most likely going to remove the .project file
and make it ignored.
On 26/08/2009, at 9:38 PM, Kevin W. Wall wrote:
> Are you referring to only the .project file for the ESAPI PHP or would
> this affect the ESAPI Java .project file as well.
> I'm OK with it if it is only the ESAPI PHP.
> Andrew van der Stock wrote:
>> Hi folks,
>> I'd like to make one final update to the project that probably should
>> have occurred before we all got going: upgrade to PDT 2.1 as the
>> development environment. I don't know (nor particularly care) about
>> what you use to develop ESAPI for PHP in, but I like to use the
>> and greatest at the beginning of the project, and leave that alone
>> until the project ships.
>> To that end, do folks mind if I upgrade the .project file to use PDT?
>> The alternative is to leave it as is at the moment, and take
>> the .project file out of version control (set to ignore) so that it
>> doesn't get overwritten.
>> I am using:
>> Eclipse 3.5 for PHP (on MacOS X Cocoa)
>> This includes everything we need to develop here in one easy download
>> Xdebug 2.0.5
>> Subclipse 1.6
>> SimpleTest 1.0.5 plugin
>> If you do not have these components, testing and debugging can be
>> complex than is truly necessary.
>> I have a few VMs, I will try to upgrade one of them to PHP 5.3.0 so
>> can test ESAPI on various 5.2.x flavors as well as 5.3.0.
>> OWASP-ESAPI mailing list
>> OWASP-ESAPI at lists.owasp.org
> Kevin W. Wall
> "The most likely way for the world to be destroyed, most experts
> is by accident. That's where we come in; we're computer professionals.
> We cause accidents." -- Nathaniel Borenstein, co-creator of
More information about the OWASP-ESAPI