| Re: [cross-project-issues-dev] Update site content cannot be displayed in IE11 |
Hi Andreas,
Thank you for the script, we've applied it.
I cannot understand why this script isn't generated by Eclipse automatically
when you create a build. There is the problem that the default update site
includes invalid script, so every project should resolve this problem on
their own way.
Let's recommend to use this script as the standard output for the build
process. Who else is interested?
Best regards,
Igor Vinnykov
Subversive Team
-----Original Message-----
From: cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Andreas
Sewe
Sent: Thursday, May 22, 2014 1:01 PM
To: cross-project-issues-dev@xxxxxxxxxxx
Subject: Re: [cross-project-issues-dev] Update site content cannot be
displayed in IE11
Hi,
> I don't know if there is a recommended format, but my 2 cents are:
>
> From a release engineer's point of view, I'd rather generate the
index.html
> statically as part of the build than rely on runtime _javascript_.
Bug 424691 may be of interest. At Code Recommenders, we use the solution
presented there to include an index.php [1] in our update sites, which
then does the content listing (download.eclipse.org allows PHP). So this
solution falls somewhere between generating the list at build time and
generating it in the user's browser using _javascript_.
If there is a desire to establish a "recommended format", I think the
CBI project should offer something akin to our repository-resources
artifact which can be easily included in CBI (= Tycho) builds.
Hope this helps.
Andreas
[1]
<https://git.eclipse.org/c/recommenders/org.eclipse.recommenders.git/tree/re
leng/repository-resources/resources/index.php.vm>
--
Codetrails UG (haftungsbeschränkt)
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Mobile: +49-170-811-3791
http://www.codetrails.com/
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev