ctakes-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lewis John McGibbney (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CTAKES-386) Remove all .classpath and.project files
Date Sun, 17 Jul 2016 01:31:20 GMT

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

Lewis John McGibbney resolved CTAKES-386.
-----------------------------------------
    Resolution: Fixed

Fixed in trunk 

r1753005 | lewismc | 2016-07-16 17:51:28 -0700 (Sat, 16 Jul 2016) | 1 line

CTAKES-386 Remove all .classpath and.project files

> Remove all .classpath and.project files
> ---------------------------------------
>
>                 Key: CTAKES-386
>                 URL: https://issues.apache.org/jira/browse/CTAKES-386
>             Project: cTAKES
>          Issue Type: Improvement
>    Affects Versions: 3.2.2
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>              Labels: build
>             Fix For: 3.2.3
>
>         Attachments: CTAKES-386.patch
>
>
> Right now the codebase is absolutely peppered with project .classpath and .project. This
means that when attempting to build a fresh project via mvn eclipse:eclipse it edits all of
those files making it very difficult to submit a patch and track local changes. I propose
to remove them all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message