Mailing-List: contact notifications-help@ctakes.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ctakes.apache.org
Date: Fri, 24 Mar 2017 20:16:41 +0000 (UTC)
From: "James Joseph Masanz (JIRA)" <jira@apache.org>
To: notifications@ctakes.apache.org
Message-ID: <JIRA.12691280.1390759297000.116802.1490386601739@Atlassian.JIRA>
In-Reply-To: <JIRA.12691280.1390759297000@Atlassian.JIRA>
References: <JIRA.12691280.1390759297000@Atlassian.JIRA> <JIRA.12691280.1390759297366@jira-lw-us.apache.org>
Subject: [jira] [Closed] (CTAKES-282) Dirty on check-out in Eclipse
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 24 Mar 2017 20:16:46 -0000


     [ https://issues.apache.org/jira/browse/CTAKES-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Joseph Masanz closed CTAKES-282.
--------------------------------------

> Dirty on check-out in Eclipse
> -----------------------------
>
>                 Key: CTAKES-282
>                 URL: https://issues.apache.org/jira/browse/CTAKES-282
>             Project: cTAKES
>          Issue Type: Bug
>            Reporter: Richard Eckart de Castilho
>            Priority: Minor
>             Fix For: 4.0.0
>
>
> When I check out cTAKES and import it into Eclipse (4.3) most of the modules appear dirty. The reason for this is that Eclipse metadata files from the (.settings folder, .project file, etc) are maintained in SVN.
> The situation could be fixed not maintaining the following files in SVN (these are automatically set up properly by m2e based on the pom.xml files:
> * .project
> * .settings/org.eclipse.core.resources.prefs
> * .settings/org.eclipse.m2e.core.prefs
> It should not be a problem to continue maintaining .settings/org.eclipse.jdt.core.prefs in the SVN - actually, having this in can be quite useful and its contents are not regenerated from the pom.xml.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)