[VOTE] Release UIMA-DUCC 1.0.0 RC5

[Jaroslaw Cwiklik <ui...@gmail.com>]

Hi,

the fifth release candidate of the sandbox project Apache UIMA DUCC v1.0.0
is ready for voting.

Issues fixed in RC5:

1) Fixed NOTICE and LICENSE files
2) Modified README and RELEASE_NOTES
3) DUCC orchestrtor (OR) ignoring ducc.properties specification of
ducc.jd.host.memory.size
4) Add getLogger() to each DUCC daemon component
5) Refactor DUCC ResourceManagerComponent to avoid NPE
6) Change DUCCs Camel autostart to false
7) Refactor DUCC JmxAgent to allow daemon to start on jmx failure
8) Fix DUCC main pom to use parent-pom maven-changes-plugin
9) Upgrade DUCC parent-pom to use the latest parent-pom v.8
10)UIMA DUCC assembly scrip tries to copy INSTALL file which doesnt exist



DUCC stands for Distributed UIMA Cluster Computing. DUCC is a cluster
management system providing tooling, management, and scheduling facilities
to automate the scale-out of applications written to the UIMA framework.
Core UIMA provides a generalized framework for applications that process
unstructured information such as human language, but does not provide a
scale-out mechanism. UIMA-AS provides a scale-out mechanism to distribute
UIMA pipelines over a cluster of computing resources, but does not provide
job or cluster management of the resources. DUCC defines a formal job model
that closely maps to a standard UIMA pipeline. Around this job model DUCC
provides cluster management services to automate the scale-out of UIMA
pipelines over computing clusters.

The Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapacheuima-1000/org/apache/uima/

The source and binary zip/tars are here:
http://people.apache.org/~cwiklik/releases/uima-ducc/1.0.0/RC5/

The SVN Tag Checkout:
http://svn.apache.org/repos/asf/uima/sandbox/uima-ducc/tags/uima-ducc-1.0.0/

See: http://uima.apache.org/testing-builds.html for instructions how to
test release candidate.

Please vote on release:

[ ] +1 OK to release
[ ]  0 Don't care
[ ] -1 Not OK to release, because ...

Re: [VOTE] Release UIMA-DUCC 1.0.0 RC5

[Jim Challenger <ch...@gmail.com>]

Some responses below.

On 1/15/14 3:33 PM, Marshall Schor wrote:
> Some things to look at:
>
> 1) The parent-pom rat excludes is too broad.  e.g: no checks for tex files -
> this doesn't seem right.
>
> 2) parent-pom rat excludes excludes non-existent files, e.g.
> src/main/resources/docbook-shared/titlepage/*.xsl, .pydevproject
>
> 3) latex build has some errors.
>
>    It looks like the duccbook.tex and the installation.tex books each have
> "latex  " run 3 times in sequence on them (a total of 6 invocations).  The last
> run still shows errors, including undefined references.  There are also other
> kinds of errors, such as
>    cannot determine size of graphic in images,
>    problem with 'list' environment
   References fixed.

  The message about the images can be ignored- they're just warnings and 
Tex/Latex tend to be
  quite wordy and hard to quite down.  The generated HTML looks correct.

Looks like the list problem is in a section authored by Lou so I'll have 
to defer to him as I'm not
sure what the intention was here.
>
> 4) in the duccbook INSTALL file, the name of UIMA is spelled UIMATM - which I
> think is a problem with the "trademark" approach.
This is an artifact of the pdf2text translation, nothing we can do about 
it.  If it's unacceptable we'll
have to pull it andsupply just pdf and html as this is done out of our 
control.  The intention of the INSTALL file
is a convenience so people can get to it without a browser or pdf 
viewer, but it's not really critical.
>
> 5) duccbook publication dates are formatted unconventionally, so that dates like
> January 7, 2014, are formatted as 07-01-2014 which would likely be taken to be
> July 1st, 2014.
Fixed.
>
> -Marshall

Re: [VOTE] Release UIMA-DUCC 1.0.0 RC5

[Marshall Schor <ms...@schor.com>]

running uima-ducc-duccdocs with the RAT exclude for **/*.tex removed, didn't
show any missing license headers :-)

-Marshall
On 1/15/2014 3:33 PM, Marshall Schor wrote:
> Some things to look at:
>
> 1) The parent-pom rat excludes is too broad.  e.g: no checks for tex files - 
> this doesn't seem right.
>
> 2) parent-pom rat excludes excludes non-existent files, e.g.
> src/main/resources/docbook-shared/titlepage/*.xsl, .pydevproject
>
> 3) latex build has some errors.
>
>   It looks like the duccbook.tex and the installation.tex books each have
> "latex  " run 3 times in sequence on them (a total of 6 invocations).  The last
> run still shows errors, including undefined references.  There are also other
> kinds of errors, such as
>   cannot determine size of graphic in images,
>   problem with 'list' environment
>
> 4) in the duccbook INSTALL file, the name of UIMA is spelled UIMATM - which I
> think is a problem with the "trademark" approach.
>
> 5) duccbook publication dates are formatted unconventionally, so that dates like
> January 7, 2014, are formatted as 07-01-2014 which would likely be taken to be
> July 1st, 2014.
>
> -Marshall
>

Re: [VOTE] Release UIMA-DUCC 1.0.0 RC5

[Marshall Schor <ms...@schor.com>]

Some things to look at:

1) The parent-pom rat excludes is too broad.  e.g: no checks for tex files - 
this doesn't seem right.

2) parent-pom rat excludes excludes non-existent files, e.g.
src/main/resources/docbook-shared/titlepage/*.xsl, .pydevproject

3) latex build has some errors.

  It looks like the duccbook.tex and the installation.tex books each have
"latex  " run 3 times in sequence on them (a total of 6 invocations).  The last
run still shows errors, including undefined references.  There are also other
kinds of errors, such as
  cannot determine size of graphic in images,
  problem with 'list' environment

4) in the duccbook INSTALL file, the name of UIMA is spelled UIMATM - which I
think is a problem with the "trademark" approach.

5) duccbook publication dates are formatted unconventionally, so that dates like
January 7, 2014, are formatted as 07-01-2014 which would likely be taken to be
July 1st, 2014.

-Marshall

Re: [VOTE] Release UIMA-DUCC 1.0.0 RC5

[Marshall Schor <ms...@schor.com>]

Would be good to run a spell checker on the source files of duccbooks - I've run
across several misspellings.  here's one:
Figure 5.2: ISeriveStatistics Interface

duccbook missing parts at the end:

section 16.4 Interfaces has a placeholder,

Sections 17.2 and onwards are missing their content.  Perhaps these should be
"commented out" for now?

-Marshall

Re: [VOTE] Release UIMA-DUCC 1.0.0 RC5

[Jim Challenger <ch...@gmail.com>]

I see ... I've been accessing the docs from the various DUCC web 
servers.  Putting HTML in the [root]/docs directory is relatively recent 
so I'd missed the directory mismatch.  Fixed.

Jim
On 1/16/14 2:40 PM, Marshall Schor wrote:
> On 1/16/2014 1:49 PM, Jim Challenger wrote:
>> On 1/15/14 5:02 PM, Marshall Schor wrote:
>>> fixups for the documentation:
>>>
>>> 1) Link in duccbook to javadocs has a typo, and is therefore broken; it's
>>> written ... docs/d/apidocs/index.html, but should be ... docs/d/api/index.html
>> Marshall, the link isn't broken, I just tested it and I got to it just fine!
>> Where are you looking?
> I took the binary distribution artifact and untarred it.  It produced a
> directory structure:
> docs/d/api/ ...
>
> There is no apidocs directory.
>
> -Marshall
>
>>> 2) Submit command, --specification : has:
>>> This file may then be used to submit the job (rather than providing all the
>>> parameters directory to submit).
>>>
>>> should be
>>> This file may then be used to submit the job (rather than providing all the
>>> parameters directly to submit)
>>>
>>> 3) The webpage setup produced by the build for the html duccbook result in the
>>> Chrome browser "forgetting" where it was:  If you click on a link that takes you
>>> to some other spot in the documentation (which works), and then you press the
>>> back button, it goes to the top of the file, instead of going back to where it
>>> was.  Firefox seems to be OK.
>>>
>>> Chrome too, works OK (e.g, it remembers where links came from) on other pages
>>> generated with other tools, such as the uima.apache.org web site.  I couldn't
>>> figure out why it didn't work on the duccbook file.
>> Sounds like a bug in Chrome !  Works fine also in Safari and Opera.
>>> -Marshall
>>>
>>>
>>

Re: [VOTE] Release UIMA-DUCC 1.0.0 RC5

[Marshall Schor <ms...@schor.com>]

On 1/16/2014 1:49 PM, Jim Challenger wrote:
>
> On 1/15/14 5:02 PM, Marshall Schor wrote:
>> fixups for the documentation:
>>
>> 1) Link in duccbook to javadocs has a typo, and is therefore broken; it's
>> written ... docs/d/apidocs/index.html, but should be ... docs/d/api/index.html
>
> Marshall, the link isn't broken, I just tested it and I got to it just fine! 
> Where are you looking?

I took the binary distribution artifact and untarred it.  It produced a
directory structure:
docs/d/api/ ...

There is no apidocs directory.

-Marshall

>>
>> 2) Submit command, --specification : has:
>> This file may then be used to submit the job (rather than providing all the
>> parameters directory to submit).
>>
>> should be
>> This file may then be used to submit the job (rather than providing all the
>> parameters directly to submit)
>>
>> 3) The webpage setup produced by the build for the html duccbook result in the
>> Chrome browser "forgetting" where it was:  If you click on a link that takes you
>> to some other spot in the documentation (which works), and then you press the
>> back button, it goes to the top of the file, instead of going back to where it
>> was.  Firefox seems to be OK.
>>
>> Chrome too, works OK (e.g, it remembers where links came from) on other pages
>> generated with other tools, such as the uima.apache.org web site.  I couldn't
>> figure out why it didn't work on the duccbook file.
>
> Sounds like a bug in Chrome !  Works fine also in Safari and Opera.
>>
>> -Marshall
>>
>>
>
>

Re: [VOTE] Release UIMA-DUCC 1.0.0 RC5

[Jim Challenger <ch...@gmail.com>]

On 1/15/14 5:02 PM, Marshall Schor wrote:
> fixups for the documentation:
>
> 1) Link in duccbook to javadocs has a typo, and is therefore broken; it's
> written ... docs/d/apidocs/index.html, but should be ... docs/d/api/index.html

Marshall, the link isn't broken, I just tested it and I got to it just 
fine!  Where are you looking?
>
> 2) Submit command, --specification : has:
> This file may then be used to submit the job (rather than providing all the
> parameters directory to submit).
>
> should be
> This file may then be used to submit the job (rather than providing all the
> parameters directly to submit)
>
> 3) The webpage setup produced by the build for the html duccbook result in the
> Chrome browser "forgetting" where it was:  If you click on a link that takes you
> to some other spot in the documentation (which works), and then you press the
> back button, it goes to the top of the file, instead of going back to where it
> was.  Firefox seems to be OK.
>
> Chrome too, works OK (e.g, it remembers where links came from) on other pages
> generated with other tools, such as the uima.apache.org web site.  I couldn't
> figure out why it didn't work on the duccbook file.

Sounds like a bug in Chrome !  Works fine also in Safari and Opera.
>
> -Marshall
>
>

Re: [VOTE] Release UIMA-DUCC 1.0.0 RC5

[Marshall Schor <ms...@schor.com>]

fixups for the documentation:

1) Link in duccbook to javadocs has a typo, and is therefore broken; it's
written ... docs/d/apidocs/index.html, but should be ... docs/d/api/index.html

2) Submit command, --specification : has:
This file may then be used to submit the job (rather than providing all the
parameters directory to submit).

should be
This file may then be used to submit the job (rather than providing all the
parameters directly to submit)

3) The webpage setup produced by the build for the html duccbook result in the
Chrome browser "forgetting" where it was:  If you click on a link that takes you
to some other spot in the documentation (which works), and then you press the
back button, it goes to the top of the file, instead of going back to where it
was.  Firefox seems to be OK. 

Chrome too, works OK (e.g, it remembers where links came from) on other pages
generated with other tools, such as the uima.apache.org web site.  I couldn't
figure out why it didn't work on the duccbook file.

-Marshall

Re: [VOTE] Release UIMA-DUCC 1.0.0 RC5

[Marshall Schor <ms...@schor.com>]

The source-release contains an issuesFixed folder with content which is
incorrect - it's issues for another project.

I thought this was going to be removed for this release?

-Marshall

Re: [VOTE] Release UIMA-DUCC 1.0.0 RC5

[Marshall Schor <ms...@schor.com>]

In the binary distribution, the jar: lib/uima-ducc-cli.jar is missing the
LICENSE / NOTICE in its METADATA.  Since these are inserted by the "standard"
build process, I'm guess this file has some custom build process that's
forgetting to put this info in.

-Marshall

Re: [VOTE] Release UIMA-DUCC 1.0.0 RC5

[Marshall Schor <ms...@schor.com>]

Notice file in DUCC jars -- might be missing the part that goes there if you
moved the original copyright by IBM from the files to the NOTICE.  (see for
example, the Notice file used for UIMA).

This page http://www.apache.org/dev/licensing-howto.html#mod-notice says:

Copyright notifications which have been relocated
<http://www.apache.org/legal/src-headers.html#headers> from source files (rather
than removed) must be preserved in |NOTICE|.

-Marshall