To be more helpful, the following bugzilla has some useful references on how to solve (on some servers, at least for the "php" case) ... if indeed its related to server settings.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=281179 See following bug for a similar case (but involved only .zip in file name that should have been treated as text files so not directly related). https://bugs.eclipse.org/bugs/show_bug.cgi?id=317393 So if your product has php, xml, html, jpeg or similar thing in the name, you should check exact contents of what was fetched. It might just be some html text with an error message that is stuffed in the jar file. Or ... it could be totally something else :) From: David M Williams/Raleigh/i...@ibmus To: P2 developer discussions <[email protected]> Date: 09/09/2010 01:07 PM Subject: Re: [p2-dev] p2 repository question Sent by: [email protected] I think there are some web server settings that can effect how jar files are served up. In the past, I seem to recall some issues on some servers where files with ".php" anywhere in the file name would routed through some PHP filters, and attempt to be served up as a php file, hence some jar named something like "org.eclipse.php.jar_versionID" would end up serving up some HTML error message file that said something related to "invalid php file". Perhaps its something like that? And all P2 knows is that the fetch of the jar failed. Just guessing. From: Pascal Rapicault <[email protected]> To: P2 developer discussions <[email protected]> Date: 09/09/2010 12:51 PM Subject: Re: [p2-dev] p2 repository question Sent by: [email protected] Nothing specific about IIS. p2 is just a bunch of files. Do you have anything setup to protect from attacks? p2 is looking for a given set of files one by one (w.o knowing whether or not they exist). I'm thinking that maybe after a while the IP would be blocked. HTH On 2010-09-09, at 11:18 AM, Rob Cavallo wrote: Hi all, Is there anything particular about a repository as I've been able to successfully update an exported product when it's being served up by Apache but not IIS. When using IIS, the update fails prior to completion with an error "artifact not found" for the product itself after it's been fetched. Thanks, Rob _______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev _______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev _______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
