jdt-dev http://dev.eclipse.org/mhonarc/lists/jdt-dev/maillist.html jdt-dev en-us Fri, 03 May 2013 14:54:54 GMT Fri, 03 May 2013 14:54:54 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) jdt-dev http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/jdt-dev/maillist.html Re: [jdt-dev] [eclipse-pmc] FW: JDK 8 schedule proposal posted http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00716.html Dani,That sounds like a great plan! Thanks. Mike Milinkovich+1.613.220.3223mike.milinkovich@xxxxxxxxxxxOn 2013-04-19, at 3:04 AM, Daniel Megert <daniel_megert@xxxxxxxxxx> wrote:
Dani,

That sounds like a great plan! Thanks. 

Mike Milinkovich
+1.613.220.3223

On 2013-04-19, at 3:04 AM, Daniel Megert <daniel_megert@xxxxxxxxxx> wrote:

With the new team members getting up to speed and lots of help from the community (thanks Stephan, Jesper and Andy!), we were back on track to have the features in the compiler for the original GA in September. But, we also knew that there are still ongoing spec discussions and expected a delay to get those remaining issues sorted out.

My plan is to provide a feature patch against Kepler SR2 once Javaâ 8 goes GA and then ship the Eclipse Javaâ 8 support along with Luna in June 2014.

Dani

From: "Mike Milinkovich" <mike.milinkovich@xxxxxxxxxxx>
To: <jdt-dev-core@xxxxxxxxxxx>,
Cc: eclipse-pmc@xxxxxxxxxxx
Date: 18.04.2013 19:05
Subject: [eclipse-pmc] FW: JDK 8 schedule proposal posted




FYI, It is now pretty much official that the Java 8 release will be slipping
to Q1 2014.

So it looks like the team has some extra time to implement the new JDT
features for Java 8. Hopefully these can be fully baked into the Luna
release plan.

Mike Milinkovich
mike.milinkovich@xxxxxxxxxxx
+1.613.220.3223


-----Original Message-----
From: gb-bounces@xxxxxxxxxxxxxxxx [mailto:gb-bounces@xxxxxxxxxxxxxxxx] On
Behalf Of mark.reinhold@xxxxxxxxxx
Sent: April-18-13 12:50 PM
To: gb@xxxxxxxxxxxxxxxx
Subject: JDK 8 schedule proposal posted

FYI:

 http://mreinhold.org/blog/secure-the-train
 http://mail.openjdk.java.net/pipermail/jdk8-dev/2013-April/002336.html

- Mark


_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc

]]> Fri, 19 Apr 2013 12:11:15 GMT http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00716.html mike.milinkovich@xxxxxxx (Mike Milinkovich) [jdt-dev] Fw: [eclipse-pmc] FW: JDK 8 schedule proposal posted http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00715.html ----- Forwarded by Daniel Megert/Zurich/IBM on 19.04.2013 09:07 ----- From: Daniel Megert/Zurich/IBM To: mike.milinkovich@xxxxxxxxxxx, Cc: eclipse-pmc@xxxxxxxxxxx, jdt-dev-@xxxxxxxxxxx, John Kellerman/Raleigh/IBM@IBMUS, Pat Huff/Raleigh/IBM@IBMUS, Scott Ri... ----- Forwarded by Daniel Megert/Zurich/IBM on 19.04.2013 09:07 -----
From: Daniel Megert/Zurich/IBM
To: mike.milinkovich@xxxxxxxxxxx,
Cc: eclipse-pmc@xxxxxxxxxxx, jdt-dev-@xxxxxxxxxxx, John Kellerman/Raleigh/IBM@IBMUS, Pat Huff/Raleigh/IBM@IBMUS, Scott Rich/Zurich/IBM@IBMCH, Thomas Watson/Austin/IBM@IBMUS
Date: 19.04.2013 09:04
Subject: Re: [eclipse-pmc] FW: JDK 8 schedule proposal posted



With the new team members getting up to speed and lots of help from the community (thanks Stephan, Jesper and Andy!), we were back on track to have the features in the compiler for the original GA in September. But, we also knew that there are still ongoing spec discussions and expected a delay to get those remaining issues sorted out.

My plan is to provide a feature patch against Kepler SR2 once Java™ 8 goes GA and then ship the Eclipse Java™ 8 support along with Luna in June 2014.

Dani

From: "Mike Milinkovich" <mike.milinkovich@xxxxxxxxxxx>
To: <jdt-dev-core@xxxxxxxxxxx>,
Cc: eclipse-pmc@xxxxxxxxxxx
Date: 18.04.2013 19:05
Subject: [eclipse-pmc] FW: JDK 8 schedule proposal posted




FYI, It is now pretty much official that the Java 8 release will be slipping
to Q1 2014.

So it looks like the team has some extra time to implement the new JDT
features for Java 8. Hopefully these can be fully baked into the Luna
release plan.

Mike Milinkovich
mike.milinkovich@xxxxxxxxxxx
+1.613.220.3223


-----Original Message-----
From: gb-bounces@xxxxxxxxxxxxxxxx [mailto:gb-bounces@xxxxxxxxxxxxxxxx] On
Behalf Of mark.reinhold@xxxxxxxxxx
Sent: April-18-13 12:50 PM
To: gb@xxxxxxxxxxxxxxxx
Subject: JDK 8 schedule proposal posted

FYI:

 http://mreinhold.org/blog/secure-the-train
 http://mail.openjdk.java.net/pipermail/jdk8-dev/2013-April/002336.html

- Mark


_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc


]]> Fri, 19 Apr 2013 07:08:09 GMT http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00715.html daniel_megert@xxxxxxx (Daniel Megert) Re: [jdt-dev] New Class Wizard with explicit values http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00714.html Those fields are set by the code. You can't change it from the outside. Dani From: Marco Isella &lt;marco@xxxxxxx&gt; To: jdt-dev@xxxxxxxxxxx, Date: 16.04.2013 14:00 Subject: [jdt-dev] New Class Wizard with explicit values Hi, I wolud like to put the values in t... Those fields are set by the code. You can't change it from the outside.

Dani

From: Marco Isella <marco@xxxxxxx>
To: jdt-dev@xxxxxxxxxxx,
Date: 16.04.2013 14:00
Subject: [jdt-dev] New Class Wizard with explicit values




Hi,

I wolud like to put the values in the 'Source Folder:' and 'Package:'
fields of the New Class Wizard to a fixed value (I want that every new
class will be created the same source folder and in the same package).
I found that I can configure a bit the wizard via the
.metadata/.plugins/org.eclipse.jdt.ui.dialog_settings.xml file but not
the fields I'm interested in.
Any idea how could I do this?

Thanks

Marco
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-dev

]]> Wed, 17 Apr 2013 09:59:06 GMT http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00714.html daniel_megert@xxxxxxx (Daniel Megert) [jdt-dev] New Class Wizard with explicit values http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00713.html Hi, I wolud like to put the values in the 'Source Folder:' and 'Package:' fields of the New Class Wizard to a fixed value (I want that every new class will be created the same source folder and in the same package). I found that I can configure a bit the w... Hi, I wolud like to put the values in the 'Source Folder:' and 'Package:' fields of the New Class Wizard to a fixed value (I want that every new class will be created the same source folder and in the same package). I found that I can configure a bit the wizard via the .metadata/.plugins/org.eclipse.jdt.ui.dialog_settings.xml file but not the fields I'm interested in. Any idea how could I do this? Thanks Marco ]]> Tue, 16 Apr 2013 12:00:22 GMT http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00713.html marco@xxxxxxx (Marco Isella) Re: [jdt-dev] org.junit 4.11 and backward compatibility http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00712.html JDT 3.7 should work fine with org.junit 4.11 and org.hamcrest.core 1.3. Our implementation doesn't have an upper bound on the JUnit version. I did some manual tests and ran our test suite with this setup, and everything looked fine. HTH, Markus Keller IBM ... JDT 3.7 should work fine with org.junit 4.11 and org.hamcrest.core 1.3.

Our implementation doesn't have an upper bound on the JUnit version. I did some manual tests and ran our test suite with this setup, and everything looked fine.

HTH,

Markus Keller
IBM Rational Zurich Research Lab
Eclipse JDT UI


From: Mickael Istria <mistria@xxxxxxxxxx>
To: jdt-dev@xxxxxxxxxxx,
Date: 2013-04-09 11:48
Subject: [jdt-dev] org.junit 4.11 and backward compatibility




Hi all,

Since Kepler M6, the default version of JUnit is 4.11, and implies using hamcrest 1.3. SWTBot depends on Hamcrest 1.1 and JUnit 4.8, and the bad piece of news is that hamcrest 1.3 has some API changes that makes SWTBot failing on Kepler M6. https://bugs.eclipse.org/bugs/show_bug.cgi?id=404346
For SWTBot, we want to keep a 2-release train backward compatibility (ie we want next version to support Kepler, Juno and Indigo).

I'm trying to figure out the best way to deal with this issue:
e tried to change SWTBot code to depend on methods that are in both hamcrest 1.3 and 1.1 => This does not work because SWTBot uses org.hamcrest.library (1.1) which fails with org.hamcrest.core (1.3), so there is still a transitive dependency on org.hamcrest 1.1. So the best way to fix that is "simply" to make SWTBot depend on org.hamcrest.* 1.3 and org.junit 4.11 (mandatory because OSGi won't load org.junit 4.8 and org.hamcrest 1.3 in same bundle classpath). But here comes the question:
Will using org.junit 4.11 and org.hamcrest 1.3 still work with Indigo? If we make a dependency from SWTBot to org.junit 4.11 and org.hamcrest 1.3, then all "test runtimes" will use these versions by default instead of "factory" org.junit 4.8 and org.hamcrest 1.1. Is there a risk of breaking JDT 3.7 with these bundles?

Cheers,

PS: this is a high priority issue for projects that are building against Kepler and using SWTBot for tests.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-dev

]]> Tue, 09 Apr 2013 13:49:39 GMT http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00712.html markus_keller@xxxxxxx (Markus Keller) [jdt-dev] org.junit 4.11 and backward compatibility http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00711.html Hi all, Since Kepler M6, the default version of JUnit is 4.11, and implies using hamcrest 1.3. SWTBot depends on Hamcrest 1.1 and JUnit 4.8, and the bad piece of news is that hamcrest 1.3 has some API changes that makes SWTBot failing on Kepler M6. https:... Hi all,

Since Kepler M6, the default version of JUnit is 4.11, and implies using hamcrest 1.3. SWTBot depends on Hamcrest 1.1 and JUnit 4.8, and the bad piece of news is that hamcrest 1.3 has some API changes that makes SWTBot failing on Kepler M6. https://bugs.eclipse.org/bugs/show_bug.cgi?id=404346
For SWTBot, we want to keep a 2-release train backward compatibility (ie we want next version to support Kepler, Juno and Indigo).

I'm trying to figure out the best way to deal with this issue:
e tried to change SWTBot code to depend on methods that are in both hamcrest 1.3 and 1.1 => This does not work because SWTBot uses org.hamcrest.library (1.1) which fails with org.hamcrest.core (1.3), so there is still a transitive dependency on org.hamcrest 1.1. So the best way to fix that is "simply" to make SWTBot depend on org.hamcrest.* 1.3 and org.junit 4.11 (mandatory because OSGi won't load org.junit 4.8 and org.hamcrest 1.3 in same bundle classpath). But here comes the question:
Will using org.junit 4.11 and org.hamcrest 1.3 still work with Indigo? If we make a dependency from SWTBot to org.junit 4.11 and org.hamcrest 1.3, then all "test runtimes" will use these versions by default instead of "factory" org.junit 4.8 and org.hamcrest 1.1. Is there a risk of breaking JDT 3.7 with these bundles?

Cheers,

PS: this is a high priority issue for projects that are building against Kepler and using SWTBot for tests.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets
]]> Tue, 09 Apr 2013 09:48:44 GMT http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00711.html mistria@xxxxxxx (Mickael Istria) [jdt-dev] Project meta data is out of date for eclipse.jdt http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00710.html Dani, Projects are required to keep meta data up to date using the MyFoundation Portal (http://portal.eclipse.org/). The following problems were found with this project's meta-data: * There is no next/future release of this project. All Eclipse projects mu... Dani, Projects are required to keep meta data up to date using the MyFoundation Portal (http://portal.eclipse.org/). The following problems were found with this project's meta-data: * There is no next/future release of this project. All Eclipse projects must have a "next release" planned and scheduled. ]]> Fri, 05 Apr 2013 04:00:22 GMT http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00710.html emo@xxxxxxx (portal on behalf of emo) [jdt-dev] Project meta data is out of date for eclipse.jdt http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00709.html Dani, Projects are required to keep meta data up to date using the MyFoundation Portal (http://portal.eclipse.org/). The following problems were found with this project's meta-data: * There is no next/future release of this project. All Eclipse projects mu... Dani, Projects are required to keep meta data up to date using the MyFoundation Portal (http://portal.eclipse.org/). The following problems were found with this project's meta-data: * There is no next/future release of this project. All Eclipse projects must have a "next release" planned and scheduled. ]]> Sat, 05 Jan 2013 05:00:14 GMT http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00709.html emo@xxxxxxx (portal on behalf of emo) Re: [jdt-dev] JDT site migration to git http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00708.html -- with best regards,Denys Digtiar See https://bugs.eclipse.org/bugs/show_bug.cgi?id=213636
 



On Tue, Oct 2, 2012 at 2:15 PM, Daniel Megert <daniel_megert@xxxxxxxxxx> wrote:
I've started the migration process. For details see bug 390915
 
: Migrate JDT website to Git.
Please file bug reports for the outdated web pages that you plan to fix, so that we can review the changes there.

Dani

From: Denys Digtiar <duemir@xxxxxxxxx>
To: jdt-dev@xxxxxxxxxxx,
Date: 26.09.2012 11:02
Subject: [jdt-dev] JDT site migration to git




Hi guys,

I am not sure whether it is right place to post it. If it is not,
please point me to the right one.
I would like to contribute to the project. I am thinking to start with
updating JDT site.
Tasks like making sure that all the pages are moved to Phoenix, making
Nova a default them, etc.
I have noticed that a lot of eclipse.org
 
sites have already been moved
from cvs to the git but jdt's one have not.
Can anybody please initiate move to the git please.
I don't want to force it and I understand that there is still 85 days
till cvs goes read-only but it is really a stopper for me.
I struggled with cvs a bit but I can not even update project without
getting an error and I see no incentives to learn how to properly use
it because I believe it is outdated and because of eclipse wide
migration to git it will eventually be deprecated.
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-dev
 


_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-dev
 





--
with best regards,
Denys Digtiar
]]> Sat, 10 Nov 2012 06:36:40 GMT http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00708.html duemir@xxxxxxx (Denys Digtiar) [jdt-dev] Project meta data is out of date for eclipse.jdt http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00707.html Dani, Projects are required to keep meta data up to date using the MyFoundation Portal (http://portal.eclipse.org/). The following problems were found with this project's meta-data: * There is no next/future release of this project. All Eclipse projects mu... Dani, Projects are required to keep meta data up to date using the MyFoundation Portal (http://portal.eclipse.org/). The following problems were found with this project's meta-data: * There is no next/future release of this project. All Eclipse projects must have a "next release" planned and scheduled. ]]> Mon, 05 Nov 2012 05:00:15 GMT http://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00707.html emo@xxxxxxx (portal on behalf of emo)