ctakes-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Eckart de Castilho (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CTAKES-282) Dirty on check-out in Eclipse
Date Tue, 21 Jun 2016 21:01:01 GMT

    [ https://issues.apache.org/jira/browse/CTAKES-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342678#comment-15342678

Richard Eckart de Castilho commented on CTAKES-282:

So before I solve this by deleting the Eclipse metadata from the repository and adding it
to svn-ignore... would anybody object to this? Is anybody actually keen on keeping these files
in SVN? Mind, if the files are removed, then everybody with a locally checked out version
of cTAKES that is in a Eclipse workspace will have to manually remove cTAKES from the workspace
and re-import it.

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

View raw message