You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@ctakes.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/07/17 00:52:20 UTC

[jira] [Commented] (CTAKES-386) Remove all .classpath and.project files

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

ASF subversion and git services commented on CTAKES-386:
--------------------------------------------------------

Commit 1753005 from [~lewismc] in branch 'ctakes/trunk'
[ https://svn.apache.org/r1753005 ]

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