- This topic has 4 replies, 2 voices, and was last updated 13 years, 2 months ago by
.
-
Posts
-
I’m sorry I failed to get my message across in the earlier post https://www.genuitec.com/forums/topic/i-cannot-download-my-plugin-using-myeclipse/
I am the developer for the plugin at SoftwareFM (hence the username), and am trying to get my plugin to work with MyEclipse. The reason that the website says that we have a problem with MyEclipse is that I put the message there, and this post is my attempt to fix the issue.
It very much seems to be a MyEclipse problem as I can install the plugin on many different versions of Helios and Indigo, on Macs / Windows and Linux. However when I use the (non standard) installer on MyEclipse, I get an error every time. The error is around the file length of the jars (see the earlier post for full details). As the update site was generated using the standard eclipse update manager project, I had very little influence over the characteristics of the jar.
As I stated in the earlier post, I have spent some time googling to find the cause. However there are only a handful of errors mentioned, and I was unable to determine the cause. I have of course checked that the file is downloadable / not corrupted and works in every other version of Eclipse that I can get my hands on. The various operating systems that I have tried moving it onto all confirmed that the file length was the expected value, and I am unable to work out why MyEclipse thinks the file length is wrong.
I am happy to modify the plugin to make it compatible with the MyEclipse requirements, but I need to know what they are. I would also appreciate understanding what the error message meant.
I don’t know MyEclipse well enough to know if the source code is available. If you are unable to help could you perhaps point me at roughly where in the source code the problem might be, so that I can fix this bug.
Thanks again for any help
Phil
Phil,
I’m investigating this issue myself.
In the meanwhile, can you tell me exactly how you exported the plugins / features and generated the update site? For example, you could have exported a set of features and then run the P2 generator on the exported directory, or, you could have used a product export or some other technique. Knowing precisely how your site was generated would help a great deal.
@Support-Brian wrote:
Phil,
I’m investigating this issue myself.
In the meanwhile, can you tell me exactly how you exported the plugins / features and generated the update site? For example, you could have exported a set of features and then run the P2 generator on the exported directory, or, you could have used a product export or some other technique. Knowing precisely how your site was generated would help a great deal.
Thank you for your help Brian. If I can help in any way please let me know. This is quite high priority for me, so I am happy to invest quite a lot of time in fixing it.
My release process uses the standard eclipse tools. The code for the feature project and the update project are available at https://github.com/phil-rice/SoftwareFm.
-
I update the version number in the feature project
I modify the site.xml to include the new feature version
I generate the update site from an eclipse update site project. I used the eclipse button “build all” to build the web site. This starts with a site.xml file, and produces all the files in the same folder.
I check that the update site is usable from a local archive using Helios and Indigo, on a PC and on a Mac. I also check the vanilla installation and the upgrade path from the last install
I use filezilla to copy the files to the update site. As it happens I copy the plugin and feature files first, then copy the others. In the future I’ll be using a symbolic link to flip over between versions, but for the moment a few second down time is OK.
I check that the update site is usable from Helios and Indigo, and ask a couple of other people to download it and check itI am of course modifying the release process to include checking on MyEclipse.
The update site is a standard Apache server. We are currently playing games with different servers to see if it makes any difference, and it appears not to.
I have added a second installation option (using the zip of the update site). Instructions are http://www.softwarefm.org/pages/downloads/install-using-archive-file.php
I am always nervous in support calls to give potentially Toxic information, but my experiments have included the following:
- Pointing MyEclipse at the update site in a local folder structure: no problems
Pointing MyEclipse at a zip file in a local folder structure: no problems
Pointing MyEclipse at zip file on the internet: no problemsGiven that our webserver is an Apache server we are scratching our heads at this.
We have found the issue. It was in fact with the apache server.
We were using a module called mod_deflate, to improve the performance of the update site. While this works with Helios and Indigo, it appears not to work with MyEclipse
We modified the http.conf file to:
<Location />
# Insert filter
BrowserMatch ^Jakarta Commons-HttpClient/3 no-gzip
SetOutputFilter DEFLATE
# Don’t compress jar / zip / gif files
SetEnvIfNoCase Request_URI \
\.(?:gif|zip|jar)$ no-gzip dont-vary
# Make sure proxies don’t deliver the wrong content
Header append Vary User-Agent env=!dont-vary
</Location>Thanks for your time
Phil
Phil,
Thank you for following up and posting the cause here; that would have been a very hard problem for me to track down.
I’ll also look into why the mod causes issues with MyEclipse and what we can do to fix it; at the very least we know where to look if other third party plugins face similar issues.
Thanks again.
