Thanks for mentioning it... it is fixed now with the following children in
the EPP Photon repo:
<children size='3'>
<child location='M3'/>
<child location='M4'/>
<child location='M5'/>
</children>
Regards,
Markus
On 12 February 2018 at 09:30, Ed Merks <ed.me...@gmail.com> wrote:
> I noticed that the EPP Photon composite repo is inconsistent right now. I
> noticed this because this familiar problem is cropping up every time I try
> to do completion in JDT:
>
> java.lang.NoSuchMethodError: org.eclipse.jface.internal.tex
> t.html.HTMLPrinter.insertPageProlog(Ljava/lang/StringBuilder
> ;ILorg/eclipse/swt/graphics/RGB;Lorg/eclipse/swt/graphics/
> RGB;Ljava/lang/String;)V
> at org.eclipse.jdt.internal.ui.text.java.AbstractJavaCompletion
> Proposal.getAdditionalProposalInfo(AbstractJavaCompletionProposal.
> java:610)
> at org.eclipse.jface.text.contentassist.AdditionalInfoControlle
> r$Timer$2$1.run(AdditionalInfoController.java:113)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
>
> The file /home/data/httpd/download.eclipse.org/technology/epp/package
> s/photon/compositeContent.jar does not contain a reference to
> /home/data/httpd/download.eclipse.org/technology/epp/packages/photon/M5/
> so when you try to install Photon M5 from the release train composite you
> actually end up with Photon M4 which seems to cause some inconsistent of
> JDT and JFace Text.
>
> Note that I see the following in /home/data/httpd/download.ecli
> pse.org/releases/photon/:
>
> <?xml version='1.0' encoding='UTF-8'?>
> <?compositeMetadataRepository version='1.0.0'?>
> <repository name='Eclipse Repository' type='org.eclipse.equinox.inte
> rnal.p2.metadata.repository.CompositeMetadataRepository' version='1.0.0'>
> <properties size='3'>
> <property name='p2.timestamp' value='1313779613118'/>
> <property name='p2.compressed' value='true'/>
> <property name='p2.atomic.composite.loading' value='true'/>
> </properties>
> <children size='3'>
> <child location='http://download.eclipse.org/technology/epp/package
> s/photon/'/>
> <child location='201802021000' />
> <child location='201712151000' />
> <child location='201711031000' />
> </children>
> </repository>
>
> So while it might point at M5 via 201802021000, it points at an EPP
> composite that does not include M5 packages so you'll definitely end up
> with M4 packages and whatever those requirements decide to pull in, which
> seems to be a mixture of M4 and M5.
>
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
