ctakes-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Joseph Masanz (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CTAKES-282) Dirty on check-out in Eclipse
Date Fri, 24 Mar 2017 20:16:41 GMT

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

James Joseph Masanz resolved CTAKES-282.
       Resolution: Fixed
    Fix Version/s: 4.0.0

I do not see any .project, .classpath, or .settings in trunk. Closing this issue. Thanks for
committing the changes.

> 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

View raw message