You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <ui...@incubator.apache.org> on 2006/11/13 17:33:38 UTC
[jira] Created: (UIMA-4) Set svn:eol-style and other flags on
appropriate files
Set svn:eol-style and other flags on appropriate files
------------------------------------------------------
Key: UIMA-4
URL: http://issues.apache.org/jira/browse/UIMA-4
Project: UIMA
Issue Type: Task
Reporter: Marshall Schor
Priority: Minor
Construct an appropriate shell script, and run it to set the eol-style and keyword and mime-type for files in SVN.
For test files, set eol-style to LF. For normal sources, set to "native".
Suggest we have an apache-tools project (under top level, no need for branches / tags?) to hold these kinds of support tools - or is there a better place for these?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Created: (UIMA-4) Set svn:eol-style and other flags on
appropriate files
Posted by Thilo Goetz <tw...@gmx.de>.
Marshall Schor (JIRA) wrote:
> Set svn:eol-style and other flags on appropriate files
> ------------------------------------------------------
>
> Key: UIMA-4
> URL: http://issues.apache.org/jira/browse/UIMA-4
> Project: UIMA
> Issue Type: Task
> Reporter: Marshall Schor
> Priority: Minor
>
>
> Construct an appropriate shell script, and run it to set the eol-style and keyword and mime-type for files in SVN.
> For test files, set eol-style to LF. For normal sources, set to "native".
>
> Suggest we have an apache-tools project (under top level, no need for branches / tags?) to hold these kinds of support tools - or is there a better place for these?
>
-1 on creating a script that actually *sets* the svn properties. We can
easily set the svn properties recursively in Eclipse for the one-time
setup we need. +1 on have a script that *checks* that eol properties
are set. We've had too much grief with EOL problems to entrust this to
a script.
--Thilo
[jira] Updated: (UIMA-4) Set svn:eol-style and other flags on
appropriate files
Posted by "Michael Baessler (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Baessler updated UIMA-4:
--------------------------------
Component/s: Build, Packaging and Test
> Set svn:eol-style and other flags on appropriate files
> ------------------------------------------------------
>
> Key: UIMA-4
> URL: https://issues.apache.org/jira/browse/UIMA-4
> Project: UIMA
> Issue Type: Task
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Priority: Minor
>
> Construct an appropriate shell script, and run it to check the eol-style and keyword and mime-type for files in SVN.
> For test files, check that eol-style is LF. For normal sources, check eol-style is "native".
> Suggest we have an apache-tools project (under top level, no need for branches / tags?) to hold these kinds of support tools - or is there a better place for these?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-4) Set svn:eol-style and other flags on
appropriate files
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/UIMA-4?page=all ]
Marshall Schor updated UIMA-4:
------------------------------
Description:
Construct an appropriate shell script, and run it to check the eol-style and keyword and mime-type for files in SVN.
For test files, check that eol-style is LF. For normal sources, check eol-style is "native".
Suggest we have an apache-tools project (under top level, no need for branches / tags?) to hold these kinds of support tools - or is there a better place for these?
was:
Construct an appropriate shell script, and run it to set the eol-style and keyword and mime-type for files in SVN.
For test files, set eol-style to LF. For normal sources, set to "native".
Suggest we have an apache-tools project (under top level, no need for branches / tags?) to hold these kinds of support tools - or is there a better place for these?
> Set svn:eol-style and other flags on appropriate files
> ------------------------------------------------------
>
> Key: UIMA-4
> URL: http://issues.apache.org/jira/browse/UIMA-4
> Project: UIMA
> Issue Type: Task
> Reporter: Marshall Schor
> Priority: Minor
>
> Construct an appropriate shell script, and run it to check the eol-style and keyword and mime-type for files in SVN.
> For test files, check that eol-style is LF. For normal sources, check eol-style is "native".
> Suggest we have an apache-tools project (under top level, no need for branches / tags?) to hold these kinds of support tools - or is there a better place for these?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (UIMA-4) Set svn:eol-style and other flags on
appropriate files
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor closed UIMA-4.
-----------------------------
Resolution: Fixed
> Set svn:eol-style and other flags on appropriate files
> ------------------------------------------------------
>
> Key: UIMA-4
> URL: https://issues.apache.org/jira/browse/UIMA-4
> Project: UIMA
> Issue Type: Task
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Priority: Minor
>
> Construct an appropriate shell script, and run it to check the eol-style and keyword and mime-type for files in SVN.
> For test files, check that eol-style is LF. For normal sources, check eol-style is "native".
> Suggest we have an apache-tools project (under top level, no need for branches / tags?) to hold these kinds of support tools - or is there a better place for these?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.