Unfortunately it's not all very transparent what exactly is going on:
https://github.com/eclipse/pdt/issues/95
And I have not personally dug deeper, although I should, time permitting...
On 16.11.2022 06:52, Aleksandar Kurtakov wrote:
Where does this PDT work happen? I look at
Where does this PDT work happen? I look at https://github.com/eclipse/pdt
and see nothing. I don't install PDT anymore due to dltk state and if there
is some nightly available to test new builds I would happily use it.
On Tue, Nov 15, 2022 at 9:59 PM Ed Merks wrote:
> Jonah,
>
> I believe that
On Tue, 15 Nov 2022 at 14:59, Ed Merks wrote:
> Jonah,
>
> I believe that PDT is working toward PHP 8 support and will remove DLTK
> dependencies as part of the process; I don't know the ETA though I'd
> recommend we let it go one more round given that PDT updates have a much
> narrower
Jonah,
I believe that PDT is working toward PHP 8 support and will remove DLTK
dependencies as part of the process; I don't know the ETA though
I'd recommend we let it go one more round given that PDT updates have a
much narrower impact.
I'll see if I can get PGP signing of features
On Tue, 15 Nov 2022 at 08:32, Aleksandar Kurtakov
wrote:
>
>
> On Mon, Nov 14, 2022 at 2:44 PM Ed Merks wrote:
>
>>
>>- *org.eclipse.dltk*
>>
>>
> As probably I'm the last person that has touched dltk, I have to share
> that the chances for a rebuild are zero as it looks like even the ci is
~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com
On Tue, 15 Nov 2022 at 13:58, Lorenzo Bettini
wrote:
>
> > * *org.eclipse.emf.parsley*
>
> Hi
>
> Concerning Parsley, this would require to perform a new release, but I
> guess we're late to start the release procedure paperwork, aren't we?
On 14/11/22 13:43, Ed Merks wrote:
*These projects need to do new builds*:
* *org.eclipse.acceleo*
* *org.eclipse.bpmn2*
* *org.eclipse.dltk*
* *org.eclipse.ecf*
* *org.eclipse.eef*
* *org.eclipse.emf.edapt*
* *org.eclipse.emf.parsley*
Hi
Concerning Parsley, this would require
Le 14/11/2022 à 13:43, Ed Merks a écrit :
*These projects need to do new builds*:
* *org.eclipse.acceleo*
* *org.eclipse.bpmn2*
* *org.eclipse.dltk*
* *org.eclipse.ecf*
* *org.eclipse.eef*
* *org.eclipse.emf.edapt*
* *org.eclipse.emf.parsley*
* *org.eclipse.fx*
*
A mistake from my end... Thanks for catching that so quickly.
I've updated my simrel contribution to
https://download.eclipse.org/acceleo/updates/milestones/3.7/S202211151354 .
Le 15/11/2022 à 14:30, Ed Merks a écrit :
Laurent,
It looks like this build was literally done with no signing.
On Mon, Nov 14, 2022 at 2:44 PM Ed Merks wrote:
> Recent versions of Java, including the most recent Java 17 release, now
> consider some jar-signed bundles to be unsigned. This affects all bundles
> and features signed between January 1, 2019 and April 14, 2022 with the
> Eclipse certificate
Laurent,
It looks like this build was literally done with no signing. One should
find files META-INF folder but there's on the MANIFEST.MF
https://download.eclipse.org/acceleo/updates/milestones/3.7/S202211151309/features/org.eclipse.acceleo.doc_3.7.12.202211151309.jar
On 15.11.2022 14:24,
Hi Ed,
Acceleo 3.7.12 built using the latest Orbit I build
(https://download.eclipse.org/tools/orbit/downloads/drops/I20221112145035)
and contributed to the simrel through
https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/196955 .
Please let me know if this doesn't solve the
Attention: The JobManager implementation was changed!
The old JobMangager implementation notified IJobChangeListener about various
IJobChangeEvent without strict order in various threads. For example
scheduled() was called in a thread that did call schedule() on a job while
done() was normally
13 matches
Mail list logo
