Re: [cross-project-issues-dev] http or https reference to P2 repos: (was Re: Initialization for 2019-06)

[Michael Keppler]

Am 08.04.2019 um 18:58 schrieb Ed Willink:


I've raised https://bugs.eclipse.org/bugs/show_bug.cgi?id=546207
requesting the *.target support to give a warning for http:


Targets are only one of many places where that can be an issue. In my
company I use a checkstyle rule to flag http URLs (to some domains, not
all) in every file of every project as a build error.

Since the foundation has a Sonarqube server, maybe adding some regex
rule there might be an alternative to catch more occurrences?

Ciao, Michael

___
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 Passage intent to participate to SimRel 2019-06

[Alexander Fedorov]

Yes, the Eclipse Passage is the new participant, and this thread is an 
announcement of intent as stated below.


I created Gerrit https://git.eclipse.org/r/#/c/140202/ to add Eclipse 
Passage.


Thanks,
AF

08.04.2019 20:56, Wayne Beaton пишет:
I've created a "simrel" record for 2019-06 and have added Eclipse 
Passage (I also added Eclipse Project while I was there).


The opt-in deadline is M1 on April 19/2019. On (or shortly after) that 
date, I'll populate the page with the rest of the information for 
participating projects.


If you are a *new participant* in the simultaneous release, you are 
required to announce your intent on this mailing list.


If you are a *returning participant*, the "royal we" will determine 
your participation status based on your aggrcon file. Specifically, if 
it exists and is enabled on the M1 date, I'll assume that you're in.


The process requires that all projects that are "in" change their 
aggrcon file to indicate that they're paying attention. Please do this 
if you can. I will get my team to chase down the project teams who 
have not updated their aggrcon between the start of this cycle and the 
M1 date to verify their status.


Thanks,

Wayne

On Mon, Apr 8, 2019 at 1:48 AM Alexander Fedorov 
mailto:alexander.fedo...@arsysop.ru>> 
wrote:


Hello,

We would like Eclipse Passage to contribute to SimRel starting
from 2019-06.

The committer to represent the interests of the project is Alexander
Fedorov (alexander.fedo...@arsysop.ru
)

The release record is
https://projects.eclipse.org/projects/technology.passage/releases/0.5.0

Thanks in advance,
Passage 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



--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.


___
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] Eclipse Passage intent to participate to SimRel 2019-06

[Wayne Beaton]

I've created a "simrel" record for 2019-06 and have added Eclipse Passage
(I also added Eclipse Project while I was there).

The opt-in deadline is M1 on April 19/2019. On (or shortly after) that
date, I'll populate the page with the rest of the information for
participating projects.

If you are a *new participant* in the simultaneous release, you are
required to announce your intent on this mailing list.

If you are a *returning participant*, the "royal we" will determine your
participation status based on your aggrcon file. Specifically, if it exists
and is enabled on the M1 date, I'll assume that you're in.

The process requires that all projects that are "in" change their aggrcon
file to indicate that they're paying attention. Please do this if you can.
I will get my team to chase down the project teams who have not updated
their aggrcon between the start of this cycle and the M1 date to verify
their status.

Thanks,

Wayne

On Mon, Apr 8, 2019 at 1:48 AM Alexander Fedorov <
alexander.fedo...@arsysop.ru> wrote:

> Hello,
>
> We would like Eclipse Passage to contribute to SimRel starting from
> 2019-06.
>
> The committer to represent the interests of the project is Alexander
> Fedorov (alexander.fedo...@arsysop.ru)
>
> The release record is
> https://projects.eclipse.org/projects/technology.passage/releases/0.5.0
>
> Thanks in advance,
> Passage 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
>


-- 

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.
___
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] http or https reference to P2 repos: (was Re: Initialization for 2019-06)

[Ed Willink]

Hi Karsten

Ouch! I didn't follow all of 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=544852 but using http: 
seems pretty irresponsible.


I've raised https://bugs.eclipse.org/bugs/show_bug.cgi?id=546207 
requesting the *.target support to give a warning for http:


    Regards

        Ed Willink

On 08/04/2019 16:17, Karsten Thoms wrote:

Hi Ed,

I’m not sure if there is a general guideline, but we were addressed 
such an issue in project Xtext and make sure that we do not use 
anything in the build that is pulled through HTTP and fix the 
remaining places when we find some.


Read more in:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=544852
https://github.com/eclipse/xtext-xtend/issues/759

~Karsten

Am 08.04.2019 um 10:05 schrieb Ed Willink >:


Hi

Checking one of my builds, I find 12 repos in the *.target file all 
specified as http: e.g.


  includeMode="planner" includeSource="true" type="InstallableUnit">

    
    location="http://download.eclipse.org/eclipse/updates/I-builds"/>

  

Checking my Tycho log, I find e.g.

[INFO] Fetching p2.index 
fromhttp://download.eclipse.org/eclipse/updates/I-builds/
[INFO] Fetching p2.index 
fromhttp://download.eclipse.org/eclipse/updates/I-builds/
[INFO] Adding repositoryhttp://download.eclipse.org/eclipse/updates/I-builds
[INFO] Fetching p2.index 
fromhttps://download.eclipse.org/eclipse/updates/4.12-I-builds/
[INFO] Fetching p2.index 
fromhttps://download.eclipse.org/eclipse/updates/4.12-I-builds/

indicating that the platform is redirecting http: to https:

Is there an EF recommendation as to whether https: (more secure) or 
http: (less overhead) should be used?


    Regards

        Ed Willink

On 02/04/2019 12:38, Becker, Matthias wrote:

From my point of view not using SSL nowadays is a bug.
One should use SSL / HTTPs everywhere these days.
*From:*on behalf of 
Wim Jongman

*Reply-To:*Cross project issues
*Date:*Tuesday, 2. April 2019 at 13:24
*To:*Cross project issues
*Subject:*Re: [cross-project-issues-dev] Initialization for 2019-06
On Mon, Apr 1, 2019 at 5:14 PM Pierre-Charles David 
mailto:pierre-charles.da...@obeo.fr>> 
wrote:




https://download.eclipse.org/tools/orbit/downloads/latest-R/seems
to be
the correct location.

Thanks for that.
Is it in general not better to serve this content through HTTP to 
avoid SSL overhead and encryption of large files? I have no clue 
what this means in terms of speed but since these repos are extremly 
popular it might be significant.


___
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


 
	Virus-free.www.avast.com 
 



___
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



---
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

Re: [cross-project-issues-dev] http or https reference to P2 repos: (was Re: Initialization for 2019-06)

[Karsten Thoms]

Hi Ed,

I’m not sure if there is a general guideline, but we were addressed such an 
issue in project Xtext and make sure that we do not use anything in the build 
that is pulled through HTTP and fix the remaining places when we find some.

Read more in:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=544852 
 
https://github.com/eclipse/xtext-xtend/issues/759 
 

~Karsten

> Am 08.04.2019 um 10:05 schrieb Ed Willink :
> 
> Hi
> 
> Checking one of my builds, I find 12 repos in the *.target file all specified 
> as http: e.g. 
> 
>includeMode="planner" includeSource="true" type="InstallableUnit">
> 
>  location="http://download.eclipse.org/eclipse/updates/I-builds; 
> />
>   
> 
> Checking my Tycho log, I find e.g.
> 
> [INFO] Fetching p2.index from 
> http://download.eclipse.org/eclipse/updates/I-builds/ 
> 
> [INFO] Fetching p2.index from 
> http://download.eclipse.org/eclipse/updates/I-builds/ 
> 
> [INFO] Adding repository http://download.eclipse.org/eclipse/updates/I-builds 
> 
> [INFO] Fetching p2.index from 
> https://download.eclipse.org/eclipse/updates/4.12-I-builds/ 
> 
> [INFO] Fetching p2.index from 
> https://download.eclipse.org/eclipse/updates/4.12-I-builds/ 
> 
> indicating that the platform is redirecting http: to https:
> 
> Is there an EF recommendation as to whether https: (more secure) or http: 
> (less overhead) should be used?
> 
> Regards
> 
> Ed Willink
> 
> On 02/04/2019 12:38, Becker, Matthias wrote:
>> From my point of view not using SSL nowadays is a bug.
>> One should use SSL / HTTPs everywhere these days.
>>  
>> From:  
>>  on behalf of Wim 
>> Jongman  
>> Reply-To: Cross project issues  
>> 
>> Date: Tuesday, 2. April 2019 at 13:24
>> To: Cross project issues  
>> 
>> Subject: Re: [cross-project-issues-dev] Initialization for 2019-06
>>  
>>  
>>  
>> On Mon, Apr 1, 2019 at 5:14 PM Pierre-Charles David 
>> mailto:pierre-charles.da...@obeo.fr>> wrote:
>> 
>> 
>> https://download.eclipse.org/tools/orbit/downloads/latest-R/ 
>>  seems to be 
>> the correct location.
>>  
>> Thanks for that. 
>>  
>> Is it in general not better to serve this content through HTTP to avoid SSL 
>> overhead and encryption of large files? I have no clue what this means in 
>> terms of speed but since these repos are extremly popular it might be 
>> significant.
>>  
>>  
>>  
>>  
>> 
>> 
>> ___
>> 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 
>> 
>  
> 
> Virus-free. www.avast.com 
> 
>  
> ___
> 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] [eclipse-dev] JDT plans to hide & disable "new" index

[Lars Vogel]

+1, No need to keep unmaintained code around.

Thanks, Andrey for taking care of this.

Andrey Loskutov  schrieb am Mo., 8. Apr. 2019, 10:23:

> Hi all,
>
> Due the lack of resources for supporting the "new" JDT index with
> appropriate quality, JDT plans to hide & disable "new" JDT index.
>
> If nobody steps in, in two weeks from now we will remove the preference
> from UI which allows to enable it and automatically disable the preference
> if it was enabled.
> As a consequence, new users will be unable to turn the new index "on" and
> existing users will automatically use the old index if they switched before
> to the new one.
>
> See discussion on bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=544898
> and also linked issues with the new index for which we need help / lack
> resources.
>
> Here is the Wiki of the "new" index:
> https://wiki.eclipse.org/JDT_Core_Index_Programmer_Guide for those who
> wants to contribute.
> Attached screenshot shows the current preference (disabled by default).
>
> Kind regards,
> Andrey Loskutov
>
> Спасение утопающих - дело рук самих утопающих
>
> https://www.eclipse.org/user/aloskutov
> ___
> eclipse-dev mailing list
> eclipse-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/eclipse-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] JDT plans to hide & disable "new" index

[Andrey Loskutov]

Hi all,

Due the lack of resources for supporting the "new" JDT index with appropriate 
quality, JDT plans to hide & disable "new" JDT index.

If nobody steps in, in two weeks from now we will remove the preference from UI 
which allows to enable it and automatically disable the preference if it was 
enabled.
As a consequence, new users will be unable to turn the new index "on" and 
existing users will automatically use the old index if they switched before to 
the new one.

See discussion on bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=544898 and 
also linked issues with the new index for which we need help / lack resources.

Here is the Wiki of the "new" index: 
https://wiki.eclipse.org/JDT_Core_Index_Programmer_Guide for those who wants to 
contribute.
Attached screenshot shows the current preference (disabled by default).

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov
___
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] http or https reference to P2 repos: (was Re: Initialization for 2019-06)

[Ed Willink]

Hi

Checking one of my builds, I find 12 repos in the *.target file all 
specified as http: e.g.


  includeMode="planner" includeSource="true" type="InstallableUnit">

    
    location="http://download.eclipse.org/eclipse/updates/I-builds"/>

  

Checking my Tycho log, I find e.g.

[INFO] Fetching p2.index 
fromhttp://download.eclipse.org/eclipse/updates/I-builds/
[INFO] Fetching p2.index 
fromhttp://download.eclipse.org/eclipse/updates/I-builds/

[INFO] Adding repositoryhttp://download.eclipse.org/eclipse/updates/I-builds
[INFO] Fetching p2.index 
fromhttps://download.eclipse.org/eclipse/updates/4.12-I-builds/
[INFO] Fetching p2.index 
fromhttps://download.eclipse.org/eclipse/updates/4.12-I-builds/

indicating that the platform is redirecting http: to https:

Is there an EF recommendation as to whether https: (more secure) or 
http: (less overhead) should be used?


    Regards

        Ed Willink

On 02/04/2019 12:38, Becker, Matthias wrote:


From my point of view not using SSL nowadays is a bug.

One should use SSL / HTTPs everywhere these days.

*From: * on behalf of 
Wim Jongman 

*Reply-To: *Cross project issues 
*Date: *Tuesday, 2. April 2019 at 13:24
*To: *Cross project issues 
*Subject: *Re: [cross-project-issues-dev] Initialization for 2019-06

On Mon, Apr 1, 2019 at 5:14 PM Pierre-Charles David 
mailto:pierre-charles.da...@obeo.fr>> 
wrote:




https://download.eclipse.org/tools/orbit/downloads/latest-R/ seems
to be
the correct location.

Thanks for that.

Is it in general not better to serve this content through HTTP to 
avoid SSL overhead and encryption of large files? I have no clue what 
this means in terms of speed but since these repos are extremly 
popular it might be significant.



___
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