platform-core-dev http://dev.eclipse.org/mhonarc/lists/platform-core-dev/maillist.html platform-core-dev en-us Fri, 03 May 2013 14:57:38 GMT Fri, 03 May 2013 14:57:38 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) platform-core-dev http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/platform-core-dev/maillist.html [platform-core-dev] Project meta data is out of date for eclipse.platform.resources http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01703.html Szymon, 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: * Project home page (projecturl = http://www.eclipse.org/eclipse/platfor... Szymon, 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: * Project home page (projecturl = http://www.eclipse.org/eclipse/platform-core/) does not have an "About <project>","About This Project" or "Information about <project>" link. Projects are required to provide that standard link on their home page (see http://www.eclipse.org/projects/standard-link-on-home-page.php) . The 'About' link should point to this URL: http://www.eclipse.org/projects/project_summary.php?projectid=eclipse.platf orm.resources ]]> Fri, 05 Apr 2013 04:00:14 GMT http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01703.html emo@xxxxxxx (portal on behalf of emo) Re: [platform-core-dev] Creating new file without using java.io.File http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01702.html Thanks a lot. That worked :) ________________________________ From: platform-core-dev-bounces@xxxxxxxxxxx [platform-core-dev-bounces@xxxxxxxxxxx] on behalf of John Arthorne [John_Arthorne@xxxxxxxxxx] Sent: Friday, March 22, 2013 4:58 PM To: Eclipse Platfor... Thanks a lot. That worked :) ________________________________ From: platform-core-dev-bounces@xxxxxxxxxxx [platform-core-dev-bounces@xxxxxxxxxxx] on behalf of John Arthorne [John_Arthorne@xxxxxxxxxx] Sent: Friday, March 22, 2013 4:58 PM To: Eclipse Platform Core component developers list. Subject: Re: [platform-core-dev] Creating new file without using java.io.File You can create a new empty file by opening an output stream and then immediately close it. I.e., fs.openOutputStream(...).close(); John From: "Grigoropol, IoanaX" <ioanax.grigoropol@xxxxxxxxx> To: "platform-core-dev@xxxxxxxxxxx" <platform-core-dev@xxxxxxxxxxx>, Date: 03/22/2013 10:28 AM Subject: [platform-core-dev] Creating new file without using java.io.File Sent by: platform-core-dev-bounces@xxxxxxxxxxx ________________________________ Hello, I am trying to abstractive a remote file store implementation and I am stuck in the following scenario: IFileStore fs = EFS.getStore(uri); fs = fs.getFileStore(relPath); IFileInfo f = fs.fetchInfo(); if (!f.exists()){ // create this file } Is there a way of creating a new file without using java.io.File.createNewFile() ? This fails in my case since the URI that this file was created on is not a local one (does not start with "file://"). Are there any recommended ways of creating a new file just by using the interfaces IFileInfo and/ord IFileStore (eg. fileStore.createNewFile() method)? Thank you, Ioana Grigoropol _______________________________________________ platform-core-dev mailing list platform-core-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/platform-core-dev ]]> Mon, 25 Mar 2013 11:12:29 GMT http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01702.html ioanax.grigoropol@xxxxxxx (Grigoropol, IoanaX) Re: [platform-core-dev] Creating new file without using java.io.File http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01701.html You can create a new empty file by opening an output stream and then immediately close it. I.e., fs.openOutputStream(...).close(); John From: &quot;Grigoropol, IoanaX&quot; &lt;ioanax.grigoropol@xxxxxxxxx&gt; To: bsp; &quot;platform-core-dev@xxxxxxxxxxxuot; &lt;platfo... You can create a new empty file by opening an output stream and then immediately close it. I.e., fs.openOutputStream(...).close();

John




From:        "Grigoropol, IoanaX" <ioanax.grigoropol@xxxxxxxxx>
To:        "platform-core-dev@xxxxxxxxxxx" <platform-core-dev@xxxxxxxxxxx>,
Date:        03/22/2013 10:28 AM
Subject:        [platform-core-dev] Creating new file without using java.io.File
Sent by:        platform-core-dev-bounces@xxxxxxxxxxx



Hello,

I am trying to abstractive a remote file store implementation and I am stuck in the following scenario:

           IFileStore fs = EFS.getStore(uri);
           fs = fs.getFileStore(relPath);
           IFileInfo f = fs.fetchInfo();
           if (!f.exists()){
                // create this file
           }
Is there a way of creating a new file without using java.io.File.createNewFile() ?  This fails in my case since the URI that this file was created on is not a local one (does not start with "file://").
Are there any recommended ways of creating a new file just by using the interfaces IFileInfo and/ord IFileStore (eg. fileStore.createNewFile() method)?

Thank you,
Ioana Grigoropol
_______________________________________________
platform-core-dev mailing list
platform-core-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-core-dev
]]> Fri, 22 Mar 2013 14:58:39 GMT http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01701.html John_Arthorne@xxxxxxx (John Arthorne) [platform-core-dev] Creating new file without using java.io.File http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01700.html Hello, I am trying to abstractive a remote file store implementation and I am stuck in the following scenario: IFileStore fs = EFS.getStore(uri); fs = fs.getFileStore(relPath); IFileInfo f = fs.fetchInfo(); if (!f.exists()){ // create this file } Is there ... Hello, I am trying to abstractive a remote file store implementation and I am stuck in the following scenario: IFileStore fs = EFS.getStore(uri); fs = fs.getFileStore(relPath); IFileInfo f = fs.fetchInfo(); if (!f.exists()){ // create this file } Is there a way of creating a new file without using java.io.File.createNewFile() ? This fails in my case since the URI that this file was created on is not a local one (does not start with "file://"). Are there any recommended ways of creating a new file just by using the interfaces IFileInfo and/ord IFileStore (eg. fileStore.createNewFile() method)? Thank you, Ioana Grigoropol ]]> Fri, 22 Mar 2013 14:28:12 GMT http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01700.html ioanax.grigoropol@xxxxxxx (Grigoropol, IoanaX) [platform-core-dev] Join 'Workspace-Local Code Search' project for GSOC 2013 http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01699.html Hi, I am final year computer engineering undergraduate from University of Peradeniya. I have used Eclipse for 3 years and I am really like to join Eclipse for GSOC 2013. I am interested in the &#39;Workspace-Local Code Search&#39; project. I have an idea about the... 
Hi,

I am final year computer engineering undergraduate from University of Peradeniya. I have used Eclipse for 3 years and I am really like to join Eclipse for GSOC 2013.
I am interested in the 'Workspace-Local Code Search' project. I have an idea about the expected task. Could you please give me advice about how I get started with

Thank you,
Malintha Adikari
]]> Sun, 24 Feb 2013 04:46:06 GMT http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01699.html malintha.adikari@xxxxxxx (Malintha Adikari) [platform-core-dev] Join 'Create filterable Console View' Project for GSOC 2013 http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01698.html Hi, I am final year computer engineering undergraduate from University of Peradeniya. I have used Eclipse for 3 years and I am really like to join Eclipse for GSOC 2013. I am interested in the 'Create filterable Console View' project. I have an idea about ... Hi,
I am final year computer engineering undergraduate from University of Peradeniya. I have used Eclipse for 3 years and I am really like to join Eclipse for GSOC 2013. I am interested in the 'Create filterable Console View' project. I have an idea about the expected task. Could you please give me advice about how I get started with

Thank you,
Malintha Adikari

]]> Sat, 23 Feb 2013 23:41:37 GMT http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01698.html malintha.adikari@xxxxxxx (Malintha) [platform-core-dev] Gerrit for eclipse.platform.ui and eclipse.platform.runtime http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01697.html We&#39;ve had Gerrit active on eclipse.platform.ua for a while without incident (also used in JDT core and platform resources), so I&#39;ve requested it be activated for eclipse.platform.ui.and eclipse.platform.runtime.&#xC2; This won&#39;t effect any committer&#39;s main deve... eclipse.platform.ua for a while without incident (also used in JDT core and platform resources), so I've requested it be activated for eclipse.platform.ui.and eclipse.platform.runtime. This won't effect any committer's main development workflow, but it will 1) make it available to committers that would like more reviews of some fixes and 2) make it available to contributors (which over time as it is adopted will make Contributor Days even easier).

I'll update http://wiki.eclipse.org/Platform_UI/How_to_Contribute when it's done.
BugÂ401544 - Update Platform UI how to contribute page

PW

--
Paul Webster
Hi floor. Make me a sammich! - GIR ]]> Fri, 22 Feb 2013 16:03:50 GMT http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01697.html pwebster@xxxxxxx (Paul Webster) Re: [platform-core-dev] Testing the Eclipse Editor component logic http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01696.html Daniel Megert murmured on Yakatit 4, 2005: Yay ! Woah, thanks a lot&#xC2;! That's pretty much exactly what I was looking for! Because of the stability approach of those tests (which I surmise are not really released, and even more probably don't have the same s... Daniel Megert murmured on Yakatit 4, 2005: > We don't have headless tests for UI components. There are several tests > for the model (document and file buffer tests) and then tests that > directly interact with either the viewer or the editor. Yay ! > You can either get all available Eclipse SDK tests from our download page, > e.g. > http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M5a-201302041400/#JUnitPlugin > or you can take a closer look at the Platform Text test projects (those > who end with ".tests"): > http://git.eclipse.org/c/platform/eclipse.platform.text.git/tree/ Woah, thanks a lotÂ! That's pretty much exactly what I was looking for! Because of the stability approach of those tests (which I surmise are not really released, and even more probably don't have the same stability goals as the Eclipse platform release itself), I may have to reproduce some of this, but in any case, the architecture is inspirational. Very cool to have had your input on this, -- FG ]]> Fri, 15 Feb 2013 10:18:10 GMT http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01696.html francois.garillot@xxxxxxx (FranÃois Garillot) Re: [platform-core-dev] Testing the Eclipse Editor component logic http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01695.html We don't have headless tests for UI components. There are several tests for the model (document and file buffer tests) and then tests that directly interact with either the viewer or the editor. You can either get all available Eclipse SDK tests from our d... We don't have headless tests for UI components. There are several tests for the model (document and file buffer tests) and then tests that directly interact with either the viewer or the editor.

You can either get all available Eclipse SDK tests from our download page, e.g. http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M5a-201302041400/#JUnitPlugin or you can take a closer look at the Platform Text test projects (those who end with ".tests"):
http://git.eclipse.org/c/platform/eclipse.platform.text.git/tree/

Dani

From: francois.garillot@xxxxxxxxxxxx (François Garillot)
To: platform-core-dev@xxxxxxxxxxx,
Date: 08.02.2013 15:19
Subject: [platform-core-dev] Testing the Eclipse Editor component logic




Hello,

I have a question about unit testing the Eclipse text editor framework,
that may or may not be finding the right outlet in this mailing
list. Feel free to point me to better options.

I'm working on a plugin which editor augments on the existing JDT editor
using aspects.

Now, Eclipse text editors that derive from AbstractTextEditor are
organized in clear components, following an MVC architecture. Those
components are then accessed through precise paths,
e.g. reconciliation. You can find one example of a custom reconciler and
the assumptions it can (and does) use on the behavior of the editor
here:

http://blog.ankursharma.org/2009/08/adding-spellchecking-to-custom-editors_19.html

I'd like to write headless unit tests against those assumptions, that
would check that my weaving through aspects has not broken anything along
the way. For example, in the case of reconciliation, I would like to
open an editor, input some incorrect content (with respect to some
reconciliation strategy), wait for a while, and check that Problems are
indeed reported : that would ensure that I haven't broken any essential
part of the reconciliation mechanism along the way.

Note that which problems are reported, or how they would be signaled to
the user in a UI component doesn't concern me, here. I want to test that
my swapping a SourceViewer for a custom one through aspects doesn't break
editor logic, /not/ my specific reconciliation strategy. In fact, I'd
probably mock it for that test. Moreover, the UI testing, being
presumably not runnable in a headless fashion, is beyond the scope of my
question.

It seems this should be easy to do if the appropriate structures
existed. Is there any test framework in sync with Eclipse's
architectural assumptions that would let me do what I have in mind ?
Such mocks would have but to reproduce the Eclipse editor workflows.
Surely this would be among Eclipse's own unit tests, right ? ... though
I can't seem to find anything of the sort. Any ideas ?

--
FG


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

]]> Mon, 11 Feb 2013 11:08:21 GMT http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01695.html daniel_megert@xxxxxxx (Daniel Megert) [platform-core-dev] Testing the Eclipse Editor component logic http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01694.html Hello, I have a question about unit testing the Eclipse text editor framework, that may or may not be finding the right outlet in this mailing list. Feel free to point me to better options. I'm working on a plugin which editor augments on the existing JDT ... Hello, I have a question about unit testing the Eclipse text editor framework, that may or may not be finding the right outlet in this mailing list. Feel free to point me to better options. I'm working on a plugin which editor augments on the existing JDT editor using aspects. Now, Eclipse text editors that derive from AbstractTextEditor are organized in clear components, following an MVC architecture. Those components are then accessed through precise paths, e.g. reconciliation. You can find one example of a custom reconciler and the assumptions it can (and does) use on the behavior of the editor here: http://blog.ankursharma.org/2009/08/adding-spellchecking-to-custom-editors_19.html I'd like to write headless unit tests against those assumptions, that would check that my weaving through aspects has not broken anything along the way. For example, in the case of reconciliation, I would like to open an editor, input some incorrect content (with respect to some reconciliation strategy), wait for a while, and check that Problems are indeed reported : that would ensure that I haven't broken any essential part of the reconciliation mechanism along the way. Note that which problems are reported, or how they would be signaled to the user in a UI component doesn't concern me, here. I want to test that my swapping a SourceViewer for a custom one through aspects doesn't break editor logic, /not/ my specific reconciliation strategy. In fact, I'd probably mock it for that test. Moreover, the UI testing, being presumably not runnable in a headless fashion, is beyond the scope of my question. It seems this should be easy to do if the appropriate structures existed. Is there any test framework in sync with Eclipse's architectural assumptions that would let me do what I have in mindÂ? Such mocks would have but to reproduce the Eclipse editor workflows. Surely this would be among Eclipse's own unit tests, right ? ... though I can't seem to find anything of the sort. Any ideasÂ? -- FG ]]> Fri, 08 Feb 2013 14:19:48 GMT http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01694.html francois.garillot@xxxxxxx (FranÃois Garillot)