You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ctakes.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2016/07/17 00:52:20 UTC
[jira] [Resolved] (CTAKES-386) Remove all .classpath and.project
files
[ 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
Assignee: Lewis John McGibbney
Committed @revision 1753005 in trunk.
If someone wishes to regenerate these files then they should build them locally with mvn eclipse:eclipse
> 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)