Re: [cross-project-issues-dev] Open Software without Free Trade.

[Mike Milinkovich]

On 2022-03-01 10:15 a.m., jkubitz-ecli...@gmx.de wrote:


Mike,

i fully agree that anyof geopolitical silos is failure. Same to 
sports: it is a failure that Russia will not participate in this 
coming events. But that is a lesser harm then the murder of people. 
It’s a signal.


We the people who want peaceful and prosperous future must not wait 
for laws. Someday there may be no more tomorrow for some (or all) of 
us. We need to take action before that happens. Now.


What about changing the splash screen (bug 575781) to a message (for 
example Ukraine flag blue + yellow).



Perhaps. But ultimately that is a project decision.

In the meantime: 
https://eclipse-foundation.blog/2022/03/01/the-eclipse-foundation-standwithukraine/



Jörg

*Von:* cross-project-issues-dev 
 *Im Auftrag von *Mike 
Milinkovich

*Gesendet:* Dienstag, 1. März 2022 15:21
*An:* cross-project-issues-dev@eclipse.org
*Betreff:* Re: [cross-project-issues-dev] Open Software without Free 
Trade.


Jörg,

Factually, what you are implying about the EPL is incorrect. Like the 
GPL the EPL is also a free software license, as is every other license 
used by Eclipse Foundation projects. And the 4 freedoms referenced by 
Boris fully apply to every project here. Implementing what you are 
suggesting would be close to impossible.


That said, the Eclipse Foundation obeys every law and regulation that 
applies to it. For example, we follow all export controls that apply 
to us under US and European law. If the current conflict results in 
additional regulations we will apply them as well. That is not the 
case as of this moment.


The Eclipse Foundation stewards a global community that embraces 
technologies from all countries. The free flow of openly licensed 
technologies drives innovation in all sectors of the economy today. 
For a peaceful and prosperous future we want to promote the lawful use 
of free and open source software from around the world. The creation 
of geopolitical silos within the open source community would be 
failure IMHO.


*Mike Milinkovich*

*Executive Director | **Eclipse Foundation AISBL*

Twitter:@mmilinkov

On 2022-03-01 8:41 a.m., jkubitz-ecli...@gmx.de wrote:

Dear Boris,

Note that eclipse is not under GNU but EPL licensed. Therefore it
is **not** public domain.

Yours

Jörg

*Von:* cross-project-issues-dev

<mailto:cross-project-issues-dev-boun...@eclipse.org> *Im Auftrag
von *Boris Baldassari
*Gesendet:* Dienstag, 1. März 2022 13:53
*An:* Cross project issues 
<mailto:cross-project-issues-dev@eclipse.org>
*Betreff:* Re: [cross-project-issues-dev] Open Software without
Free Trade.

Dear Jörg,

Note: this is my personal opinion and does not engage anyone else.

Whatever we think about the current situation, the 4 freedoms that
define free/libre open source software absolutely forbid us, or
anybody, to do that.

[1] https://en.wikipedia.org/wiki/The_Free_Software_Definition
<https://en.wikipedia.org/wiki/The_Free_Software_Definition>

Cheers,

--

boris



___

cross-project-issues-dev mailing list

cross-project-issues-dev@eclipse.org

To unsubscribe from this list, 
visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

--


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, 
visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

--

*Mike Milinkovich*

*Executive Director | **Eclipse Foundation AISBL*

Twitter:@mmilinkov
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Sad News

[Mike Milinkovich]

Pradeep,

This is so sad. Our deepest condolences to Kit's family and colleagues.

On 2022-03-01 10:42 a.m., Pradeep Balachandran wrote:


Dear Friends,

I have a sad news to share.

Kit Lo, Technical Lead for IBM Eclipse SDK, based out of IBM RTP lab, 
passed away on Saturday, Feb 26th. He was on a routine run on Saturday 
and collapsed on the way. Kit has been with IBM for 32+ years, working 
in various roles and different teams. In the past decade, Kit was the 
lead for Translation / Globalization efforts across various products. 
About 5 years ago, Kit took up the IES Technical Lead role. Kit was a 
very hard worker, continuous learner and always willing to go the 
extra mile to help those in need. Kit was also very active in Eclipse 
Open Source Community. He was the co-lead for Eclipse Babel project 
(community driven translation of strings in Eclipse distribution) and 
in the past year, he also took up the additional role of Eclipse IDE 
Release Engineer.


We in the Eclipse team in IBM, are still trying to come to terms with 
the fact that Kit is no longer with us. Kit was a great friend, mentor 
and guide for those who worked closely with him. We are lucky to have 
worked with him. Kit will be sorely missed.


Pradeep


--

*Mike Milinkovich*

*Executive Director | **Eclipse Foundation AISBL*

Twitter:@mmilinkov
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Open Software without Free Trade.

[Mike Milinkovich]

Jörg,

Factually, what you are implying about the EPL is incorrect. Like the 
GPL the EPL is also a free software license, as is every other license 
used by Eclipse Foundation projects. And the 4 freedoms referenced by 
Boris fully apply to every project here. Implementing what you are 
suggesting would be close to impossible.


That said, the Eclipse Foundation obeys every law and regulation that 
applies to it. For example, we follow all export controls that apply to 
us under US and European law. If the current conflict results in 
additional regulations we will apply them as well. That is not the case 
as of this moment.


The Eclipse Foundation stewards a global community that embraces 
technologies from all countries. The free flow of openly licensed 
technologies drives innovation in all sectors of the economy today. For 
a peaceful and prosperous future we want to promote the lawful use of 
free and open source software from around the world. The creation of 
geopolitical silos within the open source community would be failure IMHO.


*Mike Milinkovich*

*Executive Director | **Eclipse Foundation AISBL*

Twitter:@mmilinkov

On 2022-03-01 8:41 a.m., jkubitz-ecli...@gmx.de wrote:


Dear Boris,

Note that eclipse is not under GNU but EPL licensed. Therefore it is 
**not** public domain.


Yours

Jörg

*Von:* cross-project-issues-dev 
 *Im Auftrag von *Boris 
Baldassari

*Gesendet:* Dienstag, 1. März 2022 13:53
*An:* Cross project issues 
*Betreff:* Re: [cross-project-issues-dev] Open Software without Free 
Trade.


Dear Jörg,

Note: this is my personal opinion and does not engage anyone else.

Whatever we think about the current situation, the 4 freedoms that 
define free/libre open source software absolutely forbid us, or 
anybody, to do that.


[1] https://en.wikipedia.org/wiki/The_Free_Software_Definition 
<https://en.wikipedia.org/wiki/The_Free_Software_Definition>


Cheers,

--

boris


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, 
visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

--___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Sad News

[Mike Milinkovich]

All,

It is with a heavy heart that I must inform you that our friend and 
colleague Dani Megert passed away last Friday evening. Dani's death was 
not related to COVID-19.


Dani had been involved with the Eclipse community before it was even 
called Eclipse. He was one of the original Object Technology 
International team that created what became known as the Eclipse IDE. 
After OTI became part of IBM he stayed with the project with 
ever-increasing responsibilities: leader of JDT and Platform Text 
projects, Eclipse Platform Lead, Eclipse PMC member, and JDT project 
leader. More recently he stepped up his involvement with the Eclipse 
Foundation's governance and has been an elected member of the Board 
since 2016, representing our committers. Dani was a tireless advocate 
for our projects and committers in our Board discussions. Within IBM he 
was a leader, a manager, but most importantly a mentor, to the Eclipse 
IDE development team.


In recognition of Dani's commitment to the Eclipse community, he was 
awarded the Eclipse Lifetime Award in 2016.


It is impossible to over-state the contributions that Dani made to the 
Eclipse IDE platform and its community. Millions of developers around 
the world have benefited from his work. He will be deeply missed by all 
who knew him.


--

*Mike Milinkovich*

*Executive Director | **Eclipse Foundation, Inc.*

mike.milinkov...@eclipse-foundation.org

@mmilinkov

+1.613.220.3223 (m)

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Java 11 recommendations

[Mike Milinkovich]

There is no policy on the Java version. But I don’t understand why anyone would 
elect to use Java under the OTN license when you could also use it under the 
GPL+CE? 

Mike Milinkovich
mike.milinkov...@eclipse-foundation.org
(m) +1.613.220.3223

> On Dec 11, 2018, at 12:10 PM, Ed Willink  wrote:
> 
> Hi
> 
> Is there an EF policy on what Java 11 should be used?
> 
> https://www.computerweekly.com/opinion/Beware-of-Oracles-developer-Trojan
> 
> suggests that the Oracle JDK that I have used in the past may no longer be 
> appropriate.
> 
> Please advise.
> 
> Regards
> 
> Ed Willink
> 
> 
> 
> ---
> 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 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] Anonymisation of public data

[Mike Milinkovich]

The Eclipse Foundation would prefer to *not* be responsible for securely 
retaining such keys. If an interesting pattern was ever uncovered, I 
think that we could analyze the original data to discover the relevant 
authors using the original available data. And I cannot really imagine 
providing researchers direct access to interesting contributors 
discovered by analyzing anonymized data, as I am certain that would 
violate our privacy policies.


In short, IMO the privacy risk of maintaining those keys outweighs any 
potential advantages of retaining them. My 2c :)


On 2018-04-26 3:02 AM, Mickael Istria wrote:

Hi Boris,

The basic idea is to simply replace all identifiers with
asymmetrically encrypted strings, so all IDs have the same
ciphered result. RSA is used for the encryption, and the private
key is thrown away once the encoding is done, making it impossible
(according to common encryption standards) to retrieve the
original string.



Is this a requirement, at this point, to make it impossible to 
retrieve the original stream for anyone?
I understand that the providing anonymous dataset is interesting as 
you explained, but what couldn't you or Eclipse Foundation keep the 
private RSA key safely to decode the id if you find some unexpected 
patterns? If you make id anonymous and find a set of id which have a 
strange correlation and that you'd like to explain, wouldn't it be 
helpful to decode the id and find out who are the individuals behind 
it to better understand the cause of the correlation or even set up 
chats with selected contributors to better understand their practices?
I have the impression there could be value in keeping ability to 
decode strings, while I don't think fully discarding the key is much 
safer than keeping it in a safe place (like an EF server with strong 
restriction on who can access the key).


My 2c (or maybe even less ;)
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/> 
developer, for Red Hat Developers <https://developers.redhat.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://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



--
Mike Milinkovich
mike.milinkov...@eclipse-foundation.org
(m) +1.613.220.3223

___
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

Re: [cross-project-issues-dev] Fwd: JDK 9: General Availability

[Mike Milinkovich]

On 2017-09-21 3:54 PM, Fred Bricon wrote:
It says "Builds for platforms other than Linux/x64 will be published 
at a later date.".

I guess they have their reasons :-)

On Thu, Sep 21, 2017 at 3:51 PM, Daniel Megert 
mailto:daniel_meg...@ch.ibm.com>> wrote:


Yeah, I expected that, but why not on http://jdk.java.net/9/`?

Fred is correct. When Oracle made the announcement it said that they 
would start with Linux and add Windows and Mac later. So this was expected.


--
Mike Milinkovich
mike.milinkov...@eclipse-foundation.org
(m) +1.613.220.3223

EclipseCon Europe 2017 <http://www.eclipsecon.org/europe2017>
___
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] Fwd: JDK 9: General Availability

[Mike Milinkovich]

Just FYI

 Forwarded Message 
Subject:JDK 9: General Availability
Date:   Thu, 21 Sep 2017 12:21:33 -0700 (PDT)
From:   mark.reinh...@oracle.com
Reply-To:   disc...@openjdk.java.net
To: annou...@openjdk.java.net



I'm pleased -- nay, thrilled! -- to announce that JDK 9 is now Generally
Available.  We've identified no P1 bugs since we promoted build 181 seven
weeks ago so that is the official GA release, ready for production use.

GPL'd binaries from Oracle are available here:

  http://jdk.java.net/9

(There are links on that page to Oracle's commercial binaries for those
who are interested.)  I'm sure that binaries from other implementors will
be available in short order.

The key feature of this release is, of course, Project Jigsaw, about
which I've written a bit more over on my blog:

  https://mreinhold.org/blog/jigsaw-complete

Jigsaw is not, however, the only feature!  There are many other excellent
additions and improvements including, but not limited to:

  Improved Process API   http://openjdk.java.net/jeps/102
  HTTP/2 Client (incubating) http://openjdk.java.net/jeps/110
  Variable Handles   http://openjdk.java.net/jeps/193
  JShell Read-Eval-Print Loophttp://openjdk.java.net/jeps/222
  Javadoc Search http://openjdk.java.net/jeps/225
  Linux/AArch64 Port http://openjdk.java.net/jeps/237
  Marlin Graphics Renderer   http://openjdk.java.net/jeps/265
  Collection Factories   http://openjdk.java.net/jeps/269
  Enhanced Deprecation   http://openjdk.java.net/jeps/277
  Linux/s390x Port   http://openjdk.java.net/jeps/294
  Ahead-of-Time Compilation  http://openjdk.java.net/jeps/295

The complete list of features is on the JDK 9 Project page:

  http://openjdk.java.net/projects/jdk9/

Thank you to everyone who contributed to JDK 9, whether directly or
indirectly.  It's been a long road, but it will have been worth it.
This release lays a strong foundation for the future of Java.

- Mark

___
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] New Java Release Cycle

[Mike Milinkovich]

All,

FYI, it is now official and public that it is the intent of the Java 
platform team to move to a model where there will be a new Java release 
every 6 months.


I would expect that this will have a significant impact on the Eclipse 
simultaneous release cycle and processes.


From 

https://jcp.org/aboutJava/communityprocess/ec-public/materials/2017-08-15/JCP-EC-Minutes-August-2017.html

   *OpenJDK and the JCP*

   Heather reported that the OpenJDK Working Group met on August 8. The
   summary is published on the EC Community page. Brian (Goetz)
   summarized the meeting for the larger EC; he reiterated _*the desire
   of OpenJDK to move faster - they would like to move to a 6 month
   release cadence with releases in March and September with the next
   release of Java SE in early 2018.*_ Volker asked why we want more
   frequent Java releases, stating concern for long term support of
   Java. Steve suggested that support is an important point, but not
   relevant to JCP discussion, Brian reviewed the plan in the short
   term of the next release of Java to streamline stages and provide
   continuous delivery of specification work-in-progress. Simon asked
   about research on the decision to evolve Java more rapidly. Georges
   (Saab) explained that there have been many discussions in the
   community, and in order to stay relevant and moving forward to meet
   needs of the community, we need to be able to adjust to changes of
   direction and where things are going. Amelia asked about conducting
   surveys. Heather pointed out that Brian frequently conducts polls
   and surveys. We should promote and communicate them as they occur.
   Brian concurred that these have been valuable tools for input with
   thousands of replies. Mike DeNicola expressed concerns about
   ensuring the quality of the releases. Brian stated that the quality
   will be ensured through the specification process for vetting them,
   and revamping the deprecation process in Java SE 9. Oracle plans to
   file the Java 10 JSR in September, or as soon as practical, and have
   a December freeze date for the release. The OpenJDK Working Group
   will bring the discussions thus far into the JCP.Next Working Group.
   Separate meetings can resume again if needed.

--
Mike Milinkovich
mike.milinkov...@eclipse-foundation.org
(m) +1.613.220.3223

EclipseCon Europe 2017 <http://www.eclipsecon.org/europe2017>
___
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

Re: [cross-project-issues-dev] Bugzilla down? (Internal Server Error)

[Mike Milinkovich]

Yup. 

Thank you Denis for getting up at 2:00am to kick the server. 

Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223

> On Feb 8, 2017, at 10:21 AM, Remy Suen  wrote:
> 
> It was down for me too but seems back up. Connecting fine from Japan.
> 
> Regards,
> Remy
> 
>> On Wed, Feb 8, 2017 at 6:09 PM, Andrey Loskutov  wrote:
>> Yes, I get error 500 too.
>> 
>>> Am 08.02.2017 um 10:04 schrieb Andreas Sewe:
>>> 
>>> Hi,
>>> 
>>> Bugzilla seems to be down for me; I get an Internal Server Error. Is
>>> anyone else seeing this problem?
>>> 
>>> Best wishes,
>>> 
>>> Andreas
>>> 
>>> 
>>> 
>>> ___
>>> 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
>>> 
>> 
>> --
>> Kind regards,
>> Andrey Loskutov
>> 
>> http://google.com/+AndreyLoskutov
>> 
>> ___
>> 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
___
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

Re: [cross-project-issues-dev] Bugzilla is down?

[Mike Milinkovich]

On 2016-11-14 9:29 AM, SCHNEKENBURGER Remi 211865 wrote:


Hi,

Bugzilla is also down for me since this morning, wiki and other 
Eclipse sites seem to be OK however. (Suburbs of Paris  ;) )




It works for medowntown Paris. And [1] reports that it is working as 
well.

[1] http://downforeveryoneorjustme.com/bugs.eclipse.org


Regards,

Rémi

---

Rémi SCHNEKENBURGER

+33 (0)1 69 08 48 48

CEA Saclay Nano-INNOV

Institut CARNOT CEA LIST

Description : PapyrusLogo_SmallFormatwww.eclipse.org/papyrus 
<http://www.eclipse.org/papyrus>


*De :*cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] *De la part de* 
Christian Campo

*Envoyé :* lundi 14 novembre 2016 09:17
*À :* Cross project issues 
*Objet :* Re: [cross-project-issues-dev] Bugzilla is down?

Interesting enough the downforeveryoneorjustme changes its status 
nearly each and every time I call the page from UP to DOWN


*Von: *<mailto:cross-project-issues-dev-boun...@eclipse.org>> on behalf of 
Mickael Istria mailto:mist...@redhat.com>>
*Antworten an: *Cross issues <mailto:cross-project-issues-dev@eclipse.org>>

*Datum: *Montag, 14. November 2016 um 09:11
*An: *Cross issues <mailto:cross-project-issues-dev@eclipse.org>>

*Betreff: *Re: [cross-project-issues-dev] Bugzilla is down?

Same issue from here (France too).
+ http://downforeveryoneorjustme.com/bugs.eclipse.org

--
Mickael Istria
Eclipse developer for Red Hat Developers <http://developers.redhat.com>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>


-
compeople AG
Untermainanlage 8
60329 Frankfurt/Main
fon: +49 (0) 69 / 27 22 18 0
fax: +49 (0) 69 / 27 22 18 22
web: www.compeople.de <http://www.compeople.de>

Vorstand: Frank Laskowski, Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz

Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
USt-IdNr. DE207665352
-



___
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



--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223 (cell)

___
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

Re: [cross-project-issues-dev] Bugzilla is down?

[Mike Milinkovich]

It is working fine for me. ( I'm in Paris at the moment.)

Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223

> On Nov 14, 2016, at 8:47 AM, Andrey Loskutov  wrote:
> 
> Hi all,
> 
> Bugzilla seem to be down again?
> 
> Kind regards,
> Andrey Loskutov
> 
> http://google.com/+AndreyLoskutov
> ___
> 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

Re: [cross-project-issues-dev] 1000 line limit for contributions

[Mike Milinkovich]

On 20/11/2015 2:01 PM, Max Rydahl Andersen wrote:

Janet / Mike - can we make that happen ?

Or at least get the bug updated with what is standing in the way for Denis to 
attack this as the beast he say he is ?


Bug assigned to webmaster, with a comment on some additional 
implementation complexity.


--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223 (mobile)

___
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

Re: [cross-project-issues-dev] 1000 line limit for contributions

[Mike Milinkovich]

On 19/11/2015 8:27 AM, Sievers, Jan wrote:

If it was really just the missing notification in this case and in general the 
review of contributions can be done in less than 2 weeks, that's OK with me.


I know from conversations with the IP team that they prioritize these 
CQs at the very top of their list. The goal is to be much faster than 2 
weeks.


I think Denis owes both Jan and Janet a beer :)

--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223 (mobile)

___
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

Re: [cross-project-issues-dev] Announcing JDK 9 support for Eclipse Neon

[Mike Milinkovich]

On 27/10/2015 5:18 PM, Daniel Megert wrote:

> "Instead, API is provided for reading the content of such image."

==> The format is not specified but APIs allow to read the content.


Maybe I am wrong, but since we are a Java IDE don't we also have to 
*write* the content of such files?


--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223 (mobile)

EclipseCon Europe 2015 <http://www.eclipsecon.org/europe2015>
___
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

Re: [cross-project-issues-dev] Announcing JDK 9 support for Eclipse Neon

[Mike Milinkovich]

On 26/10/2015 6:49 PM, Stephan Herrmann wrote:


JDK 9 no longer ships the runtime libraries as a set of jars (rt.jar 
...),
but as jimage files, the technical format of which is not subject to 
standardization.

Instead, API is provided for reading the content of such image.
(Hence: "proprietary format").
The BETA feature provides support for working with these jimage files. 


So that causes a problem, right? If the jimage format is not spec'd as 
part of a JSR that means that we have to reverse engineer a 
GPL+CE-licensed implementation in order to emit jimage files. Do I 
understand that correctly?


Is this a topic that I should be raising concerns about at the JCP 
Executive Committee?


--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223 (mobile)

EclipseCon Europe 2015 <http://www.eclipsecon.org/europe2015>
___
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

Re: [cross-project-issues-dev] Announcing JDK 9 support for Eclipse Neon

[Mike Milinkovich]

On 26/10/2015 7:50 AM, Jayaprakash Arthanareeswaran wrote:
At this point, I would like to call out that JDK 9 is unlike any other 
JDK versions of the past, notable change being the JAR files (with 
platform classes) are giving way to a proprietary format. This update 
is not to be confused with Java 9 support, though, which is about Java 
modules.


Jay,

Could you please elaborate on those two sentences? What is the 
proprietary format you are referring to? And perhaps I am not too smart, 
but I don't understand the distinction that you're making between JDK 9 
and Java 9 support.


--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223 (mobile)

EclipseCon Europe 2015 <http://www.eclipsecon.org/europe2015>
___
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

Re: [cross-project-issues-dev] New components in Mars.1 (was Re: Eclipse Mars 1 RC4 issue with Buildship / workspace prompt)

[Mike Milinkovich]

On 23/09/2015 1:49 PM, Doug Schaefer wrote:

if we could ever get Check for Updates working properly, this wouldn't have 
been such a big issue.


Doug (or anyone)

Is there a written proposal anywhere on how "Check for Updates" should 
be modified?


Is there an existing consensus around such a proposal?

--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223 (mobile)

___
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

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

[Mike Milinkovich]

Just out of curiousity, have you asked on the Jetty dev list? Since they're 
only on the release train indirectly, I'm not sure how well they monitor this 
list? 


Mike Milinkovich
mike.milinkov...@eclipse.org 
+1.613.220.3223
  Original Message  
From: Max Rydahl Andersen
Sent: Monday, September 14, 2015 10:15 PM
To: cross-project-issues-dev@eclipse.org
Reply To: Cross project issues
Subject: [cross-project-issues-dev] jetty versions - Another issue to feed on 
the topic of semantic versioning

I don't want to hijack the other thread, but it is related.

JBoss Tools noticed that Jetty has some funky API changes going
on which unless you are super careful things breaks.

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=477385

basically jetty 9.2.9, 9.2.10 and 9.2.13 are not compatible with/between 
each other.

Resulting in if platform ships some parts of jetty 9.2.13 and your 
manifest says it works with 9.2.10 (jetty owns libraries says it does) 
then things fall apart since you end up with a mix of 9.2.10 and 9.2.13 
in your install and that just don't work.

Just wondering if others seen this and/or got any tips to better fix 
this going forward (besides restricting ones version range to 9.2.10 and 
nothing else)

/max
http://about.me/maxandersen
___
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

[cross-project-issues-dev] Fwd: JDK 9 release schedule

[Mike Milinkovich]

For your planning pleasure.Java 9 GA now 22-SEP-2016.

 Forwarded Message 
Subject:JDK 9 release schedule
Date:   Wed, 13 May 2015 11:25:02 -0700
From:   mark.reinh...@oracle.com
To: jdk9-...@openjdk.java.net



2015/5/5 9:21 -0700, mark.reinh...@oracle.com:

Here is a proposed schedule for JDK 9:

  2015-12-10  Feature Complete
  2016-02-04  All Tests Run
  2016-02-25  Rampdown Start
  2016-04-21  Zero Bug Bounce
  2016-06-16  Rampdown Phase 2
  2016-07-21  Final Release Candidate
  2016-09-22  General Availability


Hearing no objections, I've posted this as the schedule of record on
the JDK 9 Project page: http://openjdk.java.net/projects/jdk9/ .

- Mark



___
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

Re: [cross-project-issues-dev] [eclipse-pmc] Proposed schedule for JDK 9

[Mike Milinkovich]

Max,

I have the action item to take another look at this.

Mike Milinkovich
mike.milinkov...@eclipse.org 
+1.613.220.3223
  Original Message  
From: Max Rydahl Andersen
Sent: Tuesday, May 12, 2015 8:27 PM
To: eclipse-...@eclipse.org
Reply To: eclipse-...@eclipse.org
Cc: Cross project issues
Subject: Re: [eclipse-pmc] [cross-project-issues-dev] Proposed schedule for JDK 
9

On 12 May 2015, at 13:07, Daniel Megert wrote:

> The licenses haven't changed.

Afaik EclipseLink releases from Eclipse.org under same license earlier 
or is that wrong ?

> This means as with Java 8, we will provide
> feature patches that can be installed on top of 4.5.x.

Made available from where ?

How can projects like WTP use these ?

/max


>
> Dani
>
>
>
> From: "Max Rydahl Andersen" 
> To: eclipse-...@eclipse.org
> Cc: Cross project issues 
> Date: 12.05.2015 12:12
> Subject: Re: [cross-project-issues-dev] [eclipse-pmc] Proposed
> schedule for JDK 9
> Sent by: cross-project-issues-dev-boun...@eclipse.org
>
>
>
>
>
>> ICYMI, Java 9 is now releasing September 2016.
>
> I'm less worried about *running* Eclipse on Java 9 than I am about
> supporting *developing* Java 9 apps *with* Eclipse.
>
> Any plans on avoiding the issue we had with Java 8 support not being
> available in Eclipse until actual Java 8 GA date ?
>
> Other IDE's already has some basic support for developing with Java 9.
>
> /max
>
>> Mike Milinkovich
>> mike.milinkov...@eclipse.org
>> +1.613.220.3223
>> Original Message
>> From: mark.reinh...@oracle.com
>> Sent: Tuesday, May 5, 2015 12:22 PM
>> To: jdk9-...@openjdk.java.net
>> Subject: Proposed schedule for JDK 9
>>
>> Here is a proposed schedule for JDK 9:
>>
>> 2015-12-10 Feature Complete
>> 2016-02-04 All Tests Run
>> 2016-02-25 Rampdown Start
>> 2016-04-21 Zero Bug Bounce
>> 2016-06-16 Rampdown Phase 2
>> 2016-07-21 Final Release Candidate
>> 2016-09-22 General Availability
>>
>> The dates here are meant to leave sufficient time for broad review 
>> and
>> testing of the significant features of the release, in particular the
>> introduction of a module system and the modularization of the
>> platform,
>> while maintaining the cadence of shipping a major release about every
>> two years.
>>
>> The milestone definitions are the same as those for JDK 8 [1].
>>
>> Comments from JDK 9 Committers are welcome, as are reasoned
>> objections.
>> If no such objections are raised by 23:00 UTC next Tuesday, 12 May, 
>> or
>> if they're raised and then satisfactorily answered, then per the JEP
>> 2.0
>> process proposal [2] this will be adopted as the schedule for JDK 9.
>>
>> (This information is also available on the JDK 9 Project Page [3]).
>>
>> - Mark
>>
>>
>> [1] http://openjdk.java.net/projects/jdk8/milestones#definitions
>> [2] http://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html
>> [3] http://openjdk.java.net/projects/jdk9/
>> ___
>> eclipse-pmc mailing list
>> eclipse-...@eclipse.org
>> To change your delivery options, retrieve your password, or
>> unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/eclipse-pmc
>
>
> /max
> http://about.me/maxandersen
> ___
> 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
> ___
> eclipse-pmc mailing list
> eclipse-...@eclipse.org
> To change your delivery options, retrieve your password, or 
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/eclipse-pmc


/max
http://about.me/maxandersen
___
eclipse-pmc mailing list
eclipse-...@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc
___
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] Fw: Proposed schedule for JDK 9

[Mike Milinkovich]

ICYMI, Java 9 is now releasing September 2016.

Mike Milinkovich
mike.milinkov...@eclipse.org 
+1.613.220.3223
  Original Message  
From: mark.reinh...@oracle.com
Sent: Tuesday, May 5, 2015 12:22 PM
To: jdk9-...@openjdk.java.net
Subject: Proposed schedule for JDK 9

Here is a proposed schedule for JDK 9:

2015-12-10 Feature Complete
2016-02-04 All Tests Run
2016-02-25 Rampdown Start
2016-04-21 Zero Bug Bounce
2016-06-16 Rampdown Phase 2
2016-07-21 Final Release Candidate
2016-09-22 General Availability

The dates here are meant to leave sufficient time for broad review and
testing of the significant features of the release, in particular the
introduction of a module system and the modularization of the platform,
while maintaining the cadence of shipping a major release about every
two years.

The milestone definitions are the same as those for JDK 8 [1].

Comments from JDK 9 Committers are welcome, as are reasoned objections.
If no such objections are raised by 23:00 UTC next Tuesday, 12 May, or
if they're raised and then satisfactorily answered, then per the JEP 2.0
process proposal [2] this will be adopted as the schedule for JDK 9.

(This information is also available on the JDK 9 Project Page [3]).

- Mark


[1] http://openjdk.java.net/projects/jdk8/milestones#definitions
[2] http://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html
[3] http://openjdk.java.net/projects/jdk9/
___
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

Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE

[Mike Milinkovich]

On 04/03/2015 4:15 PM, Martin Lippert wrote:

I am not sure whether this “end of public updates” date reflects what is going 
on inside organizations.
Oracle still offers support for Java6 until Dec 2015, and extended support for 
Dec 2018.

http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings


Sure. And I'm also sure if you pay Microsoft enough money you can get 
support for Windows XP as well. That doesn't make it current.


I guess we just need to come up with a common definition of what we mean 
by "current version".

___
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

Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE

[Mike Milinkovich]

On 04/03/2015 12:18 PM, Ed Willink wrote:
But "As stated above, /we expect that Eclipse works fine on other 
current Java VM and OS versions/


But Java 6 is not a current version of Java. It was EOL'd in 2013.

See http://www.oracle.com/technetwork/java/eol-135779.html

--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223 (mobile)

EclipseCon 2015 <http://www.eclipsecon.org/na2015>
___
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

Re: [cross-project-issues-dev] Equinox fix for Luna SR1 now available as a feature patch in "4.4" repository.

[Mike Milinkovich]

On 02/11/2014 5:07 AM, Max Rydahl Andersen wrote:
...or is there also some political agenda on how we provide these 
updates ? 


For what's I worth, I am not aware of any political agenda that prevents 
us from providing these updates. If someone knows of such, please let me 
know either here on this list or privately.


--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223 (mobile)
___
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

Re: [cross-project-issues-dev] Congratulations! Luna repository is available!

[Mike Milinkovich]

Congratulations everyone!   Mike Milinkovich mike.milinkov...@eclipse.org+1.613.220.3223 (mobile) From: David M WilliamsSent: Wednesday, June 25, 2014 2:56 PMTo: cross-project-issues-dev@eclipse.orgReply To: Cross project issuesSubject: [cross-project-issues-dev] Congratulations! Luna repository is	available!Markus and I have "flipped on"
the Luna repository so the final release bits are now visible and available
to the world. 
The EPP packages will be visible soon,
if not already. 

Feel free to make your own sites visible,
and make your own project announcements. 

(My own little sanity test seemed quite
fast, I assume due to repositories being well mirrored and due to a well
tuned infrastructure, thank Denis and team!) 

And thanks to all you projects teams
for your cooperation and participation in this ninth annual Simultaneous
Release. Well done!


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] [birt-dev] New Eclipse BIRT Milestone Build Available for Download

[Mike Milinkovich]

Cross posting to cross-projects, as I'm sure some folks there will be interested to know of this.   Mike Milinkovich mike.milinkov...@eclipse.org+1.613.220.3223 (mobile) From: Zhiqiang QianSent: Wednesday, May 21, 2014 6:21 PMTo: birt-...@eclipse.orgReply To: For developers on the BIRT projectSubject: [birt-dev] New Eclipse BIRT Milestone Build Available for DownloadBIRT Community,The BIRT development team are pleased to let you know that BIRT 4.4RC1 Milestone Build (build number: 20140521-1030) is now available for download.4.4RC1 Milestone Build <20140521-1030> can be downloaded from the BIRT download page:http://download.eclipse.org/birt/downloads/build.php?build=M-R1-4.4RC1-201405211030As always, please provide your feedback through the newsgroup or by reporting bugs through Bugzilla.Regards,BIRT Team___
birt-dev mailing list
birt-...@eclipse.org
https://dev.eclipse.org/mailman/listinfo/birt-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] cross-project-issues-dev Digest, Vol 100, Issue 9

[Mike Milinkovich]

Rima,

Sorry, but it's a holiday in Canada today, so my guess is that you won't hear 
from Denis until tomorrow.

Mike Milinkovich 
mike.milinkov...@eclipse.org
+1.613.220.3223 (mobile)
  Original Message  
From: Rima Kanguri
Sent: Monday, May 19, 2014 8:21 PM
To: cross-project-issues-dev@eclipse.org; Denis Roy
Reply To: Cross project issues
Subject: Re: [cross-project-issues-dev] cross-project-issues-dev Digest,
Vol 100, Issue 9

We are still seeing dependency errors and fixing the build errors.

Denis,
I haven't got a response for the email below. Is it possible to restore write 
permission on eclipse git server
- Our first priority is to get the RC1 build working ( either using the git 
server or eclipse git hub )
- Next we will try to migrate the builds to use the eclipse git hub

--Rima

-Original Message-
From: Rima Kanguri 
Sent: Monday, May 19, 2014 10:31 AM
To: 'cross-project-issues-dev@eclipse.org'
Cc: Zhiqiang Qian; Wenbin He
Subject: RE: cross-project-issues-dev Digest, Vol 100, Issue 9

Team,
We are still working on build issues. Looks like in addition the icu related 
build fixes, the BIRT source has been moved to the git hub, so we are in the 
process of updating the build scripts.

Denis,
Since we need to do quite a bit of changes and testing to migrate to github.
As a fallback, is it possible for you to restore the write permission on 
Eclipse git server. In case we are not able to get the builds working using the 
new git hub server, we can try to create a working BIRT build from Eclipse Git 
server ( for RC1 release )

--Rima

-Original Message-
From: Zhiqiang Qian 
Sent: Monday, May 19, 2014 10:20 AM
To: Rima Kanguri
Subject: FW: cross-project-issues-dev Digest, Vol 100, Issue 9




Best Regards,
 
Zhiqiang Qian
Actuate Corporation - R&D
A : (+1)650-645-3231
: zq...@actuate.com 

-Original Message-
From: Rima Kanguri 
Sent: Friday, May 09, 2014 9:39 AM
To: cross-project-issues-dev@eclipse.org
Cc: Zhiqiang Qian; P Elanchezhian; Wenbin He
Subject: RE: cross-project-issues-dev Digest, Vol 100, Issue 9

The build fix has been made yesterday and checked in to git.
Chezy is working with his team to upload the build

--Rima

-Original Message-
From: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of 
cross-project-issues-dev-requ...@eclipse.org
Sent: Friday, May 09, 2014 9:00 AM
To: cross-project-issues-dev@eclipse.org
Subject: cross-project-issues-dev Digest, Vol 100, Issue 9

Send cross-project-issues-dev mailing list submissions to
cross-project-issues-dev@eclipse.org

To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
or, via email, send a message with subject or body 'help' to
cross-project-issues-dev-requ...@eclipse.org

You can reach the person managing the list at
cross-project-issues-dev-ow...@eclipse.org

When replying, please edit your Subject line so it is more specific than "Re: 
Contents of cross-project-issues-dev digest..."


Today's Topics:

1. Luna M7 staging repository is complete   (minus BIRT)
(David M Williams)
2. Luna M7 Sim. Release Repositories (and   Packages) are
available (David M Williams)


--

Message: 1
Date: Thu, 8 May 2014 12:22:39 -0400
From: David M Williams 
To: cross-project-issues-dev@eclipse.org
Subject: [cross-project-issues-dev] Luna M7 staging repository is
complete(minus BIRT)
Message-ID:

Content-Type: text/plain; charset="us-ascii"

Having heard nothing, I assume it'll take BIRT longer than we have to produce a 
compatible build, so we'll do what we can without their contribution in M7. I 
know several of you disabled some features that depend on BIRT, so at least you 
can be partially functional in M7 (thanks for that extra effort). 

I've disabled the aggregation job to avoid confusion, and will restart it 
Friday afternoon. 

The reports are still running, and suspect Markus might want to regenerate EPP 
packages to be sure they match repo. 

As far as I know, we can/will still deliver M7 on Friday, but may be "later" in 
the day, depending on how quickly package maintainers can "sign-off". 

I will (probably) still make the repo visible early on Friday, but will discuss 
more with Markus, to see if he'd prefer we coordinate to a closer time. 

Thanks all! 

-- next part --
An HTML attachment was scrubbed...
URL: 
<https://dev.eclipse.org/mailman/private/cross-project-issues-dev/attachments/20140508/08959cd6/attachment.html>

--

Message: 2
Date: Fri, 9 May 2014 09:28:25 -0400
From: David M Williams 
To: cross-project-issues-dev@eclipse.org
Subject: [cross-project-issues-dev] Luna M7 Sim. Release Repositories
(andPackages)

Re: [cross-project-issues-dev] Reminder that M7 is just days away ....

[Mike Milinkovich]

On 02/05/2014 10:52 AM, Marc Khouzam wrote:
I just want to confirm that the only difference in Eclipse Foundation 
Software User Agreement is the date and the fact that the is no Metro 
Link Public License anymore.


As the author of the change, I can confirm that is all that changed.

--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223 (mobile)
EclipseCon France 2014 <http://www.eclipsecon.org/france2014>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Reminder to update your feature "licenses" for Luna

[Mike Milinkovich]

On 25/04/2014 2:54 PM, David M Williams wrote:

If you ever need to check in extreme detail, the authoritative guide is
http://www.eclipse.org/legal/guidetolegaldoc.php 


On that topic: If anyone reading that document (or anything else on the 
legal page[1]) notices any errors or omissions, please feel free to open 
a bug and assign it to me.


Thanks.

[1] http://www.eclipse.org/legal/

--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223 (mobile)
EclipseCon France 2014 <http://www.eclipsecon.org/france2014>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] EF plans to raise awareness of Java 8 support

[Mike Milinkovich]

On 27/03/2014 3:47 PM, John Arthorne wrote:
For things coming in the Luna timeframe, I think the best answer will 
be to point people at the release train development stream builds and 
repository. By May 9th there will be a stable build of the entire 
release train that includes the Java 8 tooling support for all 
projects (assuming they are doing it for Luna). I think most consumers 
will happily wait for that if they have demands beyond the basic JDT 
support, rather than cobbling together bits and pieces from unstable 
builds of various projects. 


John,

I am not entirely sure if you are arguing against doing anything (e.g. 
my initial list of action items), or arguing against including adding 
additional projects to the coverage. Could you please clarify?


--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] EF plans to raise awareness of Java 8 support

[Mike Milinkovich]

On 27/03/2014 2:31 PM, Scott Lewis wrote:
Would you include links (or other page) to j8-enabled features from 
other EF projects?...In my case it will be ECFs use of j8 with OSGi 
remote services [1]...but there are possibly other EF projects that 
can/could have j8-enabled enhancements for Luna.


We would certainly be willing to keep a page (perhaps a wiki page) that 
contains a list of other Java 8 enabled features. But we do not want to 
bury the lede that JDT is supporting Java 8. That is what the vast 
majority of developers will care about. Perhaps closely followed by WTP 
support.


I am _not_ solid technically on this stuff, so I am probably going to 
suggest something embarrassingly dumb. But perhaps we need a shared 
repository where projects who wish to can publish their Kepler SR2 
features which support Java 8?


--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Kepler SR3 for Java 8?

[Mike Milinkovich]

On 27/03/2014 1:28 PM, Konstantin Komissarchik wrote:
Well, it is more work, but it shouldn't be a lot of work since the 
bulk of it is automated and I would think that the value to Eclipse 
community and Eclipse reputation would outweigh the investment.


My impression is that there is no consensus that a Kepler SR3 is 
desirable. That is part of the reason why we're proposing the steps 
outlined in my email from earlier today.


In any event, I think that posting on this thread was a mistake. I've 
started a new thread and will hopefully get some feedback on what the EF 
is proposing to do.


--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] EF plans to raise awareness of Java 8 support

[Mike Milinkovich]

I had previously posted this under the "Kepler SR3 for Java 8?" thread, 
but I think that was a mistake. Rather than hijacking that thread I am 
going to start a new one.


Just so everyone knows, the Eclipse Foundation is considering taking the 
following steps to raise awareness of our Java 8 support. This is coming 
partially as a result from feedback we got from this week's Javaland 
conference in Germany where a number of developers made it very clear 
that they had no idea that Eclipse supported Java 8 at all. Apparently 
only announcing these things on our internal lists isn't sufficient :)


Please note that all of this will be done with exactly what we have 
today. None of this will require any actions on behalf of the Eclipse, 
EPP or other teams.


1. We are going to create a Community Bulletin announcing Java 8
   support that will appear on our home page.
2. We are going to create a web page which clearly documents how to get
   an install our existing Java 8 support for both Kepler SR2 and the
   Luna builds.
3. We are going to put a banner on the downloads page (e.g. "Looking
   for Java 8 support?") which links to (2) above.
4. We are going to create an (or update the existing) Eclipse
   Marketplace entry for the Kepler SR2 Java 8 feature
1. This will allow a drag-and-drop install into a Kepler SR2 workbench.
2. This will allow discovery and installation via the Marketplace
   Client (MPC).
5. We are going to make this Marketplace entry a "featured product"
   which will make it visible on the Marketplace website and in the MPC.
6. [*TBC*] We are going to make the Java 8 support a "featured
   download" to give it some prominence on the download page.

We welcome any comments or feedback.

--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Kepler SR3 for Java 8?

[Mike Milinkovich]

On 27/03/2014 12:36 PM, Konstantin Komissarchik wrote:
so why not go a step farther and put out a full release, so this is 
even easier for users to consume? 


U.because that would be a lot of additional, unplanned work?

--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Kepler SR3 for Java 8?

[Mike Milinkovich]

On 27/03/2014 12:04 PM, Mike Milinkovich wrote:
6. We are going to make the Java 8 support a "featured download" to 
give it some prominence on the download page.


I just realized that this one might not make senseWe'll see what we 
can do about that one.


--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Kepler SR3 for Java 8?

[Mike Milinkovich]

On 27/03/2014 6:18 AM, Sven Efftinge wrote:
So IMHO this is not a stopper for having a more prominent download for 
the Java 8 support.


Just so everyone knows, the Eclipse Foundation is considering taking the 
following steps to raise awareness of our Java 8 support. This is coming 
partially as a result from feedback we got from this week's Javaland 
conference in Germany where a number of developers made it very clear 
that they had no idea that Eclipse supported Java 8 at all. Apparently 
only announcing these things on our internal lists isn't sufficient :)


Please note that all of this will be done with exactly what we have 
today. None of this will require any actions on behalf of the Eclipse, 
EPP or other teams.


1. We are going to create a Community Bulletin announcing Java 8
   support that will appear on our home page.
2. We are going to create a web page which clearly documents how to get
   an install our existing Java 8 support for both Kepler SR2 and the
   Luna builds.
3. We are going to put a banner on the downloads page (e.g. "Looking
   for Java 8 support?") which links to (2) above.
4. We are going to create an (or update the existing) Eclipse
   Marketplace entry for the Kepler SR2 Java 8 feature
1. This will allow a drag-and-drop install into a Kepler SR2 workbench.
2. This will allow discovery and installation via the Marketplace
   Client (MPC).
5. We are going to make this Marketplace entry a "featured product"
   which will make it visible on the Marketplace website and in the MPC.
6. We are going to make the Java 8 support a "featured download" to
   give it some prominence on the download page.

We welcome any comments or feedback.

--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] [ide-dev] EclipseCon Meeting to discuss LDAP-based preference management

[Mike Milinkovich]

Marcel,

This looks like a good summary of the meeting. Thanks for doing that.

All,

I don't see any comment on the document, and I'm not sure if that's 
because everyone loves it, or if it just hasn't been read. If you 
haven't read it you should. It has implications for Luna SR0 (e.g. June)


On 22/03/2014 7:30 AM, Marcel Bruch wrote:

Hi ide-dev,
(cc'ed cross-project)


I summarized the EclipseCon meeting about preference management for Eclipse. We 
additionally discussed briefly an error reporting tool. Please look at the 
notes here [1]. Pascal, I think you can add valuable news to the error 
reporting section since you are doing something similar at Ericsson (if I 
remember correctly)?

Feel free to send comments to the list or add them directly to the document.

Best,
Marcel

[1] 
https://docs.google.com/document/d/1fEbVfCxJ7ds8ZXNM1uCL5wiqBb46FE-2Xss1cyIVrPw/edit?usp=sharing


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] m2e ponders participation in luna

[Mike Milinkovich]

On 16/12/2013 9:39 AM, Igor Fedorenko wrote:
Wasn't there another deadline in February for new CQ submissions? 


I _think_ that's for new dependencies, not a new version of an existing 
dependency. But Wayne or Janet are the experts.


--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] m2e ponders participation in luna

[Mike Milinkovich]

On 15/12/2013 11:06 PM, Igor Fedorenko wrote:

Problem is, maven 3.1.x includes Eclipse Aether and
Eclipse Sisu binaries, both currently under incubation as eclipse
technology project. 


What I don't understand is that if these projects are mature enough to 
be included in production versions of Maven, why don't you simply ask 
the projects to do a Release Review to get to Mature status? It's not 
that much work.


--
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Has Java 5 Platform support been discontinued?

[Mike Milinkovich]

I agree. Let's figure out how to publicly and formally drop support for Java
5. Sun/Oracle discontinued public support in 2009!

 

From
http://en.wikipedia.org/wiki/Java_version_history#J2SE_5.0_.28September_30.2
C_2004.29 

 

J2SE 5.0 entered its end-of-public-updates period on April 8, 2008 updates
are no longer available to the public as of November 3, 2009.

 

Is this a Planning Council topic?

 

Mike Milinkovich

mike.milinkov...@eclipse.org

+1.613.220.3223

 

From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Ed
Willink
Sent: September-03-13 9:24 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Has Java 5 Platform support been
discontinued?

 

Hi

I am doing my best to continue support for existing functionality, so in the
absence of a clear Eclipse statement that Java 5 support is terminated, I
feel I have to continue to keep close to 5.

Guava changing to Java 6 was awkward.

OSGI changing to Java 6 is very close to a mandatory downstream consequence.

Can we please have a clear policy statement rather than a secretive creep.

I don't mind changing to Java 6, it probably makes life easier. But I hate
this are we 5 or 6 limbo?

Regards

Ed Willink 

On 03/09/2013 13:51, David M Williams wrote:

I probably should have mentioned, there are several bugs we are still trying
to work through, where the Tycho/Maven build picks a different "compiler
level" than the way PDE used to it ... and not always in the way we intend,
for example, 

 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=415116>
https://bugs.eclipse.org/bugs/show_bug.cgi?id=415116 
 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=411419>
https://bugs.eclipse.org/bugs/show_bug.cgi?id=411419 

I am not sure if this is related to the issue you are seeing ... or if
merely confirms yet another "unannounced change" ... but I don't think it
changes the bottom line: 

If you want things different than they are, open a bug or comment on an
existing one. If it is merely a matter that you don't really care, but you
have to change your test scripts, then all I can say is "sorry". 





From:Ed Willink  <mailto:e...@willink.me.uk>  
To:Cross project issues
<mailto:cross-project-issues-dev@eclipse.org>
, 
Date:09/03/2013 08:34 AM 
Subject:Re: [cross-project-issues-dev] Has Java 5 Platform
supportbeendiscontinued? 
Sent by:cross-project-issues-dev-boun...@eclipse.org 

  _  




Hi Szymon

Your list omits the 'culprit'.

It is org.eclipse.osgi.util.NLS that is now Java 6 putting paid to all 
attempts at internationalization with Java 5.

Regards

Ed Willink

On 02/09/2013 16:41, Szymon Ptaszkiewicz wrote:
> See
>
<http://www.eclipse.org/projects/project-plan.php?projectid=eclipse#appendix
>
http://www.eclipse.org/projects/project-plan.php?projectid=eclipse#appendix
> for the table of  minimum EE per bundle.
>
> Szymon
>
>
>
>
> From: David M Williams  <mailto:david_willi...@us.ibm.com>

> To: Cross project issues
<mailto:cross-project-issues-dev@eclipse.org>

> Date: 2013-09-02 17:34
> Subject: Re: [cross-project-issues-dev] Has Java 5
Platform support
>  been discontinued?
> Sent by: cross-project-issues-dev-boun...@eclipse.org
>
>
>
>> So it seems that the Platform no longer supports Java 5.
> Yes and no. As a whole, such for whole Eclipse SDK, even Kepler (If not
> Juno) said "Java 6 required", although there were always some bundles (and
> combination of bundles) that supported lower VMs.
>
>> Is this intentional and an unannounced policy change?
> Probably not announced well. It has been discussed at status meetings, and
> various bugzillas, that some previous "1.4" or "1.5" bundles were moving
to
> "1.5" or "1.6", but I am not sure there is yet a comprehensive list of
> those that have. (Other than looking in the manifests themselves).
>
> I think it's been assumed "no one cares about Java 1.5 any longer" ... so,
> if anyone does (i.e. you have requirements or customers with requirements
> for 1.5), then I suggest you open a bug on the specific use-case you need
> to support on 1.5 and what bundle changes prevent that. I'm sure the
> committers for those components would be willing to re-consider if it
> impacts adopters.
>
> But, the default assumption for testing should be "1.6" ... would be my
> personal advice.
>
> HTH
>
>
>
>
>
> From:Ed Willink  <mailto:e...@willink.me.uk> 
> To:Cross project issues
<mailto:cross-proje

Re: [cross-project-issues-dev] Are too many packages actually hurting Eclipse?

[Mike Milinkovich]

Another potential solution that should be on the list for consideration is a reasonably smart installer.   Mike Milinkovichmike.milinkov...@eclipse.org+1.613.220.3223 From: Doug SchaeferSent: Monday, July 29, 2013 8:16 PMTo: Cross project issuesReply To: Cross project issuesSubject: Re: [cross-project-issues-dev] Are too many packages actually hurting Eclipse?




That's great question I was asking myself looking at the Download page the other day. I don't think I have a great answer though.


I like the idea of the big uber package for the reason you list as #3. I'd like to fix our tools plug-ins to play nicer together. Having this package would give us a test bed to work towards.


But it's probably not a great idea for end users, at least not yet. And it certainly isn't a good idea for the Eclipse infrastructure and would chew through way too much bandwidth.


Maybe we can use or adapt the Ecilpse Marketplace to make it easier to load up components. The p2 UI is pretty tough on new users. Marketplace client is a much better experience but it's still hard to discover things. But we could provide our own catalog
 to accomplish this goal.


Doug.




From: Konstantin Komissarchik 
Reply-To: Cross project issues 
Date: Monday, 29 July, 2013 6:35 PM
To: 'Cross project issues' 
Subject: [cross-project-issues-dev] Are too many packages actually hurting Eclipse?








There are twelve packages currently listed on the downloads page, not counting the promoted ones. Are so many packages actually a benefit to users? We try to define packages based on developer profiles, but real developers rarely fit a
 profile. One of the most common complaints that I have seen on forums are related to difficulties in getting an Eclipse installation that has all the pieces that the developer requires. The ironic thing is that we go through a lot of trouble to define a common
 repository with components that are known to work with each other, but then fragment the result into a dozen different packages.
 
Would user experience be better if there was only one Eclipse package on the main download site that had pretty much everything that’s in the aggregated repository?
 
Some of the reasons for not doing that…
 
1. The package would be too large. With modern download speeds, I suspect most users would rather wait a few minutes longer for Eclipse to download than spend time later trying to figure out how to install the missing pieces. The
 disk space difference is also inconsequential these days.
 
2. The users prefer to not include pieces in their installation that they don’t use. I can see that being the case for some advanced Eclipse users, but I don’t believe this holds true across the user base. I suspect that most users
 would rather spend time on their development project than tuning their Eclipse installation.
 
3. Too many plugins in one installation leads to poor user experience. If there are problems like that, we should be identifying and fixing them.
 
Thoughts?
 
- Konstantin






___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Preferences (topic was touched in "Eclipse smells kind of dead" thread)

[Mike Milinkovich]

 

Absolutely. Those types of strategy and funding discussions happen at the 
Board. I would encourage you to pass along your thoughts to the Committer Reps 
and to the Oracle rep on the Eclipse Board.

 

These type of common good projects should not conflict with Foundation’s 
charter, so if it’s a question of funding, let’s have that discussion.

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Preferences (topic was touched in "Eclipse smells kind of dead" thread)

[Mike Milinkovich]

 

That seems to be an odd statement, given that the Eclipse Foundation does not 
manage the release train, nor do we interact with the community on behalf of 
specific projects. At least not in the ways necessary to be responsive to their 
needs.

 

All the discussions that I have seen are either about being more responsive to 
the community (faster release train) or better understanding the community. 
This is exactly the type of the common good that Eclipse Foundation can and 
should help with. 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Preferences (topic was touched in "Eclipse smells kind of dead" thread)

[Mike Milinkovich]

> I'm not sure why we're always expecting companies to drop bus loads of
> developers into projects when we have a pretty healthy individual contributor
> community already at Eclipse. In fact, over half of CDT contributions of late 
> are
> coming from individuals, not companies. And it's really coming from users who
> have the skills to contribute back and not only make their lives better, but 
> others
> as well, and get rewarded by seeing their work on the big stage.

That is really good news for CDT. I wish we had a lot more projects that were 
in your position. But the flip side is that the platform is not in that 
position today. Others will have to speak to what it will take to get to a 
position as enviable as CDT's. 

In addition, the key resources that we have supporting the simultaneous release 
process like David and Markus are, in fact, supported by member companies.  And 
as far as I know, they are tapped out. I do not think that we can realistically 
ask them to do more. And if we want them to do something different, I for one 
would prefer to hear from them what they would like to change. Maybe I'm wrong, 
and they would be perfectly happy to push out two release trains a year (for 
example).

> So really, the changes I'm talking about, more frequent release cycles, 
> creating a
> list of features and bugs we'd like fixed, is aimed at attracting more 
> individuals to
> the party. And I'm pretty sure there are some companies who would like to see
> the same. Create the buzz and companies may take another look.

We are certainly agreed about the need to attract more contributors of all 
types. The Eclipse Foundation has also been pushing this agenda for the last 
couple of years. Embracing git, implementing CBI, project hosting at GitHub, 
and switching to CLAs are all examples of things that we did specifically to 
help reduce barriers to contribution. 

I agree that we need to increase the pace of innovation. My point is that I 
don't see a realistic discussion on this thread about resourcing the changes 
that we would all like to see. I would love to be wrong.




___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Preferences (topic was touched in "Eclipse smells kind of dead" thread)

[Mike Milinkovich]

Mickael,

 

These are general comments, and are certainly not meant as a criticism of
you or Red Hat. You guys are very helpful in a lot of critical areas. That
said.

 

I could imagine the Eclipse Foundation doing something along these lines.
But I am not really sure it is of much value if there are no resources to
work on things. The status quo for quite some time has been that there are
insufficient resources helping on the platform to make the progress we all
want. Actually, it's not just the platform: it is pretty much everything
under the topic of code and processes involved in the "common good". Has
something changed in these areas to warrant the EF to make such an
investment?

 

In addition to the above, it seems that a lot of the user issues I've seen
are specifically related to the Java IDE. We can talk all we want about how
Eclipse is a general platform and there are many tools and languages
supported, but for the vast majority of users the Java development tools is
what they mean when they say "Eclipse". The Java IDE is another area which
has felt under-resourced for a long time. Are there resources - including
user experience resources - available to make significant enhancements
there? 

 

Complaining about the status quo is always good sport. Actually showing up
with the developers necessary to make and maintain those changes is how we
tell who's serious around here. I am certainly not going to have the EF
promote a bunch of changes to the release train process, the EPP packaging
process, end-user feature analysis, etc. unless the people and companies
calling for change actually commit some long-term resources for both the
enhancements and operations needed. Or alternatively they can demonstrate
that the people currently keeping these processes together are happy to make
some changes.

 

If anyone wants to educate me about how there are new resources available,
or how existing resources can be re-allocated to make some significant
progress please feel free to contact me either publicly or privately. I
would _love_ to see improvements in all of these areas. 

 

Mike Milinkovich

mike.milinkov...@eclipse.org

+1.613.220.3223

 

From: Mickael Istria [mailto:mist...@redhat.com] 
Sent: July-17-13 11:53 AM
To: mike.milinkov...@eclipse.org; Cross project issues
Subject: Re: [cross-project-issues-dev] Preferences (topic was touched in
"Eclipse smells kind of dead" thread)

 

On 07/17/2013 04:29 PM, Mike Milinkovich wrote:

If we're looking for user feedback, reading the article and comments here[1]
would be helpful.


Gathering the feedback and reacting to it based on end-users request is not
something Eclipse contributors generally excel at doing. The main
entry-point for contributors is Bugzilla, which doesn't reflect the real
concerns of most users. I guess having the Foundation gathering such
external feedback and create reports per project saying "Here is what people
like and didn't like about your project in the last 3 monthes" could help
project to identify what is critical for better adoption.
Is this something we could imagine the Foundation to provide ? Does it make
sense?

-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> 
My blog <http://mickaelistria.wordpress.com>  - My Tweets
<http://twitter.com/mickaelistria> 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Preferences (topic was touched in "Eclipse smells kind of dead" thread)

[Mike Milinkovich]

I actually did not mean to highlight the reference to Visual Studio per se. I 
meant that the comments about Eclipse’s usability in the article and especially 
in the comments are useful feedback.

 

Mike Milinkovich

mike.milinkov...@eclipse.org

+1.613.220.3223

 

From: Campo, Christian [mailto:christian.ca...@compeople.de] 
Sent: July-17-13 10:47 AM
To: mike.milinkov...@eclipse.org; Cross project issues
Subject: Re: [cross-project-issues-dev] Preferences (topic was touched in 
"Eclipse smells kind of dead" thread)

 

Are you sure that Visual Studio is our target for comparison ?

 

How about this comparision ? 
http://developer4life.blogspot.de/2012/01/intellij-vs-eclipse.html

 

And while Eclipse makes some good points there, there are still a number of 
points where Intellij seems to be better (to my surprise) i.e. "Usability: 
Intellij user experience is much easier to grasp."

 

And there are many comparisons of that kind. I think we should be tackle the 
points where the IntellJ community edition is better than Eclipse rather than 
compare us with Visual Studio.

 

just my 2 cent…..

 

Von: "mike.milinkov...@eclipse.org" 
Organisation: Eclipse Foundation
Antworten an: "mike.milinkov...@eclipse.org" , 
Cross issues 
Datum: Mittwoch, 17. Juli 2013 16:29
An: Cross issues 
Betreff: Re: [cross-project-issues-dev] Preferences (topic was touched in 
"Eclipse smells kind of dead" thread)

 

If we’re looking for user feedback, reading the article and comments here[1] 
would be helpful.

 

[1] 
http://slashdot.org/topic/bi/visual-studio-vs-eclipse-a-programmers-matchup/ 

 

Mike Milinkovich

mike.milinkov...@eclipse.org

+1.613.220.3223

 

From: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Daniel Megert
Sent: July-16-13 4:12 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Preferences (topic was touched in 
"Eclipse smells kind of dead" thread)

 

Christian,

the "refresh" issue has been resolved a year ago in the Juno (4.2) release, but 
you might not see it in old workspaces yet. Make sure the General > Workspace > 
'Refresh on access' preference is checked. You can even go further and enable 
'Refresh using native hooks or poling'.

Regarding recompiling the whole workspace: definitely a big bug. Please file a 
bug report (if not done already) and we will investigate.

The line number preference discussion currently happens in  
<https://bugs.eclipse.org/191154> https://bugs.eclipse.org/191154.

Dani 


From:"Campo, Christian" 
To:Cross project issues 
Date:16.07.2013 09:54
Subject:Re: [cross-project-issues-dev] Preferences (topic was touched 
in "Eclipse smells kind of dead" thread) 
Sent by:cross-project-issues-dev-boun...@eclipse.org

  _  




Sharing prefs between workspaces sounds good. The suggested solution still 
sounds a little bit too complicated (for my taste of course). If I open a 
workspace, why cant I not directly reference an existing workspace and copy the 
preferences from there ? (why the extra export step) And for completeness 
wouldnt it be call if all my Eclipse installations share the same list of know 
workspace locations :-) so that I dont have to add them again when I unpack a 
new Eclipse IDE. 


I also think the "IHateEclipse" page is not only about preferences. I can think 
of a list of top 10 items that every newcomer to Eclipse hates and we since we 
use it so long got used to it. We accept although deep in us we dont think that 
it has to be that way right ?

*   line numbers
*   the reoccuring refresh option (eclipse detects a change on disk, but 
you need to press F5, no option (default=true) to always refresh)
*   software update: couldnt Eclipse auto check for updates like any 
current other tool I use and say "there are updates, do you want to install 
them"
*   software update:  when I select a software update site, it checks the 
P2 data, yet the progress of this is shown at the bottom of the shell window 
and not in the dialog where I am currently working, maybe a thing that people 
dont even notice and get the impression of slowliness
*   and yes I have also seen myself "An error occurred, details: cant 
display details: an error occurred"
*   which leads too:  could it be interesting to give users the option to 
send exceptions in the IDE to eclipse.org and then the individual plugin 
providers can pick them up or query them. (What exceptions in real life have 
happened in the EMF model editor ?) 
*   easier or standard shortcuts. I like the point about CTRL-TAB for 
editor switching. And I hate shortcuts like ALT-CTRL + G + I (does anyone 
seriously use that)
*   I also dont get it why Eclipse recompiles my whole workspace when I 
start t

Re: [cross-project-issues-dev] Preferences (topic was touched in "Eclipse smells kind of dead" thread)

[Mike Milinkovich]

If we’re looking for user feedback, reading the article and comments here[1]
would be helpful.

 

[1]
http://slashdot.org/topic/bi/visual-studio-vs-eclipse-a-programmers-matchup/


 

Mike Milinkovich

mike.milinkov...@eclipse.org

+1.613.220.3223

 

From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Daniel
Megert
Sent: July-16-13 4:12 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Preferences (topic was touched in
"Eclipse smells kind of dead" thread)

 

Christian, 

the "refresh" issue has been resolved a year ago in the Juno (4.2) release,
but you might not see it in old workspaces yet. Make sure the General >
Workspace > 'Refresh on access' preference is checked. You can even go
further and enable 'Refresh using native hooks or poling'. 

Regarding recompiling the whole workspace: definitely a big bug. Please file
a bug report (if not done already) and we will investigate. 

The line number preference discussion currently happens in
<https://bugs.eclipse.org/191154> https://bugs.eclipse.org/191154. 

Dani 


From:"Campo, Christian"  
To:Cross project issues  
Date:16.07.2013 09:54 
Subject:Re: [cross-project-issues-dev] Preferences (topic was
touched in "Eclipse smells kind of dead" thread) 
Sent by:cross-project-issues-dev-boun...@eclipse.org 

  _  




Sharing prefs between workspaces sounds good. The suggested solution still
sounds a little bit too complicated (for my taste of course). If I open a
workspace, why cant I not directly reference an existing workspace and copy
the preferences from there ? (why the extra export step) And for
completeness wouldnt it be call if all my Eclipse installations share the
same list of know workspace locations :-) so that I dont have to add them
again when I unpack a new Eclipse IDE. 


I also think the "IHateEclipse" page is not only about preferences. I can
think of a list of top 10 items that every newcomer to Eclipse hates and we
since we use it so long got used to it. We accept although deep in us we
dont think that it has to be that way right ? 

*   line numbers 
*   the reoccuring refresh option (eclipse detects a change on disk, but
you need to press F5, no option (default=true) to always refresh) 
*   software update: couldnt Eclipse auto check for updates like any
current other tool I use and say "there are updates, do you want to install
them" 
*   software update:  when I select a software update site, it checks
the P2 data, yet the progress of this is shown at the bottom of the shell
window and not in the dialog where I am currently working, maybe a thing
that people dont even notice and get the impression of slowliness 
*   and yes I have also seen myself "An error occurred, details: cant
display details: an error occurred" 
*   which leads too:  could it be interesting to give users the option
to send exceptions in the IDE to eclipse.org and then the individual plugin
providers can pick them up or query them. (What exceptions in real life have
happened in the EMF model editor ?)  
*   easier or standard shortcuts. I like the point about CTRL-TAB for
editor switching. And I hate shortcuts like ALT-CTRL + G + I (does anyone
seriously use that) 
*   I also dont get it why Eclipse recompiles my whole workspace when I
start the Eclipse IDE, although it was compiled and running when I stopped
the IDE 
*   why is the Maven default to update the dependencies from all remote
repositories (takes ages) 
*   startup time ("preparing JDT tooling" etc.) also a complain.


What I really want to say is the pain points that are articulated on that
website, I believe are larger than fixing the preferences. 

So next to that existing technical discussion of preferences I think it
would be also cool if there where a thread about what kind of others
improvments we see. Does anyone agree with my personal list above ? Do you
have your own list of things that got used too but dont really like ? What
are the pain points of your customers ? 

christian 

Von: Eric Moffatt < <mailto:emoff...@ca.ibm.com> emoff...@ca.ibm.com>
Antworten an: Cross issues < <mailto:cross-project-issues-dev@eclipse.org>
cross-project-issues-dev@eclipse.org>
Datum: Montag, 15. Juli 2013 20:39
An: Cross issues < <mailto:cross-project-issues-dev@eclipse.org>
cross-project-issues-dev@eclipse.org>
Betreff: Re: [cross-project-issues-dev] Preferences (topic was touched in
"Eclipse smells kind of dead" thread) 

This is a great discussion !  To me it's always seemed odd that the
workspace is where all the ui information is stored. I'd like to always use
the same UI for the same type of task regardless of where the projects /
files reside.

We've already started 

Re: [cross-project-issues-dev] 6 month release cycle

[Mike Milinkovich]

 

Just out of curiousity, is there a reason why people keep mentioning
monthly, when there is a long-established 6-week cadence? 

 

Maybe we can address these issues by having a few of these monthly builds
get promoted as 'Package Releases'. 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] 6 month release cycle

[Mike Milinkovich]

> ok, fair enough...but if the LTS has been investing so much time and effort 
> into
> building a process for being able to release updates to simultaneous releases,
> will they assume that burden from the Planning Council eventually?  

No, not that I am aware of. As far as I am concerned, LTS is solving quite a 
different problem.

> Will that effort be rolled back into the simultaneous release process that 
> the 
> Planning Council currently takes care of?

At this point in time, the LTS working group is still very much in start-up 
mode. They're still figuring out how to do the builds and manage the processes. 

My advice is that any variant of the thought that somehow LTS will allow change 
to the simultaneous release process is wrong for at least the next year or two. 
I won't say never, but I certainly don't see it within any reasonable planning 
horizon.
 
> maybe a slight off topic, if so my apologies 

No problem at all.

For the record, I _like_ the idea of trying to accelerate our releases to 
encourage more innovation and participation. But there are lots of moving 
parts, requirements, and expectations which need to be satisfied. And very 
limited resources to do them. As but one example, our entire community lean 
heavily on the time and personal commitment of David Williams and Markus 
Knauer. Asking them to do more does not seem reasonable. Perhaps this 
conversation will spur others to step forward to help.
 


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] 6 month release cycle

[Mike Milinkovich]

> but since LTS has the a goal of having a set of set points in time (the 
> existing
> releases) that is maintained into the future, doesn't it make sense to have 
> LTS
> be the primary stakeholder for the entire simultaneous release concept (maybe
> they are?)

The Planning Council is currently responsible for defining and running the 
simultaneous release process.

LTS currently relies upon the existence of a simultaneous release as its 
starting point. The LTS working group would be a very poor replacement for the 
Planning Council in running the simultaneous release. For example, one of the 
major features of the Planning Council is that it has representation on it from 
each of the PMCs. The LTS working group steering committee  does not.


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] 6 month release cycle

[Mike Milinkovich]

> On the flip side, we need to evaluate the benefits of more frequent
releases to
> see if it's worth it.

Completely agree. My assumption is that some projects will want to ship more
often, and some will not. We have a large community, and one size rarely
fits all. A strategy that can accommodate differing requirements will be
necessary.



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] 6 month release cycle

[Mike Milinkovich]

> I wonder, for those companies that want stability, should they focus on
the LTS
> program where old releases are maintained for long periods of time.

The LTS program is in no way intended to be a replacement for the
simultaneous release.

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Eclipse Luna

[Mike Milinkovich]

All,

 

The "Eclipse Luna" name has passed our trademark review process. I think
that was the last hurdle, and Luna is now the official name of the 2014
release train.

 

Thanks for your patience.

 

Mike Milinkovich

Executive Director

Eclipse Foundation

 <mailto:mike.milinkov...@eclipse.org> mike.milinkov...@eclipse.org

+1.613.220.3223 mobile

+1.613.224.9461 x228 office

@mmilinkov

 

 <http://www.eclipsecon.org/2013> eclipsecon 2013

 

<>___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Some Juno participants have not signed up for Kepler

[Mike Milinkovich]

 

Good guess J

 

 

My guess is Mike is thinking of Riena, and yes, that are back in Kepler. 



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Some Juno participants have not signed up for Kepler

[Mike Milinkovich]

Markus,

 

You're right. My bad. I was looking for "RAP", rather than "Remote
Application Platform". Thanks for responding so quickly.

 

Mike Milinkovich

mike.milinkov...@eclipse.org

+1.613.220.3223

 

From: Markus Knauer [mailto:mkna...@eclipsesource.com] 
Sent: January-08-13 4:59 PM
To: Mike Milinkovich
Cc: Eclipse Cross Project Issues
Subject: Re: [cross-project-issues-dev] Some Juno participants have not
signed up for Kepler

 

RAP is/was always part of Juno and will be part of Kepler. Is there a
misunderstanding or what went wrong? 

Thanks, Markus 

On 8 Jan 2013 22:46, "Mike Milinkovich" 
wrote:

In addition to that list, if I recall correctly RAP didn't join Juno, but
thought that they would re-join Kepler. Any news on that?

 

 

From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Wayne
Beaton
Sent: January-08-13 4:17 PM
To: Cross project issues
Subject: [cross-project-issues-dev] Some Juno participants have not signed
up for Kepler

 

AFAICT, the following Juno participants  have not yet signed up to
participate in Kepler:

Virgo, Jetty, Xtend, Xtext, Modeling Workflow Engine, Orion, and Data Tools
Platform

I assume that at least some of these are oversights/errors. Can everybody
please take a look at the projects you care about? 


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Some Juno participants have not signed up for Kepler

[Mike Milinkovich]

In addition to that list, if I recall correctly RAP didn't join Juno, but
thought that they would re-join Kepler. Any news on that?

 

 

From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Wayne
Beaton
Sent: January-08-13 4:17 PM
To: Cross project issues
Subject: [cross-project-issues-dev] Some Juno participants have not signed
up for Kepler

 

AFAICT, the following Juno participants  have not yet signed up to
participate in Kepler:

Virgo, Jetty, Xtend, Xtext, Modeling Workflow Engine, Orion, and Data Tools
Platform

I assume that at least some of these are oversights/errors. Can everybody
please take a look at the projects you care about? 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Website down

[Mike Milinkovich]

It appears to be behaving the same way as the DOS issue we had a few days
ago. I've let Denis know. 

 

From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Wim
Jongman
Sent: September-11-12 7:29 AM
To: Cross project issues; Webmaster(Matt Ward)
Subject: [cross-project-issues-dev] Website down

 

Hi,

 

No response at http://eclipse.org

 

Regards,

 

Wim

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse Testing Lab (was: Performance, 3.8 versus 4.2)

[Mike Milinkovich]

Shawn,

Thanks very much to Google for making this happen! Especially so quickly.

Your support is much appreciated.

> -Original Message-
> From: Shawn Pearce [mailto:s...@google.com]
> Sent: September-07-12 12:45 PM
> To: cross-project-issues-dev@eclipse.org
> Cc: Mike Milinkovich; Denis Roy
> Subject: Eclipse Testing Lab (was: Performance, 3.8 versus 4.2)
> 
> Given the recently raised news concerning 4.2's performance, and the loss
of
> testing hardware previously provided by some member companies, Google's
> Open Source Programs Office is sending the Eclipse Foundation a donation
of
> $20,000 to purchase hardware and begin building a common testing lab.
> 
> Some of this donation may also be used to support the common build
> infrastructure, subject to Denis Roy's and Mike Milinkovich's discretion.
> 
> :-)


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Performance, 3.8 versus 4.2

[Mike Milinkovich]

This one I know the answer to.

 

We puchased a brand new Mac Mini, and we've received it. It will be
provisioned and available shortly after Matt gets back from vacation.

 

Mac tests: The mac test machine in particular has been difficult to get any
kind of tests to run on consistently. Tests take a very long time, and
frequently DNF. We heard rumours of a new mac test machine at eclipse.org,
which I think would be a big help here. 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Performance, 3.8 versus 4.2

[Mike Milinkovich]

McQ,

 

I have to admit that today was the first time that I realized that we had
stopped doing performance testing and test coverage analysis. It was not
what I would consider a pleasant surprise. 

 

The EMO can help. Both in finding computing resources and and helping to
raise awareness that the community needs to step up to help. 

 

The first step in resolving most issues is stating the requirements.  Is
there a document anywhere that describes what the platform team would need
in order to reinstate performance testing in a meaningful way?

 

 

 

From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Mike
Wilson
Sent: September-05-12 5:12 PM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Performance, 3.8 versus 4.2

 

We definitely *want* to re-enable the performance tests. The two things that
have been holding it up currently are:
1) Resources to get them working on the foundation hardware
2) Working through the issues caused by running the performance tests on
shared devices.

When we had a lab to hold dedicated performance machines we put a lot of
effort into configuring and managing them so they behaved as close to
exactly the same as possible. For example, there was one time that the RAM
in a machine failed and we were able to see the impact of replacing that RAM
(even though it was rated the same) as a difference in the test results.

In a world with potentially other tasks running on the same machines, wildly
variable network traffic, etc. I don't think our current performance testing
story will work. If that's true, it means it will be a *lot* of work to get
them running again. Btw, if anyone has good insights on this and/or wants to
help us get the tests running again, we'd love to get your help.

McQ.

Inactive hide details for "Andrey Loskutov" ---2012/09/05 16:16:17---Hi,
Listening to all this 4.2 performance discussions here"Andrey Loskutov"
---2012/09/05 16:16:17---Hi, Listening to all this 4.2 performance
discussions here and for example at

From: "Andrey Loskutov" 
To: cross-project-issues-dev@eclipse.org,
cross-project-issues-dev-requ...@eclipse.org
Date: 2012/09/05 16:16
Subject: Re: [cross-project-issues-dev] Performance, 3.8 versus 4.2
Sent by: cross-project-issues-dev-boun...@eclipse.org

  _  




Hi,

Listening to all this 4.2 performance discussions here and for example at 
[1] I would like to ask if the is a plan to re-enable performance 
regression tests for Eclipse (3.8.x / 4.2.x) platform as we had in the 
past before they were disabled in Juno (see [2]).

If there is no such plan yet, shouldn't we have one?

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=385272
[2] 
http://wiki.eclipse.org/Platform-releng/Transition_Plans_for_Platform_builds
_after_Juno_M6

Regards,
Andrey

On Wed, 05 Sep 2012 15:29:31 +0200, 
 wrote:

> Date: Wed, 5 Sep 2012 09:21:10 -0400
> From: John Arthorne 
> To: Cross project issues 
> Subject: Re: [cross-project-issues-dev] Performance, 3.8 versus 4.2
> Message-ID:
> 
> Content-Type: text/plain; charset="us-ascii"
>
> I suggest anyone having problems to add constructive details on that bug.
> For example profiler output when repeatedly performing a slow operation,
> what plugins are installed, whether it is reproducible with vanilla
> Eclipse SDK, etc. There are some users reporting pervasive slowdowns, and
> for many others it is performing well. Something like a listener leak
> could have effects like this in conjunction with particular installed
> plugins. It takes time after any major release to isolate and resolve
> problems like this.
>
> John
>
> On Wed, Sep 5, 2012 at 3:08 PM, Thomas Hallgren  wrote:
> Hi,
>
> For various reasons I had to switch my development environment from 4.2 
> to
> 3.8 today. I was stunned by the performance improvement after the switch.
> The 3.8 platform is much MUCH faster. It boots faster, it closes windows
> faster, it shows menus faster, etc. It also seems to consume less memory
> and be less buggy. The way things stand right now, there's just no way
> I'll switch back to 4.2!
>
> I must say I was very surprised by this. Why is the 4.2 platform what's
> being fronted on the Eclipse download page when it's user experience and
> quality is lagging behind this much? Is it just me who have had this
> experience?
>
> Regards,
> Thomas Hallgren
>
> --
>
> Message: 5
> Date: Wed, 5 Sep 2012 06:29:22 -0700
> From: "Konstantin Komissarchik" 
> To: "'Cross project issues'" 
> Subject: Re: [cross-project-issues-dev] Performance, 3.8 versus 4.2
> Message-ID: <001201cd8b6a$76b74950$6425dbf0$@komissarc...@oracle.com>
> Content-Type: text/plain; charset="utf-8"
>
> Thomas,
>
>
> You are certainly not the only one seeing performance issues with 4.2. I 
> go back and forth between 4.2 and 3.8 every day depending on the project 
> I need to work on and the difference is quiet noticeable even on very 
> fast 

Re: [cross-project-issues-dev] Does this behavior violate EPL or community prinicples

[Mike Milinkovich]

+Tools PMC (note bolded comment below)

+PDT dev list (please see https://bugs.eclipse.org/bugs/show_bug.cgi?id=383977) 

 

From: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of zhu kane
Sent: July-05-12 1:53 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Does this behavior violate EPL or 
community prinicples

 

I also appreciate the effort of PDT team made, it's great to release 
maintenance version in Indigo SR2 time frame. And it still works well in Juno.

I don't think development team is possible to mess up the release version. 
Anyway I would like to see comments from PDT and PMC.

Mengxin



On Wed, Jul 4, 2012 at 3:04 PM, Ed Willink  wrote:

Hi

The situation doesn't seem nearly as bad as you make out.

The public promoted builds on http://www.eclipse.org/pdt/downloads/ show a 
2-Jan-2012 3.0.0 Maintenance build as the most recent and examining the ZIP 
content reveals 3.0.1 content.

Installing the Juno release train installs a 2-Jan-2012 3.0.1, which correlates 
with the Eclipse CVS.

The Hudson build job 
https://hudson.eclipse.org/hudson/job/cbi-pdt-3.0-juno/changes shows active 
public development of 3.1 in the Eclipse CVS. 

So it seems there are some releng difficulties that cause 3.0.1 to be listed as 
3.0.0 on the download page, and some over-enthusiasm that causes a 3.0.1 
contribution to be called 3.1.

A rename can fix the download page. A resubmission of the review slides can fix 
the misleading version claim. Perhaps Kepler should be 3.2 to avoid more 
confusion.

Regards

Ed Willink



On 04/07/2012 06:17, zhu kane wrote: 

Hello community,

I hesitated about raising such question in here. But I can't get any response 
from PDT project even if filing critical bug for it[1].

PDT team announced PDT 3.1 was released[2] with Juno simultaneous release. PDT 
3.1 also is listed in highlighted Juno project
list[3]. But none of Eclipse users knows how to install it.

I would like to believe it's just a bug, however nobody of PDT project takes 
action for it. In my understanding all projects of Eclipse.org are open source, 
everybody can browse the latest source code even under developing. I'm 
astonished that I can't find any commit related to PDT 3.1 from its source 
repository[4]. Looks like PDT 3.1 doesn't have any public nightly build and 
integration build. I only find a build[5] for 3.0 in Hudson.

I'm wondering whether Eclipse.org/EPL allows a project under it that is not 
really open source and just declared its new release. Hope experienced people 
help resolve my doubts.

Thank you.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=383977
[2] https://bugs.eclipse.org/bugs/attachment.cgi?id=216929
[3] http://eclipse.org/juno/projects.php
[4] 
http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.pdt/features/org.eclipse.php-feature/?root=Tools_Project
[5] https://hudson.eclipse.org/hudson/job/cbi-pdt-3.0-juno/changes

Mengxin Zhu 

 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Is hudson-slave1 down?

[Mike Milinkovich]

I believe Denis got this restarted. Please let us know if you're still having 
problems. 



Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223

-Original Message-
From: Ed Willink 
Sender: cross-project-issues-dev-boun...@eclipse.org
Date: Wed, 13 Jun 2012 07:43:43 
To: Cross project issues
Reply-To: Cross project issues 
Subject: Re: [cross-project-issues-dev] Is hudson-slave1 down?

Hi

slave1 seems ok but fastlane has gone uncommunicative 
(https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-branch-tests/194/)

 Regards

 Ed Willink

On 13/06/2012 02:46, Denis Roy wrote:
> I have restarted the slave agent on slave1.  Let me know if this does not 
> solve the issue.
>
> Sent from mobile device
>
>
> Michael Golubev  wrote:
>
>> Hello,
>>
>> Last half a hour I am getting seemingly endless stream of builds, all
>> failing like the one at [1] with:
>>
>> hudson.util.IOException2: remote file operation failed:
>> /opt/users/hudsonbuild/workspace/tycho-gmp.gmf.tooling at
>> hudson.remoting.Channel@18931e52:hudson-slave1
>>
>> Is it just me or some known problem?
>>
>> [1] https://hudson.eclipse.org/hudson/job/tycho-gmp.gmf.tooling/265/console
>>
>> Regards
>> -- 
>>
>> *Michael "Borlander" Golubev
>> *Eclipse Committer (GMF, UML2Tools)
>> at Montages Think Tank, Prague, Czech Republic
>> 1165/1 Dvorecka, 14700, Prague-4 Podoli
>>
>> tek: +420 602 483 463
>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
> -
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2180 / Virus Database: 2433/5064 - Release Date: 06/12/12
>
>

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Target audience of Juno repo

[Mike Milinkovich]

Just my personal opinion, but given that the Marketplace Client is quite
popular and is included in almost all of the packages, I would recommend
that Eclipse projects take the time to make their project distributions
available via that channel.

 

From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of
Konstantin Komissarchik
Sent: May-29-12 12:39 PM
To: 'Cross project issues'
Subject: Re: [cross-project-issues-dev] Target audience of Juno repo

 

Trying to fragment the repository around user profiles isn't going to be
easy or clean. Many users and use cases will not easily fit into neat
profiles.

 

On the other hand, we already have a venue for presenting users with an
easier to use course-granularity installation option. Eclipse Marketplace.

 

- Konstantin

 

 

From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Miles
Parker
Sent: Tuesday, May 29, 2012 9:25 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Target audience of Juno repo

 


+1, but probably way too late to be asking people to make these kind of
changes now. Something that people should be thinking hard about for Kepler.
There is a major need for a higher level of granularity on the features.
Ideally it would be one per project but that isn't practical in many cases. 

On 2012-05-29, at 8:29 AM, Pascal Rapicault wrote:



Once in a while I go through the content of the Juno repo to see what's
there; and I try to see if I can make any sense of what is made available.
Unfortunately this year it reached a point where I just can't. There are way
too many entries that are subtle variations around the same project and
whose installation result in unexpected results or non functional additions
to my install. For example there is 11 entries for Sapphire, 5 entries for
windowBuilder, an infinity of Mylyn related entries...?

 

I understand that we are all trying to promote our project and brand, but I
would argue that the plethora of entries has a reverse effect that let the
user confused as to what to install.

 

So the main question is "what is the primary target audience of the Juno
repo?"

- an eclipse user - e.g. a JEE programmer

- an eclipse extender - e.g. someone using eclipse technologies
to build an app

 

At this point, the content of the repo looks like what we are addressing
both audience which may be a convenience for us but a nuisance for the end
users. 

 

IMO, the Juno repo should be "end user" focused and only include entries
whose installation will result in new functionalities to be added to the
IDE. Also each entry should have

- a descriptive name (which include removing adjectives such as
incubation, extender)

- a minimal number of entries returned when I search for the
name

- be adequately categorized

 

How do we go about exposing the rest of the content for extenders?

- Different repo URLs (e.g.
download.eclipse.org/releases/juno/developer)

- Addition of a developer focused category (with nested
categories)

 

wdyt?

 

Pascal

___

cross-project-issues-dev mailing list

cross-project-issues-dev@eclipse.org

https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

 

__

Miles T. Parker

Senior Solutions Architect

Tasktop

http://tasktop.com

Committer, Eclipse Mylyn and Virgo

Project Lead, Model Focussing Tools and AMP

http://milesparker.blogspot.com

skype: milestravisparker

 

 

 

 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] deploying snapshot builds from hudson.e.o to oss.sonatype.org

[Mike Milinkovich]

The Eclipse Foundation has a strict policy of using only open source
technology for its core infrastructure. The reason is that we have over 100
commerical members who compete in  the marketplace and would love to point
to Eclipse as a reference case for their software. Vendor neutrality is,
upon occasion, a PITA.

 

This has been discussed at the Board many times, but if you want to raise it
as an issue with the committer reps please do so. 

 

I just checked with the folks at Sonatype, and they have a standing offer of
a free license for Nexus Pro, with no strings attached, for the Eclipse
Foundation.

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] deploying snapshot builds from hudson.e.o to oss.sonatype.org

[Mike Milinkovich]

Darn. That means we can't use it. We avoid using proprietary tools in 
our shared development infrastructure.



On 09/12/2011 12:48 PM, Brian de Alwis wrote:

On 9-Dec-2011, at 12:10 PM, Mike Milinkovich wrote:

Can anyone on this list advise as to whether the most recent open source 
version of Nexus supports this staging feature?

Sonatype's comparison chart shows that it's a feature of the professional 
version only:

http://sonatype.com/Products/Sonatype-Pro-for-Nexus/Features-Overview

Brian.

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] deploying snapshot builds from hudson.e.o to oss.sonatype.org

[Mike Milinkovich]

> -Original Message-
> I mean whatever the version that is on maven.eclipse.org doesn't have
> staging support, I am not sure if that is only in the commercial version or 
> not
> anymore

Can anyone on this list advise as to whether the most recent open source 
version of Nexus supports this staging feature?
 
 


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] deploying snapshot builds from hudson.e.o to oss.sonatype.org

[Mike Milinkovich]

> -Original Message-
> To make the maven.eclipse.org instance really useful it needs to have
staging
> support which is not in the version of nexus there at the moment. 

Jesse,

Can you please clarify that a bit? By the "version of nexus", do you mean we
don't have the most recent version of the open source version, or we don't
have the commercial version?



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Maven buildQualifier value

[Mike Milinkovich]

I am going to take a wild guess and say that the build is using UTC



> -Original Message-
> From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-
> issues-dev-boun...@eclipse.org] On Behalf Of Greg Watson
> Sent: November-10-11 1:17 PM
> To: Cross project issues
> Subject: [cross-project-issues-dev] Maven buildQualifier value
> 
> Hi,
> 
> Does anyone know why the buildQualifier value is about 5 hours ahead of
> the actual build time? For example, the last cdt-nightly build run on Nov
9 at
> 6:01am, however the buildQualifier is 20091106. Is the hudson master
in
> some far off time zone somewhere? Or in a time warp?
> 
> Greg
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Unable to get to bugs.eclipse.org, eclipse.org

[Mike Milinkovich]

and we're back. The website should be up and running.


> -Original Message-
> From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-
> issues-dev-boun...@eclipse.org] On Behalf Of Greg Watson
> Sent: November-05-11 9:19 PM
> To: Cross project issues
> Subject: Re: [cross-project-issues-dev] Unable to get to bugs.eclipse.org,
> eclipse.org
> 
> Great! It's not a figment of my imagination then :-)
> 
> Greg
> 
> On Nov 5, 2011, at 9:06 PM, Mike Milinkovich wrote:
> 
> >
> > I am.
> >
> >
> > --Original Message--
> > From: Greg Watson
> > Sender: cross-project-issues-dev-boun...@eclipse.org
> > To: Cross project issues
> > ReplyTo: Cross project issues
> > Subject: [cross-project-issues-dev] Unable to get to bugs.eclipse.org,
>   eclipse.org
> > Sent: Nov 5, 2011 9:04 PM
> >
> > I'm getting server errors from bugs.eclipse.org and eclipse.org. Is
anyone
> else seeing this?
> >
> > Greg
> > ___
> > cross-project-issues-dev mailing list
> > cross-project-issues-dev@eclipse.org
> > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> >
> >
> > Mike Milinkovich
> > mike.milinkov...@eclipse.org
> > +1.613.220.3223
> > ___
> > cross-project-issues-dev mailing list
> > cross-project-issues-dev@eclipse.org
> > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Unable to get to bugs.eclipse.org, eclipse.org

[Mike Milinkovich]

A slightly longer answer: yes, it appears that the website is down. The
webmaster team is working on it.


> -Original Message-
> From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-
> issues-dev-boun...@eclipse.org] On Behalf Of Greg Watson
> Sent: November-05-11 9:05 PM
> To: Cross project issues
> Subject: [cross-project-issues-dev] Unable to get to bugs.eclipse.org,
> eclipse.org
> 
> I'm getting server errors from bugs.eclipse.org and eclipse.org. Is anyone
> else seeing this?
> 
> Greg
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Unable to get to bugs.eclipse.org, eclipse.org

[Mike Milinkovich]

I am. 


--Original Message--
From: Greg Watson
Sender: cross-project-issues-dev-boun...@eclipse.org
To: Cross project issues
ReplyTo: Cross project issues
Subject: [cross-project-issues-dev] Unable to get to bugs.eclipse.org,  
eclipse.org
Sent: Nov 5, 2011 9:04 PM

I'm getting server errors from bugs.eclipse.org and eclipse.org. Is anyone else 
seeing this?

Greg
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev