Re: [cross-project-issues-dev] Eclipse Platform bundles usage of new language constructs and your plugins

[Andrew Obuchowicz]

Discussion with regards to
https://www.eclipse.org/lists/cross-project-issues-dev/msg17114.html
can be continued on https://bugs.eclipse.org/bugs/show_bug.cgi?id=552194.

PS: I apologize for not directly replying to the above email thread as I
wasn't subscribed to this mailing list at the time.

- Andrew Obuchowicz
___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Regarding updatation of N&N pages for Eclipse Installer and EPP w.r.t. Win10 Defender performance issue.

[Daniel Megert]

I am against to invest too much here. The message itself is clear and 
every user knows if he is on Windows 10 and uses Defender. Microsoft 
acknowledged the bug, especially it affects other things too, e.g. 
extracting files from archives can take very long.

Dani



From:   Rolf Theunissen 
To: Cross project issues 
Date:   16.10.2019 16:55
Subject:[EXTERNAL] Re: [cross-project-issues-dev] Regarding 
updatation of N&N pages for Eclipse Installer and EPP w.r.t. Win10 
Defender performance issue.
Sent by:cross-project-issues-dev-boun...@eclipse.org



Hi Mickael,

It must be possible to detect that Windows Defender is running and show a 
warning. At least IntelliJ IDEA and Android Studio's Project Marble should 
be doing similar, see 
https://blog.jetbrains.com/idea/2019/06/intellij-idea-2019-2-eap5-commit-from-local-changes-and-more/
 
(scroll down to "Windows Defender performance warning")

Regards,
Rolf

Op wo 16 okt. 2019 om 15:51 schreef Mickael Istria :
Hello Niraj,

Let's first assume that the vast majority of users don't read any 
documentation ;)
Can we detect that we are in the "slow" case at runtime? Would it make 
sense to open a popup on startup when we know we're in a bad state?

Cheers,
___
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://www.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://www.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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Fwd: Eclipse IDE in the brower

[Mickael Istria]

Sorry, it's "eclipse-broadway"

$ docker pull wsskeleton/eclipse-broadway
$ docker run wsskeleton/eclipse-broadway

On Thu, Oct 17, 2019 at 5:45 PM Fred Bricon  wrote:

> docker pull wsskeleton/broadway
> Using default tag: latest
> Error response from daemon: pull access denied for wsskeleton/broadway,
> repository does not exist or may require 'docker login': denied: requested
> access to the resource is denied
>
> On Thu, Oct 17, 2019 at 5:33 PM Mickael Istria  wrote:
>
>>
>>
>> -- Forwarded message -
>> From: Mickael Istria 
>> Date: Thu, Oct 17, 2019 at 5:30 PM
>> Subject: Eclipse IDE in the brower
>> To: Eclipse platform general developers list. ,
>> Discussions about the IDE 
>>
>>
>> Hi all,
>>
>> For some months, we've been working as a background task on making
>> Eclipse IDE and related stack cloud-friendlier and possible to integrate
>> efficiently in Che.
>> This is available thanks to GTK Broadway backend, that allows to render
>> GTK-based (so SWT-based) applications on a web browser. After a few tweaks
>> on Broadway side, this Eclipse IDE on Broadway story has reached a decent
>> level of usability and is IMO worth being demoed here and there.
>>
>> To try it
>> $ docker pull wsskeleton/broadway
>> $ docker run wsskeleton/broadway
>>
>> And there you are.
>> From here, you can demo Java projects, installation of plugins, edition
>> of diagrams (I usually install BPMN editor from SimRel site and verify it's
>> usable)...
>> There are of course limitations with this image with that: neither Maven
>> nor Gradle is installed in the Docker image, the environment is pretty
>> basic. But the value in the demo isn't really showing the image is complete
>> for serious Java project development, but more showing that integration of
>> Eclipse Platform/RCP-based solutions is possible in the Cloud and in the
>> Web.
>>
>> From here, the story is also to show Eclipse Platform (with extra plugins
>> or any RCP app) can be embedded as an editor into Eclipse Che, for people
>> who are interested in the cloud/collaboration/environment-as-a-service
>> value of Eclipse Che but still have high capital of specific features based
>> on Eclipse Platform that they want to remain able to use in a
>> *-as-a-service approach.
>> To demo this, the Eclipse IDE is available as an editor in Che 7, that
>> you can try on che.openshift.io for instance. You can tweak a Che
>> workspace and configure the editor to be Eclipse IDE instead of Theia and
>> remove a few other che plugins like jdt-ls which becomes irrelevant for
>> Eclipse IDE. This will use the Docker image mentioned above, will start the
>> Eclipse IDE as editor in Che, so you can show the same features and tell
>> users "sure, Eclipse IDE/Che can do that".
>>
>> Cheers,
>> --
>> Mickael Istria
>> Eclipse IDE 
>> developer, for Red Hat Developers 
>>
>>
>> --
>> Mickael Istria
>> Eclipse IDE 
>> developer, for Red Hat Developers 
>> ___
>> 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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
>
> --
> "Have you tried turning it off and on again" - The IT Crowd
> And if that fails, then http://goo.gl/tnBgH5
> ___
> 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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev



-- 
Mickael Istria
Eclipse IDE 
developer, for Red Hat Developers 
___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Fwd: Eclipse IDE in the brower

[Fred Bricon]

docker pull wsskeleton/broadway
Using default tag: latest
Error response from daemon: pull access denied for wsskeleton/broadway,
repository does not exist or may require 'docker login': denied: requested
access to the resource is denied

On Thu, Oct 17, 2019 at 5:33 PM Mickael Istria  wrote:

>
>
> -- Forwarded message -
> From: Mickael Istria 
> Date: Thu, Oct 17, 2019 at 5:30 PM
> Subject: Eclipse IDE in the brower
> To: Eclipse platform general developers list. ,
> Discussions about the IDE 
>
>
> Hi all,
>
> For some months, we've been working as a background task on making Eclipse
> IDE and related stack cloud-friendlier and possible to integrate
> efficiently in Che.
> This is available thanks to GTK Broadway backend, that allows to render
> GTK-based (so SWT-based) applications on a web browser. After a few tweaks
> on Broadway side, this Eclipse IDE on Broadway story has reached a decent
> level of usability and is IMO worth being demoed here and there.
>
> To try it
> $ docker pull wsskeleton/broadway
> $ docker run wsskeleton/broadway
>
> And there you are.
> From here, you can demo Java projects, installation of plugins, edition of
> diagrams (I usually install BPMN editor from SimRel site and verify it's
> usable)...
> There are of course limitations with this image with that: neither Maven
> nor Gradle is installed in the Docker image, the environment is pretty
> basic. But the value in the demo isn't really showing the image is complete
> for serious Java project development, but more showing that integration of
> Eclipse Platform/RCP-based solutions is possible in the Cloud and in the
> Web.
>
> From here, the story is also to show Eclipse Platform (with extra plugins
> or any RCP app) can be embedded as an editor into Eclipse Che, for people
> who are interested in the cloud/collaboration/environment-as-a-service
> value of Eclipse Che but still have high capital of specific features based
> on Eclipse Platform that they want to remain able to use in a
> *-as-a-service approach.
> To demo this, the Eclipse IDE is available as an editor in Che 7, that you
> can try on che.openshift.io for instance. You can tweak a Che workspace
> and configure the editor to be Eclipse IDE instead of Theia and remove a
> few other che plugins like jdt-ls which becomes irrelevant for Eclipse IDE.
> This will use the Docker image mentioned above, will start the Eclipse IDE
> as editor in Che, so you can show the same features and tell users "sure,
> Eclipse IDE/Che can do that".
>
> Cheers,
> --
> Mickael Istria
> Eclipse IDE 
> developer, for Red Hat Developers 
>
>
> --
> Mickael Istria
> Eclipse IDE 
> developer, for Red Hat Developers 
> ___
> 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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev



-- 
"Have you tried turning it off and on again" - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5
___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Fwd: Eclipse IDE in the brower

[Mickael Istria]

-- Forwarded message -
From: Mickael Istria 
Date: Thu, Oct 17, 2019 at 5:30 PM
Subject: Eclipse IDE in the brower
To: Eclipse platform general developers list. ,
Discussions about the IDE 


Hi all,

For some months, we've been working as a background task on making Eclipse
IDE and related stack cloud-friendlier and possible to integrate
efficiently in Che.
This is available thanks to GTK Broadway backend, that allows to render
GTK-based (so SWT-based) applications on a web browser. After a few tweaks
on Broadway side, this Eclipse IDE on Broadway story has reached a decent
level of usability and is IMO worth being demoed here and there.

To try it
$ docker pull wsskeleton/broadway
$ docker run wsskeleton/broadway

And there you are.
>From here, you can demo Java projects, installation of plugins, edition of
diagrams (I usually install BPMN editor from SimRel site and verify it's
usable)...
There are of course limitations with this image with that: neither Maven
nor Gradle is installed in the Docker image, the environment is pretty
basic. But the value in the demo isn't really showing the image is complete
for serious Java project development, but more showing that integration of
Eclipse Platform/RCP-based solutions is possible in the Cloud and in the
Web.

>From here, the story is also to show Eclipse Platform (with extra plugins
or any RCP app) can be embedded as an editor into Eclipse Che, for people
who are interested in the cloud/collaboration/environment-as-a-service
value of Eclipse Che but still have high capital of specific features based
on Eclipse Platform that they want to remain able to use in a
*-as-a-service approach.
To demo this, the Eclipse IDE is available as an editor in Che 7, that you
can try on che.openshift.io for instance. You can tweak a Che workspace and
configure the editor to be Eclipse IDE instead of Theia and remove a few
other che plugins like jdt-ls which becomes irrelevant for Eclipse IDE.
This will use the Docker image mentioned above, will start the Eclipse IDE
as editor in Che, so you can show the same features and tell users "sure,
Eclipse IDE/Che can do that".

Cheers,
-- 
Mickael Istria
Eclipse IDE 
developer, for Red Hat Developers 


-- 
Mickael Istria
Eclipse IDE 
developer, for Red Hat Developers 
___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse Platform bundles usage of new language constructs and your plugins

[Aleksandar Kurtakov]

On Thu, Oct 17, 2019 at 5:04 PM Ed Willink  wrote:

> Hi
>
> "move your bundle to newer BREE (highest BREE of deps)"
>
> Seems like a good candidate for a MANIFEST.MF warning.
>
I would highly appreciate if someone provide patches for that.


> Regards
>
> Ed Willink
>
> On 17/10/2019 14:14, Aleksandar Kurtakov wrote:
>
> Eclipse Platform starts using more and more new Java constructs (up to
> Java 8 for now) like try-with-resources, foreach and etc.
> Bundles have their minimal versions bumped whenever BREE has been bumped
> so one can have clear indicator of this change.
> This new features bring dependency on new classes like AutoClosable ( Java
> 1.7) , Iterable (Java 1.5) and probably others.
> If your bundles have BREE lower than the Platform bundle they depend on
> and you have JVM of that level configured in Eclipse errors like "The
> type java.lang.Iterable cannot be resolved. It is indirectly referenced
> from required .class files" could be shown.
> This is source level only issue if you try to build your old bundle
> against latest platform. People just using their prebuilt bundles won't
> face anything like this.
> Possible fixes for this issue are:
> * move your bundle to newer BREE (highest BREE of deps)
> * build against proper target platform containing the oldest versions of
> your deps you support
>
> I don't believe many people will face such issues but let's get this out
> for the sake of having it written somewhere.
>
> --
> Alexander Kurtakov
> Red Hat Eclipse Team
>
> ___
> cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, 
> visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_-8993089781911435847_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> ___
> 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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev



-- 
Alexander Kurtakov
Red Hat Eclipse Team
___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse Platform bundles usage of new language constructs and your plugins

[Ed Willink]

Hi

"move your bundle to newer BREE (highest BREE of deps)"

Seems like a good candidate for a MANIFEST.MF warning.

    Regards

        Ed Willink

On 17/10/2019 14:14, Aleksandar Kurtakov wrote:
Eclipse Platform starts using more and more new Java constructs (up to 
Java 8 for now) like try-with-resources, foreach and etc.
Bundles have their minimal versions bumped whenever BREE has been 
bumped so one can have clear indicator of this change.
This new features bring dependency on new classes like AutoClosable ( 
Java 1.7) , Iterable (Java 1.5) and probably others.
If your bundles have BREE lower than the Platform bundle they depend 
on and you have JVM of that level configured in Eclipse errors like 
"The type java.lang.Iterable cannot be resolved. It is indirectly 
referenced from required .class files" could be shown.
This is source level only issue if you try to build your old bundle 
against latest platform. People just using their prebuilt bundles 
won't face anything like this.

Possible fixes for this issue are:
* move your bundle to newer BREE (highest BREE of deps)
* build against proper target platform containing the oldest versions 
of your deps you support


I don't believe many people will face such issues but let's get this 
out for the sake of having it written somewhere.


--
Alexander Kurtakov
Red Hat Eclipse Team

___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev



--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Eclipse Platform bundles usage of new language constructs and your plugins

[Aleksandar Kurtakov]

Eclipse Platform starts using more and more new Java constructs (up to Java
8 for now) like try-with-resources, foreach and etc.
Bundles have their minimal versions bumped whenever BREE has been bumped so
one can have clear indicator of this change.
This new features bring dependency on new classes like AutoClosable ( Java
1.7) , Iterable (Java 1.5) and probably others.
If your bundles have BREE lower than the Platform bundle they depend on and
you have JVM of that level configured in Eclipse errors like "The type
java.lang.Iterable cannot be resolved. It is indirectly referenced from
required .class files" could be shown.
This is source level only issue if you try to build your old bundle against
latest platform. People just using their prebuilt bundles won't face
anything like this.
Possible fixes for this issue are:
* move your bundle to newer BREE (highest BREE of deps)
* build against proper target platform containing the oldest versions of
your deps you support

I don't believe many people will face such issues but let's get this out
for the sake of having it written somewhere.

-- 
Alexander Kurtakov
Red Hat Eclipse Team
___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Staging for SimRel 2019-12 Milestone 1 (M1) is complete

[Frederic Gurr]

Hi,

Since nobody asked for an extension, I'm declaring the staging
repository for 2019-12 M1 as complete and ready for EPP.

To confirm that everything works as expected, please test

=> http://download.eclipse.org/staging/2019-12/

This will become the official "M1 Simultaneous Milestone" on Friday.

=> http://download.eclipse.org/releases/2019-12/


Thanks for all contributions. Please remember to test early and often!


Regards,

Fred


-- 
Frederic Gurr
Release Engineer | Eclipse Foundation Europe GmbH

Annastr. 46, D-64673 Zwingenberg
Handelsregister: Darmstadt HRB 92821
Managing Directors: Ralph Mueller, Mike Milinkovich, Gaël Blondelle
___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev