headers
Eddie Epstein (JIRA | 2 Sep 2008 15:19
Picon
Favicon

[jira] Commented: (UIMA-1147) Merge uima-as-post1st branch with the uima-as SVN trunk


    [
https://issues.apache.org/jira/browse/UIMA-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627666#action_12627666
] 

Eddie Epstein commented on UIMA-1147:
-------------------------------------

Yes, but 1131 is still open. See last comment on that issue.

> Merge uima-as-post1st branch with the uima-as SVN trunk
> -------------------------------------------------------
>
>                 Key: UIMA-1147
>                 URL: https://issues.apache.org/jira/browse/UIMA-1147
>             Project: UIMA
>          Issue Type: Task
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>         Attachments: uimaj-as-activemq-UIMA-1147-patch.txt, uimaj-as-core-UIMA-1147-patch-02.txt,
uimaj-as-core-UIMA-1147-patch.txt, uimaj-as-jms-UIMA-1147-patch.txt
>
>
> Merge the uima-as branch with the SVN uima-as trunk

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Marshall Schor | 2 Sep 2008 16:45

Re: [jira] Commented: (UIMA-1147) Merge uima-as-post1st branch with the uima-as SVN trunk

I believe that if you say UIMA-1131 instead of 1131 in your comment,
Jira will automagically convert it into a working hyperlink to the issue
:-)

-Marshall

Eddie Epstein (JIRA) wrote:
>     [
https://issues.apache.org/jira/browse/UIMA-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627666#action_12627666
] 
>
> Eddie Epstein commented on UIMA-1147:
> -------------------------------------
>
> Yes, but 1131 is still open. See last comment on that issue.
>
>   
>> Merge uima-as-post1st branch with the uima-as SVN trunk
>> -------------------------------------------------------
>>
>>                 Key: UIMA-1147
>>                 URL: https://issues.apache.org/jira/browse/UIMA-1147
>>             Project: UIMA
>>          Issue Type: Task
>>          Components: Async Scaleout
>>            Reporter: Jerry Cwiklik
>>            Assignee: Jerry Cwiklik
>>         Attachments: uimaj-as-activemq-UIMA-1147-patch.txt, uimaj-as-core-UIMA-1147-patch-02.txt,
uimaj-as-core-UIMA-1147-patch.txt, uimaj-as-jms-UIMA-1147-patch.txt
>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor (JIRA | 2 Sep 2008 19:31
Picon
Favicon

[jira] Commented: (UIMA-1163) set svn:eol-style to native for source files in UIMA project


    [
https://issues.apache.org/jira/browse/UIMA-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627758#action_12627758
] 

Marshall Schor commented on UIMA-1163:
--------------------------------------

Among the kinds of files in our svn repository are scripts.  Some of these are intended for windows (they end
in .cmd or .bat).  Others are intended to run on linux or other unix (they end in .sh).

How should the svn:eol-style be set for these?

Here are some choices:

1) no setting at all
2) "native"
3) CRLF for the Windows files, LF for the *nix files

Do we have a goal of having the line endings for the scripts correspond to the Operating System category
(windows or *nix)?

It may be true that most (all?) target OSs don't care about this.  It might be "safer" though to have these match.

If we want them to match, then 2) above fails - because if we "build" the distribution on a Windows system, it
would have CRLF for all files, and if we build on a *nix system, it would have LF for all files.

1) and 3) would work for these, provided if choosing 1) we insured the line endings were the right "kind" for
the file.  This seems easy to break, though - I think most of our "mixed line endings" situations were caused
by copy /paste actions in the past (perhaps copying in a license header, etc.).
(Continue reading)

Permalink | Reply | 1 comment |
headers
Eddie Epstein (JIRA | 2 Sep 2008 23:03
Picon
Favicon

[jira] Commented: (UIMA-1163) set svn:eol-style to native for source files in UIMA project


    [
https://issues.apache.org/jira/browse/UIMA-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627810#action_12627810
] 

Eddie Epstein commented on UIMA-1163:
-------------------------------------

CRLF line endings definitely break Unix shell scripts, so they all should be marked as per #3.

> set svn:eol-style to native for source files in UIMA project
> ------------------------------------------------------------
>
>                 Key: UIMA-1163
>                 URL: https://issues.apache.org/jira/browse/UIMA-1163
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>    Affects Versions: 2.2.2
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>
> set the svn:eol-style to native for java source files in the UIMA project.  (Other sandbox projects may
also want to do similar things, and the uimaCPP project, and the site project).
> Don't set this for scripts - the ones that are intended to run on windows probably can have either line
ending style, but I think the ones that run on the various linuxes need the unix style.  This is so that
extracts for builds done on a windows machine can properly build a linux distribution.
> Don't set this for test data - some UTF-16 or UTF-8 test data may have things intentionally present that
might look like line endings, but are not, and should not be disturbed by checkout.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Burn Lewis | 3 Sep 2008 15:50
Picon

Re: [jira] Commented: (UIMA-1163) set svn:eol-style to native for source files in UIMA project

+1 for #3 since it means we only have to set the appropriate eol-style when
adding new scripts while #1 means we in addition have to check on every
update that the line-ends are correct.

On Tue, Sep 2, 2008 at 1:31 PM, Marshall Schor (JIRA) <
uima-dev@...> wrote:

>
>    [
> https://issues.apache.org/jira/browse/UIMA-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627758#action_12627758]
>
> Marshall Schor commented on UIMA-1163:
> --------------------------------------
>
> Among the kinds of files in our svn repository are scripts.  Some of these
> are intended for windows (they end in .cmd or .bat).  Others are intended to
> run on linux or other unix (they end in .sh).
>
> How should the svn:eol-style be set for these?
>
> Here are some choices:
>
> 1) no setting at all
> 2) "native"
> 3) CRLF for the Windows files, LF for the *nix files
>
> Do we have a goal of having the line endings for the scripts correspond to
> the Operating System category (windows or *nix)?
>
> It may be true that most (all?) target OSs don't care about this.  It might
(Continue reading)

Permalink | Reply | 0 comments |
headers
Burn Lewis (JIRA | 3 Sep 2008 16:27
Picon
Favicon

[jira] Commented: (UIMA-1117) Simple aggregate hangs when get a delegate error on an input CAS


    [
https://issues.apache.org/jira/browse/UIMA-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628015#action_12628015
] 

Burn Lewis commented on UIMA-1117:
----------------------------------

Although this patch does not appear to have been applied, the problem appears to have been fixed after the
merge of the branch.  So should we add the test case?  It may be the only one that doesn't include a CM or CR.

> Simple aggregate hangs when get a delegate error on an input CAS
> ----------------------------------------------------------------
>
>                 Key: UIMA-1117
>                 URL: https://issues.apache.org/jira/browse/UIMA-1117
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.2.2
>            Reporter: Burn Lewis
>             Fix For: 2.3AS
>
>         Attachments: UIMA-1117.patch, uimaj-as-core-UIMA-1117.txt
>
>
> If continueOnRetryFailure is true for a delegate that reports an error, the CAS continues to the end of the
aggregate but is not returned to the client or to the pool.  When it is false the exception is returned
correctly.  This only fails for original input CASes ... error handling works correctly for CASes created
by a CR or CM inside the aggregate.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor | 3 Sep 2008 22:59

Re: [VOTE] Release uimacpp-2.2.2-03 as uimacpp-2.2.2-incubating

+1.  I note that the process being followed with respect to SVN is
building the release candidate on a stable branch, without "tagging"
until the release candidate is fully approved.

This process is used by some other apache projects, and is one of the
processes described in Apache Release best practices (
http://incubator.apache.org/guides/releasemanagement.html#best-practice )

When this process is used, the SVN "release candidate" is uniquely
identified by the branch name (in this case, it is uimacpp-2.2.2) *plus*
the SVN revision number, which for release candidate 03 is 688195.

-Marshall

Eddie Epstein wrote:
> All of the issues raised during discussion of the last release
> candidate (http://markmail.org/message/z5d4o3hempxeo4sw)
> have been addressed.
>
> The release artifacts and RAT results are available on
> p.a.o/~eae/uimacpp-release-candidates/2.2.2/03/
>
> Please cast your vote:
>
> [ ] +1 release candidate uimacpp-2.2.2-incubating RC03 is ready and
> can be released
> [ ] 0 don't care
> [ ] -1 don't release yet, I found some more issues
>
> Thanks, Eddie
(Continue reading)

Permalink | Reply | 1 comment |
headers
Eddie Epstein | 3 Sep 2008 23:06
Picon

Re: [VOTE] Release uimacpp-2.2.2-03 as uimacpp-2.2.2-incubating

my +1.

Marshall, thanks for the clarification of SVN handling for this release.

Eddie

On Wed, Sep 3, 2008 at 4:59 PM, Marshall Schor <msa@...> wrote:

> +1.  I note that the process being followed with respect to SVN is
> building the release candidate on a stable branch, without "tagging"
> until the release candidate is fully approved.
>
> This process is used by some other apache projects, and is one of the
> processes described in Apache Release best practices (
> http://incubator.apache.org/guides/releasemanagement.html#best-practice )
>
> When this process is used, the SVN "release candidate" is uniquely
> identified by the branch name (in this case, it is uimacpp-2.2.2) *plus*
> the SVN revision number, which for release candidate 03 is 688195.
>
>
> -Marshall
>
> Eddie Epstein wrote:
> > All of the issues raised during discussion of the last release
> > candidate (http://markmail.org/message/z5d4o3hempxeo4sw)
> > have been addressed.
> >
> > The release artifacts and RAT results are available on
> > p.a.o/~eae/uimacpp-release-candidates/2.2.2/03/
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor (JIRA | 3 Sep 2008 23:11
Picon
Favicon

[jira] Commented: (UIMA-1163) set svn:eol-style to native for source files in UIMA project


    [
https://issues.apache.org/jira/browse/UIMA-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628134#action_12628134
] 

Marshall Schor commented on UIMA-1163:
--------------------------------------

This was noted in previous Jira's and already fixed - see UIMA-747 and UIMA-934

> set svn:eol-style to native for source files in UIMA project
> ------------------------------------------------------------
>
>                 Key: UIMA-1163
>                 URL: https://issues.apache.org/jira/browse/UIMA-1163
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>    Affects Versions: 2.2.2
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>
> set the svn:eol-style to native for java source files in the UIMA project.  (Other sandbox projects may
also want to do similar things, and the uimaCPP project, and the site project).
> Don't set this for scripts - the ones that are intended to run on windows probably can have either line
ending style, but I think the ones that run on the various linuxes need the unix style.  This is so that
extracts for builds done on a windows machine can properly build a linux distribution.
> Don't set this for test data - some UTF-16 or UTF-8 test data may have things intentionally present that
might look like line endings, but are not, and should not be disturbed by checkout.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Burn Lewis (JIRA | 4 Sep 2008 00:33
Picon
Favicon

[jira] Commented: (UIMA-1163) set svn:eol-style to native for source files in UIMA project


    [
https://issues.apache.org/jira/browse/UIMA-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628180#action_12628180
] 

Burn Lewis commented on UIMA-1163:
----------------------------------

FWIW the .sh files in uimaj-distr do not have the svn:executable set ... those in uima-as-distr do.  But they
all are +x in the latest build!
Except for the ones in apache-activemq-4.1.1/bin which are not executable but do have svn:executable set !??

> set svn:eol-style to native for source files in UIMA project
> ------------------------------------------------------------
>
>                 Key: UIMA-1163
>                 URL: https://issues.apache.org/jira/browse/UIMA-1163
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>    Affects Versions: 2.2.2
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>
> set the svn:eol-style to native for java source files in the UIMA project.  (Other sandbox projects may
also want to do similar things, and the uimaCPP project, and the site project).
> Don't set this for scripts - the ones that are intended to run on windows probably can have either line
ending style, but I think the ones that run on the various linuxes need the unix style.  This is so that
extracts for builds done on a windows machine can properly build a linux distribution.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane