- This topic has 10 replies, 3 voices, and was last updated 17 years, 7 months ago by
.
-
Posts
-
Since MyEclipse requires removing the standard WTP from Eclipse 3.2, does anybody know if installing PHP IDE or PDT (http://www.eclipse.org/php/) will work without breaking MyEclipse in the notorious ways mentioned here when WTP is installed?
I think it’s important that these two things work together, but am leery of trying it and losing productivity unless nobody else knows offhand. I tried a couple rudimentary searches in the forum, but got pretty random results not really applicable to the domain.
Since MyEclipse requires removing the standard WTP from Eclipse 3.2, does anybody know if installing PHP IDE or PDT (http://www.eclipse.org/php/) will work without breaking MyEclipse in the notorious ways mentioned here when WTP is installed?
Just to clarify, the situation is that MyEclipse 5.1.0 builds ontop of standard WTP 1.5.2. We did have to make one minor change to WST/JST and add a helper class to them that supports our new validation-exclusion feature in 5.1, that’s the only change (and some bug fixes).
So given that, as long as your PHP IDE plugin works with WTP 1.5.2, it should work fine along side a clean install of MyEclipse.
I have not personally tested this setup though… you could try doing a test setup by first downloading our All-In-One installer for Windows, installing it, then adding PHP IDE (the installer is a pre-configured setup of JDK/Eclipse/WTP/MyEclipse all ready to run in a best-case setup).
It does not appear that this works for the upcoming PDT release. I get the following message when trying to install on the All-In-One:
PDT Feature (0.7.0.v20070101——9FhPQOPYPY) requires feature “org.eclipse.wst.common_core.feature (1.5.0)”, or later version.
This error message is when trying to use the updater to pull down the repository at:
That is possible if PDT is building against nightlies or milestones which is possible with some pre-1.0 projects. They don’t have the requirement to be stable-API compatible yet I believe.
This doesn’t appear to be the case. On a standalone Eclipse, I can download the regular WTP from the Callisto Discovery site and the PDT works fine. It only seems that in its absence and MyEclipse’s WTP replacement, does this requirement look to be unable to resolve from the updater’s standpoint.
Can you force the upgrade? The problem might be that we bumped the version of WST one because of our changes (required so the platform loads our WST instead of WTP’s) and the plugin could be seeing a different version when in reality it’s perfectly compatible.
The package can be downloaded as a ZIP file and extracted into the eclipse directory. Upon the next restart, it will be there and appears to function as I would expect; however, the updater then refuses to install anything else via the eclipse updater citing the failure previously mentioned as a reason the new configuration will not work out. So this will force the user to manually install anything new (including MyEclipse updates) via a manual process and not the control panel tool.
Again the failure is:
PDT Feature (0.7.0.v20070101——9FhPQOPYPY) requires feature “org.eclipse.wst.common_core.feature (1.5.0)”, or later version.
Are there bug reports on eclipse.org for the additional functionality you are adding to WTP such that the need for a customized version in future MyEclipse versions is not necessary? Is there something that should be added to the bugzilla for PDT enabling differing implementations of WST?… such as, are they keying off the wrong class and version and instead should key off an interface level?
however, the updater then refuses to install anything else via the eclipse updater citing the failure previously mentioned as a reason the new configuration will not work out.
Unfortunately this is one of the biggest problems with the update manager.
So this will force the user to manually install anything new (including MyEclipse updates) via a manual process and not the control panel tool.
Agreed that’s not the most ideal situation.
Are there bug reports on eclipse.org for the additional functionality you are adding to WTP such that the need for a customized version in future MyEclipse versions is not necessary?
Not that I’m aware of. We had to add a basic hook to support turning off the validators (controlled by WTP) on files that people want to ignore. It wasn’t major, but we did have to hook in at the WST level. I’m sure they will add something soon to support this then we can roll ontop of what they are doing as we’ve done in the past.
such as, are they keying off the wrong class and version and instead should key off an interface level?
I don’t believe that is the problem. I believe PDT is set to require a very specific version of WST, so when it doesn’t see it (in this case, MyEclipse’s increments the WST version, so it doesn’t match 1:1) it refuses to install. One solution might be to loosen the PDT requirement, unfortunately I’m not sure how to do this off hand.
In the long run, if both plugins work stable next to eachother, I would just force the install and manage it over the next year or so until everyone gets resynced on the new Europa release, then I would just rebuild my install. Since all the settings are in the workspace, it’s not so much of a pain.
I don’t get it. Are you saying that we need to manage manual updates for a year, until MyEclipse gets a fix for this? That sounds borderline ridiculous. My subscription expires in 32 days. I will be giving a good hard look at the other options before I decide to renew, if this is the kind of response time we can expect from MyEclipse.
I installed the current MyEclipse all in one package. And I installed/updated the PDT package from the Zend update site, using the Eclipse Install/Update dialog. There is no reason PDT should not work with MyEclipse.
And by the way…. The BIRT package gets the same error when trying to update the MyEclipse all in one distro.
Dennis
I don’t get it. Are you saying that we need to manage manual updates for a year, until MyEclipse gets a fix for this? That sounds borderline ridiculous. My subscription expires in 32 days. I will be giving a good hard look at the other options before I decide to renew, if this is the kind of response time we can expect from MyEclipse.
This packaging error will be fixed in 5.5, we have a milestone release for it coming out in a few weeks. I didn’t mean to communicate that we are going to sit on our hands while our users have broken installs. That’s not a good solution for anyone.
