[jira] [Commented] (UIMA-6366) Spelling error in documentation
[ https://issues.apache.org/jira/browse/UIMA-6366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347879#comment-17347879 ] Richard Eckart de Castilho commented on UIMA-6366: -- Thanks :) Care to fix it with a pull request?: https://github.com/apache/uima-uimaj/blob/main/uima-docbook-overview-and-setup/src/docbook/conceptual_overview.xml > Spelling error in documentation > > > Key: UIMA-6366 > URL: https://issues.apache.org/jira/browse/UIMA-6366 > Project: UIMA > Issue Type: Documentation > Components: Documentation >Reporter: Sarthak Kathuria >Priority: Trivial > Labels: spelling > > 2.1 UIMA Introduction > Third paragraph last line: > These component analytics must interoperate and must be easily combined to > facilitate the -developed- development of UIM applications. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (UIMA-6365) Warn or fail if a primitive field is marked as a non-mandatory parameter
Richard Eckart de Castilho created UIMA-6365:
Summary: Warn or fail if a primitive field is marked as a
non-mandatory parameter
Key: UIMA-6365
URL: https://issues.apache.org/jira/browse/UIMA-6365
Project: UIMA
Issue Type: Improvement
Components: uimaFIT-Maven-Plugin
Reporter: Richard Eckart de Castilho
Fix For: 3.3.0uimaFIT
The {{mandatory}} flag on configuration parameters indicates if the target
field accepts a {{null}} value or not. For primitive fields, this is obviously
not the case. Thus, for primitive fields, {{mandatory}} must always be {{true}}
and if we want to avoid that the user actually has to specify the parameter
every time, the {{defaultValue}} must be set. That makes the parameter
effectively optional from the user's perspective.
Probably the best place to catch this is the "generate" or "enhance" goal of
the Maven plugin - which could immediately fail.
It could also be detected by uimaFIT itself at runtime, but then it would be
better just to warn (maybe warn less with high frequency).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (UIMA-6364) Generate XML descriptors for resources
Richard Eckart de Castilho created UIMA-6364: Summary: Generate XML descriptors for resources Key: UIMA-6364 URL: https://issues.apache.org/jira/browse/UIMA-6364 Project: UIMA Issue Type: Improvement Components: uimaFIT-Maven-Plugin Reporter: Richard Eckart de Castilho Fix For: 3.3.0uimaFIT It appears as if the Maven uimaFIT plugin goal "generate" (and probably also "enhance") currently only operate on analysis components. The should also work for resources and probably also for stuff such as flow controllers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-6355) Component Descriptor Editor not working 100%
[ https://issues.apache.org/jira/browse/UIMA-6355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17346828#comment-17346828 ] Richard Eckart de Castilho commented on UIMA-6355: -- Hi Andy, sounds like something to discuss on the mailing list rather than in a closed issue. My guess would be that you mix UIMA 2 and UIMA 3. The add-ons have not been updated to UIMA 3. And you cannot mix UIMAv3 JCas classes with UIMAv2 code either. > Component Descriptor Editor not working 100% > > > Key: UIMA-6355 > URL: https://issues.apache.org/jira/browse/UIMA-6355 > Project: UIMA > Issue Type: Bug > Components: Eclipse plugins >Affects Versions: 3.1.1SDK >Reporter: Andreas Korger >Priority: Major > Fix For: 3.2.0SDK > > > Hello, > i installed a complete uima framework (latest eclipse, plugin, addons, ruta, > examples) i can use the Document Analyzer on a tutorial descriptor. The > descriptor editor is available as file viewer and shows functionality BUT > does not recognize changes nor can they be saved. The file name is not shown > on the file tab. No error messages. UIMA link in eclipse Menu and JCasGen > also not available. > Thx for help, > Andy -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (UIMA-6363) When enhance goal fails the source file name is not displayed
Richard Eckart de Castilho created UIMA-6363:
Summary: When enhance goal fails the source file name is not
displayed
Key: UIMA-6363
URL: https://issues.apache.org/jira/browse/UIMA-6363
Project: UIMA
Issue Type: Bug
Components: uimaFIT-Maven-Plugin
Affects Versions: 3.2.0uimaFIT
Reporter: Richard Eckart de Castilho
The uimaFIT "enhance" goal chokes on code like this where there is a "," in a
list without an element following it:
{code}
@LanguageCapability({
"en",
"fr",
})
{code}
And unfortunately, it does so by only saying in which line/row the error
happens but the source file is simply called "UNKNOWN SOURCE" - that makes it a
bit user-unfriendly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (UIMA-6361) p2-layout-resolver upgrade required for Java 16 builds
Richard Eckart de Castilho created UIMA-6361: Summary: p2-layout-resolver upgrade required for Java 16 builds Key: UIMA-6361 URL: https://issues.apache.org/jira/browse/UIMA-6361 Project: UIMA Issue Type: Bug Components: Ruta Reporter: Richard Eckart de Castilho Fix For: 3.1.1ruta The p2-layout-resolver used by Ruta is not compatible with Java 16. To achieve compatibility, upgrade to the 1.3.0 of the resolver. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6331) uimaFIT 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6331:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (/) Copy the release artifacts from the staging spot to the dist spot in SVN
(and remove older release)
- (/) Release staging repository at {{http://repository.apache.org/}}
- (/) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (/) Merge the release branch
- (/) Update website
- (/) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (/) Copy the release artifacts from the staging spot to the dist spot in SVN
(and remove older release)
- (/) Release staging repository at {{http://repository.apache.org/}}
- (/) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (/) Merge the release branch
- (/) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
> uimaFIT 3.2.0 release
> -
>
> Key: UIMA-6331
> URL: https://issues.apache.org/jira/browse/UIMA-6331
> Project: UIMA
> Issue Type: Task
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> - (/) Close
[jira] [Resolved] (UIMA-6331) uimaFIT 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6331.
--
Fix Version/s: 3.2.0uimaFIT
Resolution: Fixed
> uimaFIT 3.2.0 release
> -
>
> Key: UIMA-6331
> URL: https://issues.apache.org/jira/browse/UIMA-6331
> Project: UIMA
> Issue Type: Task
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.2.0uimaFIT
>
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> - (/) Close the staging repository at {{http://repository.apache.org/}}
> - (/) Check out release staging svn spot
> {{https://dist.apache.org/repos/dist/dev/uima/}}
> - (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
> release staging spot
> - (/) Call for a vote including URLs for
> ** Issue list
> ** Staging repository
> ** SVN staging spot (artifacts)
> ** Git tag
> - (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
> release)
> - (/) Post vote results (sign mail using same GPG key that was used to sign
> release)
> - (/) Copy the release artifacts from the staging spot to the dist spot in
> SVN (and remove older release)
> - (/) Release staging repository at {{http://repository.apache.org/}}
> - (/) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
> prefixed with {{rel}}
> - (/) Merge the release branch
> - (/) Update website
> - (/) Post release announcement to {{annou...@apache.org}} (Cc:
> {{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
> at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign
> mail using same GPG key that was used to sign release)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (UIMA-6331) uimaFIT 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6331:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (/) Copy the release artifacts from the staging spot to the dist spot in SVN
(and remove older release)
- (/) Release staging repository at {{http://repository.apache.org/}}
- (/) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (/) Merge the release branch
- (/) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (/) Copy the release artifacts from the staging spot to the dist spot in SVN
(and remove older release)
- (/) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (/) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
> uimaFIT 3.2.0 release
> -
>
> Key: UIMA-6331
> URL: https://issues.apache.org/jira/browse/UIMA-6331
> Project: UIMA
> Issue Type: Task
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> - (/) Close
[jira] [Updated] (UIMA-6331) uimaFIT 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6331:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (/) Copy the release artifacts from the staging spot to the dist spot in SVN
(and remove older release)
- (/) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (/) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (/) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
> uimaFIT 3.2.0 release
> -
>
> Key: UIMA-6331
> URL: https://issues.apache.org/jira/browse/UIMA-6331
> Project: UIMA
> Issue Type: Task
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> - (/) Close the staging repository at
[jira] [Updated] (UIMA-6331) uimaFIT 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6331:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (/) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** Git tag
- (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (x) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (x) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
> uimaFIT 3.2.0 release
> -
>
> Key: UIMA-6331
> URL: https://issues.apache.org/jira/browse/UIMA-6331
> Project: UIMA
> Issue Type: Task
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> - (/) Close the staging repository at
[jira] [Updated] (UIMA-6331) uimaFIT 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6331:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** Git tag
- (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (x) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (x) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (x) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (x) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (x) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
> uimaFIT 3.2.0 release
> -
>
> Key: UIMA-6331
> URL: https://issues.apache.org/jira/browse/UIMA-6331
> Project: UIMA
> Issue Type: Task
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> - (/) Close the staging repository
[jira] [Updated] (UIMA-6331) uimaFIT 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6331:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (x) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (x) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (x) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (x) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (x) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (x) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
> uimaFIT 3.2.0 release
> -
>
> Key: UIMA-6331
> URL: https://issues.apache.org/jira/browse/UIMA-6331
> Project: UIMA
> Issue Type: Task
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> -
[jira] [Updated] (UIMA-6355) Component Descriptor Editor not working 100%
[ https://issues.apache.org/jira/browse/UIMA-6355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6355: - Fix Version/s: 3.2.0SDK > Component Descriptor Editor not working 100% > > > Key: UIMA-6355 > URL: https://issues.apache.org/jira/browse/UIMA-6355 > Project: UIMA > Issue Type: Bug > Components: Eclipse plugins >Affects Versions: 3.1.1SDK >Reporter: Andreas Korger >Priority: Major > Fix For: 3.2.0SDK > > > Hello, > i installed a complete uima framework (latest eclipse, plugin, addons, ruta, > examples) i can use the Document Analyzer on a tutorial descriptor. The > descriptor editor is available as file viewer and shows functionality BUT > does not recognize changes nor can they be saved. The file name is not shown > on the file tab. No error messages. UIMA link in eclipse Menu and JCasGen > also not available. > Thx for help, > Andy -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6331) uimaFIT 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6331:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (x) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (x) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (x) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (x) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (x) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (x) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
> uimaFIT 3.2.0 release
> -
>
> Key: UIMA-6331
> URL: https://issues.apache.org/jira/browse/UIMA-6331
> Project: UIMA
> Issue Type: Task
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> -
[jira] [Updated] (UIMA-6331) uimaFIT 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6331:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (x) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (x) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (x) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (x) Clean local m2 repository and build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (x) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (x) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (x) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
> uimaFIT 3.2.0 release
> -
>
> Key: UIMA-6331
> URL: https://issues.apache.org/jira/browse/UIMA-6331
> Project: UIMA
> Issue Type: Task
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (x) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (x) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> -
[jira] [Reopened] (UIMA-6264) Switch from DocBook to Asciidoc
[ https://issues.apache.org/jira/browse/UIMA-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho reopened UIMA-6264: -- > Switch from DocBook to Asciidoc > --- > > Key: UIMA-6264 > URL: https://issues.apache.org/jira/browse/UIMA-6264 > Project: UIMA > Issue Type: Task > Components: uimaFIT, uimaFIT-Maven-Plugin >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 2.6.0uimaFIT, 3.2.0uimaFIT > > > Convert the existing DocBook XML setup to an Asciidoc(tor)-based setup. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (UIMA-6264) Switch from DocBook to Asciidoc
[ https://issues.apache.org/jira/browse/UIMA-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6264. -- Resolution: Fixed > Switch from DocBook to Asciidoc > --- > > Key: UIMA-6264 > URL: https://issues.apache.org/jira/browse/UIMA-6264 > Project: UIMA > Issue Type: Task > Components: uimaFIT, uimaFIT-Maven-Plugin >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 2.6.0uimaFIT, 3.2.0uimaFIT > > > Convert the existing DocBook XML setup to an Asciidoc(tor)-based setup. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6331) uimaFIT 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6331:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (x) Clean local m2 repository and build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (x) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (x) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (x) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (x) Update API comparison version in POM
- (x) Clean local m2 repository and build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (x) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (x) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (x) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
> uimaFIT 3.2.0 release
> -
>
> Key: UIMA-6331
> URL: https://issues.apache.org/jira/browse/UIMA-6331
> Project: UIMA
> Issue Type: Task
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (x) Clean local m2 repository and build locally with {{-Papache-release}}
> - (x) Check the issues report in {{issuesFixed}} if it looks ok
> - (x) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (x) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> -
[jira] [Resolved] (UIMA-6357) Upgrade Apache Commons dependencies
[ https://issues.apache.org/jira/browse/UIMA-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6357. -- Resolution: Fixed > Upgrade Apache Commons dependencies > --- > > Key: UIMA-6357 > URL: https://issues.apache.org/jira/browse/UIMA-6357 > Project: UIMA > Issue Type: Improvement > Components: uimaFIT >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.2.0uimaFIT > > > Upgrade to Commons IO 2.8.0 > Upgrade Commons Lang 3 to 3.12.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6331) uimaFIT 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6331:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (x) Update API comparison version in POM
- (x) Clean local m2 repository and build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (x) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (x) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (x) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
was:
- (/) Create release branch
- (/) Update {{README}} file
- (x) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (x) Update API comparison version in POM
- (x) Clean local m2 repository and build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (x) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (x) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (x) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
> uimaFIT 3.2.0 release
> -
>
> Key: UIMA-6331
> URL: https://issues.apache.org/jira/browse/UIMA-6331
> Project: UIMA
> Issue Type: Task
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (x) Update API comparison version in POM
> - (x) Clean local m2 repository and build locally with {{-Papache-release}}
> - (x) Check the issues report in {{issuesFixed}} if it looks ok
> - (x) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (x) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> -
[jira] [Work started] (UIMA-6357) Upgrade Apache Commons dependencies
[ https://issues.apache.org/jira/browse/UIMA-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-6357 started by Richard Eckart de Castilho. > Upgrade Apache Commons dependencies > --- > > Key: UIMA-6357 > URL: https://issues.apache.org/jira/browse/UIMA-6357 > Project: UIMA > Issue Type: Improvement > Components: uimaFIT >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.2.0uimaFIT > > > Upgrade to Commons IO 2.8.0 > Upgrade Commons Lang 3 to 3.12.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6357) Upgrade Apache Commons dependencies
[ https://issues.apache.org/jira/browse/UIMA-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6357: - Description: Upgrade to Commons IO 2.8.0 Upgrade Commons Lang 3 to 3.12.0 was:Upgrade to Commons IO 2.8.0 > Upgrade Apache Commons dependencies > --- > > Key: UIMA-6357 > URL: https://issues.apache.org/jira/browse/UIMA-6357 > Project: UIMA > Issue Type: Improvement > Components: uimaFIT >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.2.0uimaFIT > > > Upgrade to Commons IO 2.8.0 > Upgrade Commons Lang 3 to 3.12.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6357) Upgrade Apache Commons dependencies
[ https://issues.apache.org/jira/browse/UIMA-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6357: - Summary: Upgrade Apache Commons dependencies (was: Upgrade to Commons IO 2.8.0) > Upgrade Apache Commons dependencies > --- > > Key: UIMA-6357 > URL: https://issues.apache.org/jira/browse/UIMA-6357 > Project: UIMA > Issue Type: Improvement > Components: uimaFIT >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.2.0uimaFIT > > > Upgrade to Commons IO 2.8.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (UIMA-6357) Upgrade to Commons IO 2.8.0
Richard Eckart de Castilho created UIMA-6357: Summary: Upgrade to Commons IO 2.8.0 Key: UIMA-6357 URL: https://issues.apache.org/jira/browse/UIMA-6357 Project: UIMA Issue Type: Improvement Components: uimaFIT Reporter: Richard Eckart de Castilho Assignee: Richard Eckart de Castilho Fix For: 3.2.0uimaFIT Upgrade to Commons IO 2.8.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6331) uimaFIT 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6331:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (x) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (x) Update API comparison version in POM
- (x) Clean local m2 repository and build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (x) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (x) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (x) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) -Update {{RELEASE_NOTES.html}} file- (is part of {{README}} in uimaFIT)
- (x) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (x) Update API comparison version in POM
- (x) Clean local m2 repository and build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (x) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (x) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Remove the old update site and move the new one in at
{{https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3}}
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (x) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
> uimaFIT 3.2.0 release
> -
>
> Key: UIMA-6331
> URL: https://issues.apache.org/jira/browse/UIMA-6331
> Project: UIMA
> Issue Type: Task
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (x) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT
[jira] [Updated] (UIMA-6331) uimaFIT 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6331:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) -Update {{RELEASE_NOTES.html}} file- (is part of {{README}} in uimaFIT)
- (x) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (x) Update API comparison version in POM
- (x) Clean local m2 repository and build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (x) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (x) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Remove the old update site and move the new one in at
{{https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3}}
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (x) Merge the release branch
- (x) Update website
- (x) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
was:
- (/) Create release branch
- (x) Update {{README}} file
- (x) Update {{RELEASE_NOTES.html}} file
- (x) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (x) Update Jira version in POM for fixed-issues report
- (x) Update API comparison version in POM
- (x) Clean local m2 repository and build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> uimaFIT 3.2.0 release
> -
>
> Key: UIMA-6331
> URL: https://issues.apache.org/jira/browse/UIMA-6331
> Project: UIMA
> Issue Type: Task
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) -Update {{RELEASE_NOTES.html}} file- (is part of {{README}} in uimaFIT)
> - (x) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (x) Update API comparison version in POM
> - (x) Clean local m2 repository and build locally with {{-Papache-release}}
> - (x) Check the issues report in {{issuesFixed}} if it looks ok
> - (x) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (x) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> - (x) Close the staging repository at {{http://repository.apache.org/}}
> - (x) Check out release staging svn spot
>
[jira] [Resolved] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6329.
--
Fix Version/s: 3.2.0SDK
Resolution: Fixed
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.2.0SDK
>
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> - (/) Close the staging repository at {{http://repository.apache.org/}}
> - (/) Check out release staging svn spot
> {{https://dist.apache.org/repos/dist/dev/uima/}}
> - (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
> release staging spot
> - (/) Update the version in the {{uimaj-eclipse-update-site}}
> - (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
> - (/) Copy the update site to a subdirectory of the release staging spot and
> *commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
> be removed!)
> - (/) Call for a vote including URLs for
> ** Issue list
> ** Staging repository
> ** SVN staging spot (artifacts)
> ** SVN staging spot (update site)
> ** Git tag
> - (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
> release)
> - (/) Post vote results (sign mail using same GPG key that was used to sign
> release)
> - (/) Copy the release artifacts from the staging spot to the dist spot in SVN
> - (/) Remove the old update site and move the new one in at
> {{https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3}}
> - (/) Release staging repository at {{http://repository.apache.org/}}
> - (/) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
> prefixed with {{rel}}
> - (/) Merge the release branch
> - (/) Update website
> - (/) Post release announcement to {{annou...@apache.org}} (Cc:
> {{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
> at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign
> mail using same GPG key that was used to sign release)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (/) Copy the release artifacts from the staging spot to the dist spot in SVN
- (/) Remove the old update site and move the new one in at
{{https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3}}
- (/) Release staging repository at {{http://repository.apache.org/}}
- (/) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (/) Merge the release branch
- (/) Update website
- (/) Post release announcement to {{annou...@apache.org}} (Cc:
{{dev@uima.apache.org}}, {{u...@uima.apache.org}} -- once release has arrived
at {{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}} -- sign mail
using same GPG key that was used to sign release)
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (/) Copy the release artifacts from the staging spot to the dist spot in SVN
- (/) Remove the old update site and move the new one in at
{{https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3}}
- (/) Release staging repository at {{http://repository.apache.org/}}
- (/) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (/) Merge the release branch
- (/) Update website
- (x) Publish release announcement (once release has arrived at
{{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}}
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components:
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (/) Copy the release artifacts from the staging spot to the dist spot in SVN
- (/) Remove the old update site and move the new one in at
{{https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3}}
- (/) Release staging repository at {{http://repository.apache.org/}}
- (/) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not
prefixed with {{rel}}
- (/) Merge the release branch
- (/) Update website
- (x) Publish release announcement (once release has arrived at
{{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}}
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (/) Copy the release artifacts from the staging spot to the dist spot in SVN
- (/) Remove the old update site and move the new one in at
{{https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3}}
- (/) Release staging repository at {{http://repository.apache.org/}}
- (/) Update website
- (x) Publish release announcement (once release has arrived at
{{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}}
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (/) Copy the release artifacts from the staging spot to the dist spot in SVN
- (/) Remove the old update site and move the new one in at
{{https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3}}
- (/) Release staging repository at {{http://repository.apache.org/}}
- (/) Update website
- (x) Publish release announcement (once release has arrived at
{{https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/}}
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (/) Copy the release artifacts from the staging spot to the dist spot in SVN
- (/) Remove the old update site and move the new one in at
{{https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3}}
- (/) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (/) Copy the release artifacts from the staging spot to the dist spot in SVN
- (/) Remove the old update site and move the new one in at
{{https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3}}
- (/) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (/) Copy the release artifacts from the staging spot to the dist spot in SVN
- (/) Remove the old update site and move the new one in at
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3
- (/) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/)
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (/) Copy the release artifacts from the staging spot to the dist spot in SVN
- (/) Remove the old update site and move the new one in at
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3
- (/) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (/) Copy the release artifacts from the staging spot to the dist spot in SVN
- (/) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
>
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (/) Copy the release artifacts from the staging spot to the dist spot in SVN
- (/) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (/) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build ({{mvn -DautoVersionSubmodules=true
>
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (/) VOTE (wait at least for 72 hours, at least 3 +1 votes required for
release)
- (/) Post vote results (sign mail using same GPG key that was used to sign
release)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (/) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (/) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> - (/) Close the staging repository at {{http://repository.apache.org/}}
> - (/) Check out release staging svn spot
>
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (/) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> - (/) Close the staging repository at {{http://repository.apache.org/}}
> - (/) Check out release staging svn spot
> {{https://dist.apache.org/repos/dist/dev/uima/}}
> - (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
> release staging spot
> - (/)
[jira] [Comment Edited] (UIMA-6355) Component Descriptor Editor not working 100%
[ https://issues.apache.org/jira/browse/UIMA-6355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17337399#comment-17337399 ] Richard Eckart de Castilho edited comment on UIMA-6355 at 4/30/21, 1:41 PM: There was a brief period where 3.2.0 was wrongly already listed on the official UIMA Eclipse update site (but not installable). This has been rolled back. Presently it is only available from the release candidate staging area. was (Author: rec): There was a brief period where 3.2.0 was wrongly already available via the official UIMA Eclipse update site. This has been rolled back. Presently it is only available from the release candidate staging area. > Component Descriptor Editor not working 100% > > > Key: UIMA-6355 > URL: https://issues.apache.org/jira/browse/UIMA-6355 > Project: UIMA > Issue Type: Bug > Components: Eclipse plugins >Affects Versions: 3.1.1SDK >Reporter: Andreas Korger >Priority: Major > > Hello, > i installed a complete uima framework (latest eclipse, plugin, addons, ruta, > examples) i can use the Document Analyzer on a tutorial descriptor. The > descriptor editor is available as file viewer and shows functionality BUT > does not recognize changes nor can they be saved. The file name is not shown > on the file tab. No error messages. UIMA link in eclipse Menu and JCasGen > also not available. > Thx for help, > Andy -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-6355) Component Descriptor Editor not working 100%
[ https://issues.apache.org/jira/browse/UIMA-6355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17337399#comment-17337399 ] Richard Eckart de Castilho commented on UIMA-6355: -- There was a brief period where 3.2.0 was wrongly already available via the official UIMA Eclipse update site. This has been rolled back. Presently it is only available from the release candidate staging area. > Component Descriptor Editor not working 100% > > > Key: UIMA-6355 > URL: https://issues.apache.org/jira/browse/UIMA-6355 > Project: UIMA > Issue Type: Bug > Components: Eclipse plugins >Affects Versions: 3.1.1SDK >Reporter: Andreas Korger >Priority: Major > > Hello, > i installed a complete uima framework (latest eclipse, plugin, addons, ruta, > examples) i can use the Document Analyzer on a tutorial descriptor. The > descriptor editor is available as file viewer and shows functionality BUT > does not recognize changes nor can they be saved. The file name is not shown > on the file tab. No error messages. UIMA link in eclipse Menu and JCasGen > also not available. > Thx for help, > Andy -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-6355) Component Descriptor Editor not working 100%
[ https://issues.apache.org/jira/browse/UIMA-6355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17337370#comment-17337370 ] Richard Eckart de Castilho commented on UIMA-6355: -- I can also observe the issue in Eclipse 2021-03 with UIMA 3.1.1. With 3.2.0 RC4, I do not observe the issue in a fresh Eclipse 2021-03. I can create a type descriptor file, edit it, save it, and re-open it. The filename is present in the tab title. You can find a link to the 3.2.0 RC 4 update site on the UIMA developers mailing list in the vote mail for the release if you are curious and willing to try it without it having been fully released yet. > Component Descriptor Editor not working 100% > > > Key: UIMA-6355 > URL: https://issues.apache.org/jira/browse/UIMA-6355 > Project: UIMA > Issue Type: Bug > Components: Eclipse plugins >Affects Versions: 3.1.1SDK >Reporter: Andreas Korger >Priority: Major > > Hello, > i installed a complete uima framework (latest eclipse, plugin, addons, ruta, > examples) i can use the Document Analyzer on a tutorial descriptor. The > descriptor editor is available as file viewer and shows functionality BUT > does not recognize changes nor can they be saved. The file name is not shown > on the file tab. No error messages. UIMA link in eclipse Menu and JCasGen > also not available. > Thx for help, > Andy -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-6355) Component Descriptor Editor not working 100%
[ https://issues.apache.org/jira/browse/UIMA-6355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17337295#comment-17337295 ] Richard Eckart de Castilho commented on UIMA-6355: -- What Eclipse version are you using? > Component Descriptor Editor not working 100% > > > Key: UIMA-6355 > URL: https://issues.apache.org/jira/browse/UIMA-6355 > Project: UIMA > Issue Type: Bug > Components: Eclipse plugins >Affects Versions: 3.1.1SDK >Reporter: Andreas Korger >Priority: Major > > Hello, > i installed a complete uima framework (latest eclipse, plugin, addons, ruta, > examples) i can use the Document Analyzer on a tutorial descriptor. The > descriptor editor is available as file viewer and shows functionality BUT > does not recognize changes nor can they be saved. The file name is not shown > on the file tab. No error messages. UIMA link in eclipse Menu and JCasGen > also not available. > Thx for help, > Andy -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (UIMA-6310) JCasClassLoaderTest sometimes fails
[
https://issues.apache.org/jira/browse/UIMA-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6310.
--
Fix Version/s: (was: 3.2.0uimaFIT)
3.2.0SDK
Resolution: Fixed
> JCasClassLoaderTest sometimes fails
> ---
>
> Key: UIMA-6310
> URL: https://issues.apache.org/jira/browse/UIMA-6310
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
>Affects Versions: 2.10.4SDK
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 2.11.0SDK, 3.2.0SDK
>
>
> The
> JCasClassLoaderTest.thatCASCanBeDefinedWithoutJCasWrappersAndTheyComeInWithAnnotatorsViaClasspath
> test fails at times. It seems to happen regularly when the builds run on a
> Jenkins Windows node. I have not been able to reproduce the issue on OS X.
> There are rumours about a potentially related issue sometimes happening on
> with UIMAv2 on Linux (i.e. a PEAR provides a JCas wrapper but when the PEAR
> tries to access FSes of that type, it instead gets Annotation_Impl because
> the JCas wrapper is not known at the pipeline level...).
> {noformat}
> Error
> The following assertion failed:
> 1) [AddTokenAnnotator and FetchTokenAnnotator use different Token wrappers]
> Expecting:
>
> not to be equal to:
>
> at
> JCasClassLoaderTest.thatCASCanBeDefinedWithoutJCasWrappersAndTheyComeInWithAnnotatorsViaClasspath(JCasClassLoaderTest.java:148)
> Stacktrace
> org.assertj.core.api.SoftAssertionError:
> The following assertion failed:
> 1) [AddTokenAnnotator and FetchTokenAnnotator use different Token wrappers]
> Expecting:
>
> not to be equal to:
>
> at
> JCasClassLoaderTest.thatCASCanBeDefinedWithoutJCasWrappersAndTheyComeInWithAnnotatorsViaClasspath(JCasClassLoaderTest.java:148)
> at
> org.apache.uima.cas.test.JCasClassLoaderTest.thatCASCanBeDefinedWithoutJCasWrappersAndTheyComeInWithAnnotatorsViaClasspath(JCasClassLoaderTest.java:155)
> Standard Output
> [JCas creation] org.apache.uima.cas.test.Token NOT AVAILABLE
> [AE creation: AddATokenAnnotator] org.apache.uima.cas.test.Token 2107109044
> [AE creation: FetchTheTokenAnnotator] org.apache.uima.cas.test.Token
> 2107109044
> org.apache.uima.cas.test.JCasClassLoaderTest$AddATokenAnnotator class loader:
> jdk.internal.loader.ClassLoaders$AppClassLoader@2aae9190
> [AE runtime: org.apache.uima.cas.test.JCasClassLoaderTest$AddATokenAnnotator]
> org.apache.uima.cas.test.Token 2107109044
> org.apache.uima.cas.test.JCasClassLoaderTest$FetchTheTokenAnnotator class
> loader: jdk.internal.loader.ClassLoaders$AppClassLoader@2aae9190
> [AE runtime:
> org.apache.uima.cas.test.JCasClassLoaderTest$FetchTheTokenAnnotator]
> org.apache.uima.cas.test.Token 2107109044
> [AE runtime CAS:
> org.apache.uima.cas.test.JCasClassLoaderTest$FetchTheTokenAnnotator]
> org.apache.uima.cas.test.Token 2107109044
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work started] (UIMA-6310) JCasClassLoaderTest sometimes fails
[
https://issues.apache.org/jira/browse/UIMA-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-6310 started by Richard Eckart de Castilho.
> JCasClassLoaderTest sometimes fails
> ---
>
> Key: UIMA-6310
> URL: https://issues.apache.org/jira/browse/UIMA-6310
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
>Affects Versions: 2.10.4SDK
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.2.0uimaFIT, 2.11.0SDK
>
>
> The
> JCasClassLoaderTest.thatCASCanBeDefinedWithoutJCasWrappersAndTheyComeInWithAnnotatorsViaClasspath
> test fails at times. It seems to happen regularly when the builds run on a
> Jenkins Windows node. I have not been able to reproduce the issue on OS X.
> There are rumours about a potentially related issue sometimes happening on
> with UIMAv2 on Linux (i.e. a PEAR provides a JCas wrapper but when the PEAR
> tries to access FSes of that type, it instead gets Annotation_Impl because
> the JCas wrapper is not known at the pipeline level...).
> {noformat}
> Error
> The following assertion failed:
> 1) [AddTokenAnnotator and FetchTokenAnnotator use different Token wrappers]
> Expecting:
>
> not to be equal to:
>
> at
> JCasClassLoaderTest.thatCASCanBeDefinedWithoutJCasWrappersAndTheyComeInWithAnnotatorsViaClasspath(JCasClassLoaderTest.java:148)
> Stacktrace
> org.assertj.core.api.SoftAssertionError:
> The following assertion failed:
> 1) [AddTokenAnnotator and FetchTokenAnnotator use different Token wrappers]
> Expecting:
>
> not to be equal to:
>
> at
> JCasClassLoaderTest.thatCASCanBeDefinedWithoutJCasWrappersAndTheyComeInWithAnnotatorsViaClasspath(JCasClassLoaderTest.java:148)
> at
> org.apache.uima.cas.test.JCasClassLoaderTest.thatCASCanBeDefinedWithoutJCasWrappersAndTheyComeInWithAnnotatorsViaClasspath(JCasClassLoaderTest.java:155)
> Standard Output
> [JCas creation] org.apache.uima.cas.test.Token NOT AVAILABLE
> [AE creation: AddATokenAnnotator] org.apache.uima.cas.test.Token 2107109044
> [AE creation: FetchTheTokenAnnotator] org.apache.uima.cas.test.Token
> 2107109044
> org.apache.uima.cas.test.JCasClassLoaderTest$AddATokenAnnotator class loader:
> jdk.internal.loader.ClassLoaders$AppClassLoader@2aae9190
> [AE runtime: org.apache.uima.cas.test.JCasClassLoaderTest$AddATokenAnnotator]
> org.apache.uima.cas.test.Token 2107109044
> org.apache.uima.cas.test.JCasClassLoaderTest$FetchTheTokenAnnotator class
> loader: jdk.internal.loader.ClassLoaders$AppClassLoader@2aae9190
> [AE runtime:
> org.apache.uima.cas.test.JCasClassLoaderTest$FetchTheTokenAnnotator]
> org.apache.uima.cas.test.Token 2107109044
> [AE runtime CAS:
> org.apache.uima.cas.test.JCasClassLoaderTest$FetchTheTokenAnnotator]
> org.apache.uima.cas.test.Token 2107109044
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (UIMA-6310) JCasClassLoaderTest sometimes fails
[
https://issues.apache.org/jira/browse/UIMA-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho reopened UIMA-6310:
--
> JCasClassLoaderTest sometimes fails
> ---
>
> Key: UIMA-6310
> URL: https://issues.apache.org/jira/browse/UIMA-6310
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
>Affects Versions: 2.10.4SDK
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 2.11.0SDK
>
>
> The
> JCasClassLoaderTest.thatCASCanBeDefinedWithoutJCasWrappersAndTheyComeInWithAnnotatorsViaClasspath
> test fails at times. It seems to happen regularly when the builds run on a
> Jenkins Windows node. I have not been able to reproduce the issue on OS X.
> There are rumours about a potentially related issue sometimes happening on
> with UIMAv2 on Linux (i.e. a PEAR provides a JCas wrapper but when the PEAR
> tries to access FSes of that type, it instead gets Annotation_Impl because
> the JCas wrapper is not known at the pipeline level...).
> {noformat}
> Error
> The following assertion failed:
> 1) [AddTokenAnnotator and FetchTokenAnnotator use different Token wrappers]
> Expecting:
>
> not to be equal to:
>
> at
> JCasClassLoaderTest.thatCASCanBeDefinedWithoutJCasWrappersAndTheyComeInWithAnnotatorsViaClasspath(JCasClassLoaderTest.java:148)
> Stacktrace
> org.assertj.core.api.SoftAssertionError:
> The following assertion failed:
> 1) [AddTokenAnnotator and FetchTokenAnnotator use different Token wrappers]
> Expecting:
>
> not to be equal to:
>
> at
> JCasClassLoaderTest.thatCASCanBeDefinedWithoutJCasWrappersAndTheyComeInWithAnnotatorsViaClasspath(JCasClassLoaderTest.java:148)
> at
> org.apache.uima.cas.test.JCasClassLoaderTest.thatCASCanBeDefinedWithoutJCasWrappersAndTheyComeInWithAnnotatorsViaClasspath(JCasClassLoaderTest.java:155)
> Standard Output
> [JCas creation] org.apache.uima.cas.test.Token NOT AVAILABLE
> [AE creation: AddATokenAnnotator] org.apache.uima.cas.test.Token 2107109044
> [AE creation: FetchTheTokenAnnotator] org.apache.uima.cas.test.Token
> 2107109044
> org.apache.uima.cas.test.JCasClassLoaderTest$AddATokenAnnotator class loader:
> jdk.internal.loader.ClassLoaders$AppClassLoader@2aae9190
> [AE runtime: org.apache.uima.cas.test.JCasClassLoaderTest$AddATokenAnnotator]
> org.apache.uima.cas.test.Token 2107109044
> org.apache.uima.cas.test.JCasClassLoaderTest$FetchTheTokenAnnotator class
> loader: jdk.internal.loader.ClassLoaders$AppClassLoader@2aae9190
> [AE runtime:
> org.apache.uima.cas.test.JCasClassLoaderTest$FetchTheTokenAnnotator]
> org.apache.uima.cas.test.Token 2107109044
> [AE runtime CAS:
> org.apache.uima.cas.test.JCasClassLoaderTest$FetchTheTokenAnnotator]
> org.apache.uima.cas.test.Token 2107109044
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (UIMA-6310) JCasClassLoaderTest sometimes fails
[
https://issues.apache.org/jira/browse/UIMA-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6310:
-
Fix Version/s: 3.2.0uimaFIT
> JCasClassLoaderTest sometimes fails
> ---
>
> Key: UIMA-6310
> URL: https://issues.apache.org/jira/browse/UIMA-6310
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
>Affects Versions: 2.10.4SDK
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.2.0uimaFIT, 2.11.0SDK
>
>
> The
> JCasClassLoaderTest.thatCASCanBeDefinedWithoutJCasWrappersAndTheyComeInWithAnnotatorsViaClasspath
> test fails at times. It seems to happen regularly when the builds run on a
> Jenkins Windows node. I have not been able to reproduce the issue on OS X.
> There are rumours about a potentially related issue sometimes happening on
> with UIMAv2 on Linux (i.e. a PEAR provides a JCas wrapper but when the PEAR
> tries to access FSes of that type, it instead gets Annotation_Impl because
> the JCas wrapper is not known at the pipeline level...).
> {noformat}
> Error
> The following assertion failed:
> 1) [AddTokenAnnotator and FetchTokenAnnotator use different Token wrappers]
> Expecting:
>
> not to be equal to:
>
> at
> JCasClassLoaderTest.thatCASCanBeDefinedWithoutJCasWrappersAndTheyComeInWithAnnotatorsViaClasspath(JCasClassLoaderTest.java:148)
> Stacktrace
> org.assertj.core.api.SoftAssertionError:
> The following assertion failed:
> 1) [AddTokenAnnotator and FetchTokenAnnotator use different Token wrappers]
> Expecting:
>
> not to be equal to:
>
> at
> JCasClassLoaderTest.thatCASCanBeDefinedWithoutJCasWrappersAndTheyComeInWithAnnotatorsViaClasspath(JCasClassLoaderTest.java:148)
> at
> org.apache.uima.cas.test.JCasClassLoaderTest.thatCASCanBeDefinedWithoutJCasWrappersAndTheyComeInWithAnnotatorsViaClasspath(JCasClassLoaderTest.java:155)
> Standard Output
> [JCas creation] org.apache.uima.cas.test.Token NOT AVAILABLE
> [AE creation: AddATokenAnnotator] org.apache.uima.cas.test.Token 2107109044
> [AE creation: FetchTheTokenAnnotator] org.apache.uima.cas.test.Token
> 2107109044
> org.apache.uima.cas.test.JCasClassLoaderTest$AddATokenAnnotator class loader:
> jdk.internal.loader.ClassLoaders$AppClassLoader@2aae9190
> [AE runtime: org.apache.uima.cas.test.JCasClassLoaderTest$AddATokenAnnotator]
> org.apache.uima.cas.test.Token 2107109044
> org.apache.uima.cas.test.JCasClassLoaderTest$FetchTheTokenAnnotator class
> loader: jdk.internal.loader.ClassLoaders$AppClassLoader@2aae9190
> [AE runtime:
> org.apache.uima.cas.test.JCasClassLoaderTest$FetchTheTokenAnnotator]
> org.apache.uima.cas.test.Token 2107109044
> [AE runtime CAS:
> org.apache.uima.cas.test.JCasClassLoaderTest$FetchTheTokenAnnotator]
> org.apache.uima.cas.test.Token 2107109044
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (UIMA-6244) test case bug, running in windows
[ https://issues.apache.org/jira/browse/UIMA-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6244. -- Resolution: Fixed > test case bug, running in windows > - > > Key: UIMA-6244 > URL: https://issues.apache.org/jira/browse/UIMA-6244 > Project: UIMA > Issue Type: Bug > Components: Core Java Framework >Affects Versions: 2.4.2SDK, 3.1.1SDK >Reporter: Marshall Schor >Assignee: Marshall Schor >Priority: Minor > Fix For: 2.11.0SDK, 3.2.0SDK > > > The test > "TestPearInstallation.thatSpecialXmlCharactersInTargetPathDoNotBreakInstallation > uses characters not allowed in windows. Change to characters that are > special and allowed. > See [https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file] for > list of invalid chars in windows. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (UIMA-6244) test case bug, running in windows
[ https://issues.apache.org/jira/browse/UIMA-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho reopened UIMA-6244: -- > test case bug, running in windows > - > > Key: UIMA-6244 > URL: https://issues.apache.org/jira/browse/UIMA-6244 > Project: UIMA > Issue Type: Bug > Components: Core Java Framework >Affects Versions: 2.4.2SDK, 3.1.1SDK >Reporter: Marshall Schor >Assignee: Marshall Schor >Priority: Minor > Fix For: 2.11.0SDK, 3.2.0SDK > > > The test > "TestPearInstallation.thatSpecialXmlCharactersInTargetPathDoNotBreakInstallation > uses characters not allowed in windows. Change to characters that are > special and allowed. > See [https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file] for > list of invalid chars in windows. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
*commit* (*Caution:* the update site contains a {{.svn}} folder that needs to
be removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit (*Caution:* the update site contains a {{.svn}} folder that needs to be
removed!)
- (x) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> - (/) Close the staging repository at {{http://repository.apache.org/}}
> - (/) Check out release staging svn spot
> {{https://dist.apache.org/repos/dist/dev/uima/}}
> - (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
> release staging spot
>
[jira] [Resolved] (UIMA-6305) Convert UIMAv3 User's Guide from DocBook to Asciidoc
[ https://issues.apache.org/jira/browse/UIMA-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6305. -- Resolution: Fixed > Convert UIMAv3 User's Guide from DocBook to Asciidoc > > > Key: UIMA-6305 > URL: https://issues.apache.org/jira/browse/UIMA-6305 > Project: UIMA > Issue Type: Improvement > Components: Documentation >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Minor > Fix For: 3.2.0SDK > > > Convert UIMAv3 User's Guide from DocBook to Asciidoc. Won't be updating the > other manuals in this issue - those will have separate issues and probably be > done at a later time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (UIMA-6354) Limit permitted JDK to minimal JDK for release builds
Richard Eckart de Castilho created UIMA-6354:
Summary: Limit permitted JDK to minimal JDK for release builds
Key: UIMA-6354
URL: https://issues.apache.org/jira/browse/UIMA-6354
Project: UIMA
Issue Type: Improvement
Components: Core Java Framework, uimaFIT
Reporter: Richard Eckart de Castilho
Fix For: 3.3.0SDK, 3.3.0uimaFIT
When the {{apache-release}} profile is active, add an additional enforcer rule
that requires the JDK being used to match the minimum system requirements. E.g.
as long as we support Java 1.8, the release builds should fail unless the JDK
being used for the build is a 1.8 JDK.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work started] (UIMA-6305) Convert UIMAv3 User's Guide from DocBook to Asciidoc
[ https://issues.apache.org/jira/browse/UIMA-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-6305 started by Richard Eckart de Castilho. > Convert UIMAv3 User's Guide from DocBook to Asciidoc > > > Key: UIMA-6305 > URL: https://issues.apache.org/jira/browse/UIMA-6305 > Project: UIMA > Issue Type: Improvement > Components: Documentation >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Minor > Fix For: 3.2.0SDK > > > Convert UIMAv3 User's Guide from DocBook to Asciidoc. Won't be updating the > other manuals in this issue - those will have separate issues and probably be > done at a later time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (UIMA-6305) Convert UIMAv3 User's Guide from DocBook to Asciidoc
[ https://issues.apache.org/jira/browse/UIMA-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho reopened UIMA-6305: -- New docu not included in release ZIP yet... > Convert UIMAv3 User's Guide from DocBook to Asciidoc > > > Key: UIMA-6305 > URL: https://issues.apache.org/jira/browse/UIMA-6305 > Project: UIMA > Issue Type: Improvement > Components: Documentation >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Minor > Fix For: 3.2.0SDK > > > Convert UIMAv3 User's Guide from DocBook to Asciidoc. Won't be updating the > other manuals in this issue - those will have separate issues and probably be > done at a later time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit (*Caution:* the update site contains a {{.svn}} folder that needs to be
removed!)
- (x) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
commit (*Caution:* the update site contains a {{.svn}} folder that needs to be
removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (x) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (x) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> - (x) Close the staging repository at {{http://repository.apache.org/}}
> - (x) Check out release staging svn spot
> {{https://dist.apache.org/repos/dist/dev/uima/}}
> - (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
> release
[jira] [Resolved] (UIMA-6353) Logger_common_impl.error(String arg0, Object arg1, Object arg2) swallows last argument
[
https://issues.apache.org/jira/browse/UIMA-6353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6353.
--
Resolution: Fixed
> Logger_common_impl.error(String arg0, Object arg1, Object arg2) swallows last
> argument
> --
>
> Key: UIMA-6353
> URL: https://issues.apache.org/jira/browse/UIMA-6353
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
>Affects Versions: 3.1.1SDK
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.2.0SDK
>
>
> {{Logger_common_impl.error(String arg0, Object arg1, Object arg2)}} does not
> pass the second object argument down to the logging framework. This can cause
> e.g. exceptions to be not logged with their stack traces if the last argument
> is an exception or it can cause placeholders not to be filled. The issue
> affects all logging levels.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (UIMA-6353) Logger_common_impl.error(String arg0, Object arg1, Object arg2) swallows last argument
Richard Eckart de Castilho created UIMA-6353:
Summary: Logger_common_impl.error(String arg0, Object arg1, Object
arg2) swallows last argument
Key: UIMA-6353
URL: https://issues.apache.org/jira/browse/UIMA-6353
Project: UIMA
Issue Type: Bug
Components: Core Java Framework
Affects Versions: 3.1.1SDK
Reporter: Richard Eckart de Castilho
Assignee: Richard Eckart de Castilho
Fix For: 3.2.0SDK
{{Logger_common_impl.error(String arg0, Object arg1, Object arg2)}} does not
pass the second object argument down to the logging framework. This can cause
e.g. exceptions to be not logged with their stack traces if the last argument
is an exception or it can cause placeholders not to be filled. The issue
affects all logging levels.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work started] (UIMA-6353) Logger_common_impl.error(String arg0, Object arg1, Object arg2) swallows last argument
[
https://issues.apache.org/jira/browse/UIMA-6353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-6353 started by Richard Eckart de Castilho.
> Logger_common_impl.error(String arg0, Object arg1, Object arg2) swallows last
> argument
> --
>
> Key: UIMA-6353
> URL: https://issues.apache.org/jira/browse/UIMA-6353
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
>Affects Versions: 3.1.1SDK
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.2.0SDK
>
>
> {{Logger_common_impl.error(String arg0, Object arg1, Object arg2)}} does not
> pass the second object argument down to the logging framework. This can cause
> e.g. exceptions to be not logged with their stack traces if the last argument
> is an exception or it can cause placeholders not to be filled. The issue
> affects all logging levels.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (UIMA-6352) reinit(CASCompleteSerializer) does not properly reset indexes
[
https://issues.apache.org/jira/browse/UIMA-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6352.
--
Resolution: Fixed
> reinit(CASCompleteSerializer) does not properly reset indexes
> -
>
> Key: UIMA-6352
> URL: https://issues.apache.org/jira/browse/UIMA-6352
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
>Affects Versions: 3.1.1SDK
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.2.0SDK
>
>
> The {{CASCompleteSerializer}} consists of a {{CASMgrSerializer}} and a
> {{CASSerializer}}. However, {{CAS.reinit(CASCompleteSerializer)}} does not
> fully include the behavior of {{CAS.reinit(CASMgrSerializer)}} - in
> particular the index repositories in {{baseCas.svd.sofa2indexMap}} are not
> cleared. Since the {{CAS.reinit(CASCompleteSerializer)}} can replace the type
> system in the CAS, this can cause the {{TypeSystem}} and {{Type}} instances
> used in the CAS to be out-of-sync with the respective instances used in the
> {{FSIndexRepository}} instances stored in {{baseCas.svd.sofa2indexMap}}.
> This test illustrates the problem:
> {code}
> @Test
> public void thatReplacingTypeSystemInCasWorks() throws Exception {
> System.setProperty("uima.enable_strict_type_source_check", "true");
>
> CAS cas = CasCreationUtils.createCas();
> cas.setDocumentText("First view text");
> cas.createView("secondView").setDocumentText("Second view text");
> TypeSystem originalTypeSystem = cas.getTypeSystem();
> ByteArrayOutputStream buffer = new ByteArrayOutputStream();
> serializeWithCompression(cas, buffer, originalTypeSystem);
>
> TypeSystemDescription newTSD = new TypeSystemDescription_impl();
> newTSD.addType("my.Type", "", CAS.TYPE_NAME_ANNOTATION);
>
> CAS tempCas = createCas(newTSD, null, null, null);
> CASCompleteSerializer serializer = serializeCASComplete((CASImpl)
> tempCas);
> deserializeCASComplete(serializer, (CASImpl) cas);
>
> load(new ByteArrayInputStream(buffer.toByteArray()), cas,
> originalTypeSystem);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (UIMA-6352) reinit(CASCompleteSerializer) does not properly reset indexes
[
https://issues.apache.org/jira/browse/UIMA-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6352:
-
Description:
The {{CASCompleteSerializer}} consists of a {{CASMgrSerializer}} and a
{{CASSerializer}}. However, {{CAS.reinit(CASCompleteSerializer)}} does not
fully include the behavior of {{CAS.reinit(CASMgrSerializer)}} - in particular
the index repositories in {{baseCas.svd.sofa2indexMap}} are not cleared. Since
the {{CAS.reinit(CASCompleteSerializer)}} can replace the type system in the
CAS, this can cause the {{TypeSystem}} and {{Type}} instances used in the CAS
to be out-of-sync with the respective instances used in the
{{FSIndexRepository}} instances stored in {{baseCas.svd.sofa2indexMap}}.
This test illustrates the problem:
{code}
@Test
public void thatReplacingTypeSystemInCasWorks() throws Exception {
System.setProperty("uima.enable_strict_type_source_check", "true");
CAS cas = CasCreationUtils.createCas();
cas.setDocumentText("First view text");
cas.createView("secondView").setDocumentText("Second view text");
TypeSystem originalTypeSystem = cas.getTypeSystem();
ByteArrayOutputStream buffer = new ByteArrayOutputStream();
serializeWithCompression(cas, buffer, originalTypeSystem);
TypeSystemDescription newTSD = new TypeSystemDescription_impl();
newTSD.addType("my.Type", "", CAS.TYPE_NAME_ANNOTATION);
CAS tempCas = createCas(newTSD, null, null, null);
CASCompleteSerializer serializer = serializeCASComplete((CASImpl) tempCas);
deserializeCASComplete(serializer, (CASImpl) cas);
load(new ByteArrayInputStream(buffer.toByteArray()), cas,
originalTypeSystem);
}
{code}
was:The {{CASCompleteSerializer}} consists of a {{CASMgrSerializer}} and a
{{CASSerializer}}. However, {{CAS.reinit(CASCompleteSerializer)}} does not
fully include the behavior of {{CAS.reinit(CASMgrSerializer)}} - in particular
the index repositories in {{baseCas.svd.sofa2indexMap}} are not cleared. Since
the {{CAS.reinit(CASCompleteSerializer)}} can replace the type system in the
CAS, this can cause the {{TypeSystem}} and {{Type}} instances used in the CAS
to be out-of-sync with the respective instances used in the
{{FSIndexRepository}} instances stored in {{baseCas.svd.sofa2indexMap}}.
> reinit(CASCompleteSerializer) does not properly reset indexes
> -
>
> Key: UIMA-6352
> URL: https://issues.apache.org/jira/browse/UIMA-6352
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
>Affects Versions: 3.1.1SDK
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.2.0SDK
>
>
> The {{CASCompleteSerializer}} consists of a {{CASMgrSerializer}} and a
> {{CASSerializer}}. However, {{CAS.reinit(CASCompleteSerializer)}} does not
> fully include the behavior of {{CAS.reinit(CASMgrSerializer)}} - in
> particular the index repositories in {{baseCas.svd.sofa2indexMap}} are not
> cleared. Since the {{CAS.reinit(CASCompleteSerializer)}} can replace the type
> system in the CAS, this can cause the {{TypeSystem}} and {{Type}} instances
> used in the CAS to be out-of-sync with the respective instances used in the
> {{FSIndexRepository}} instances stored in {{baseCas.svd.sofa2indexMap}}.
> This test illustrates the problem:
> {code}
> @Test
> public void thatReplacingTypeSystemInCasWorks() throws Exception {
> System.setProperty("uima.enable_strict_type_source_check", "true");
>
> CAS cas = CasCreationUtils.createCas();
> cas.setDocumentText("First view text");
> cas.createView("secondView").setDocumentText("Second view text");
> TypeSystem originalTypeSystem = cas.getTypeSystem();
> ByteArrayOutputStream buffer = new ByteArrayOutputStream();
> serializeWithCompression(cas, buffer, originalTypeSystem);
>
> TypeSystemDescription newTSD = new TypeSystemDescription_impl();
> newTSD.addType("my.Type", "", CAS.TYPE_NAME_ANNOTATION);
>
> CAS tempCas = createCas(newTSD, null, null, null);
> CASCompleteSerializer serializer = serializeCASComplete((CASImpl)
> tempCas);
> deserializeCASComplete(serializer, (CASImpl) cas);
>
> load(new ByteArrayInputStream(buffer.toByteArray()), cas,
> originalTypeSystem);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (UIMA-6352) reinit(CASCompleteSerializer) does not properly reset indexes
Richard Eckart de Castilho created UIMA-6352:
Summary: reinit(CASCompleteSerializer) does not properly reset
indexes
Key: UIMA-6352
URL: https://issues.apache.org/jira/browse/UIMA-6352
Project: UIMA
Issue Type: Bug
Components: Core Java Framework
Affects Versions: 3.1.1SDK
Reporter: Richard Eckart de Castilho
Assignee: Richard Eckart de Castilho
Fix For: 3.2.0SDK
The {{CASCompleteSerializer}} consists of a {{CASMgrSerializer}} and a
{{CASSerializer}}. However, {{CAS.reinit(CASCompleteSerializer)}} does not
fully include the behavior of {{CAS.reinit(CASMgrSerializer)}} - in particular
the index repositories in {{baseCas.svd.sofa2indexMap}} are not cleared. Since
the {{CAS.reinit(CASCompleteSerializer)}} can replace the type system in the
CAS, this can cause the {{TypeSystem}} and {{Type}} instances used in the CAS
to be out-of-sync with the respective instances used in the
{{FSIndexRepository}} instances stored in {{baseCas.svd.sofa2indexMap}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
commit (*Caution:* the update site contains a {{.svn}} folder that needs to be
removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
commit (*Caution:* the update site contains a {{.svn}} folder that needs to be
removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> - (/) Close the staging repository at {{http://repository.apache.org/}}
> - (/) Check out release staging svn spot
> {{https://dist.apache.org/repos/dist/dev/uima/}}
> - (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
> release staging spot and commit
> - (/) Update the version in the
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
commit (*Caution:* the update site contains a {{.svn}} folder that needs to be
removed!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
commit (*Caution:* the update site contains a {{.svn}} folder that needs to be
removed!)
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build
> - (/) Close the staging repository at {{http://repository.apache.org/}}
> - (/) Check out release staging svn spot
> {{https://dist.apache.org/repos/dist/dev/uima/}}
> - (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
> release staging spot and commit
> - (/) Update the version in the {{uimaj-eclipse-update-site}}
> - (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
> - (/) Copy the update site to a subdirectory of the release
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) Copy the update site to a subdirectory of the release staging spot and
commit (*Caution:* the update site contains a {{.svn}} folder that needs to be
removed!)
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit (*Caution:* the update site contains a {{.svn}}
folder that needs to be removed!)
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build
> - (/) Close the staging repository at {{http://repository.apache.org/}}
> - (/) Check out release staging svn spot
> {{https://dist.apache.org/repos/dist/dev/uima/}}
> - (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
> release staging spot and commit
> - (/) Update the version in the {{uimaj-eclipse-update-site}}
> - (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
> - (/) Copy the update site to a subdirectory of the release staging spot and
>
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit (*Caution:* the update site contains a {{.svn}}
folder that needs to be removed!)
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit (**Caution:** the update site contains a
{{.svn}} folder that needs to be removed!)
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build
> - (/) Close the staging repository at {{http://repository.apache.org/}}
> - (/) Check out release staging svn spot
> {{https://dist.apache.org/repos/dist/dev/uima/}}
> - (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
> release staging spot and commit (*Caution:* the update site contains a
> {{.svn}} folder that needs to be removed!)
> - (x) Update the version in the {{uimaj-eclipse-update-site}}
> - (x) Build the {{uimaj-eclipse-update-site}} module with
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit (**Caution:** the update site contains a
{{.svn}} folder that needs to be removed!)
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build
> - (/) Close the staging repository at {{http://repository.apache.org/}}
> - (/) Check out release staging svn spot
> {{https://dist.apache.org/repos/dist/dev/uima/}}
> - (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
> release staging spot and commit (**Caution:** the update site contains a
> {{.svn}} folder that needs to be removed!)
> - (x) Update the version in the {{uimaj-eclipse-update-site}}
> - (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
> - (x) Copy the update site to a subdirectory of the release staging spot
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (/) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build
> - (/) Close the staging repository at {{http://repository.apache.org/}}
> - (/) Check out release staging svn spot
> {{https://dist.apache.org/repos/dist/dev/uima/}}
> - (/) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
> release staging spot and commit
> - (x) Update the version in the {{uimaj-eclipse-update-site}}
> - (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
> - (x) Copy the update site to a subdirectory of the release staging spot and
> commit
> - (x) Call for a vote including URLs for
> ** Staging repository
> ** SVN staging spot (artifacts)
> ** SVN staging spot (update site)
> ** Git tag
> - (x)
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (/) Do the release build
- (/) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (x) Do the release build
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (/) Do the release build
> - (/) Close the staging repository at {{http://repository.apache.org/}}
> - (x) Check out release staging svn spot
> {{https://dist.apache.org/repos/dist/dev/uima/}}
> - (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
> release staging spot and commit
> - (x) Update the version in the {{uimaj-eclipse-update-site}}
> - (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
> - (x) Copy the update site to a subdirectory of the release staging spot and
> commit
> - (x) Call for a vote including URLs for
> ** Staging repository
> ** SVN staging spot (artifacts)
> ** SVN staging spot (update site)
> ** Git tag
> - (x)
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Check that the Java version in the current terminal {{java -version}}
corresponds to the minimum supported version (i.e. Java 1.8)
- (x) Do the release build
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Check that the Java version in the current terminal {{java -version}}
> corresponds to the minimum supported version (i.e. Java 1.8)
> - (x) Do the release build
> - (x) Close the staging repository at {{http://repository.apache.org/}}
> - (x) Check out release staging svn spot
> {{https://dist.apache.org/repos/dist/dev/uima/}}
> - (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
> release staging spot and commit
> - (x) Update the version in the {{uimaj-eclipse-update-site}}
> - (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
> - (x) Copy the update site to a subdirectory of the release staging spot and
> commit
> - (x) Call for a vote including URLs for
> ** Staging repository
> ** SVN staging spot (artifacts)
> ** SVN staging spot (update site)
> ** Git tag
> - (x) VOTE
> - (x) Copy the release artifacts from the staging spot to the dist spot in SVN
> - (x) Release staging repository at
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (x) Do the release build
> - (x) Close the staging repository at {{http://repository.apache.org/}}
> - (x) Check out release staging svn spot
> {{https://dist.apache.org/repos/dist/dev/uima/}}
> - (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
> release staging spot and commit
> - (x) Update the version in the {{uimaj-eclipse-update-site}}
> - (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
> - (x) Copy the update site to a subdirectory of the release staging spot and
> commit
> - (x) Call for a vote including URLs for
> ** Staging repository
> ** SVN staging spot (artifacts)
> ** SVN staging spot (update site)
> ** Git tag
> - (x) VOTE
> - (x) Copy the release artifacts from the staging spot to the dist spot in SVN
> - (x) Release staging repository at {{http://repository.apache.org/}}
> - (x) Update website
> - (x) Publish release announcement
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (UIMA-6146) uimaj package.html files in wrong format for javadoc tool
[ https://issues.apache.org/jira/browse/UIMA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6146. -- Resolution: Fixed > uimaj package.html files in wrong format for javadoc tool > - > > Key: UIMA-6146 > URL: https://issues.apache.org/jira/browse/UIMA-6146 > Project: UIMA > Issue Type: Bug > Components: Core Java Framework >Affects Versions: 2.10.4SDK, 3.1.1SDK >Reporter: Marshall Schor >Assignee: Marshall Schor >Priority: Minor > Fix For: 2.11.0SDK, 3.2.0SDK > > > Fix the package.html files in the source to be appropriate for what the > javadoc tool does with this. In particular, > a) treat the first sentence of the body special (like a title) (see > [https://docs.oracle.com/javase/7/docs/technotes/tools/solaris/javadoc.html#packagecomment] > ) > b) remove etc markup, Java release 13 complains. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (UIMA-6146) uimaj package.html files in wrong format for javadoc tool
[ https://issues.apache.org/jira/browse/UIMA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho reopened UIMA-6146: -- > uimaj package.html files in wrong format for javadoc tool > - > > Key: UIMA-6146 > URL: https://issues.apache.org/jira/browse/UIMA-6146 > Project: UIMA > Issue Type: Bug > Components: Core Java Framework >Affects Versions: 2.10.4SDK, 3.1.1SDK >Reporter: Marshall Schor >Assignee: Marshall Schor >Priority: Minor > Fix For: 2.11.0SDK, 3.2.0SDK > > > Fix the package.html files in the source to be appropriate for what the > javadoc tool does with this. In particular, > a) treat the first sentence of the body special (like a title) (see > [https://docs.oracle.com/javase/7/docs/technotes/tools/solaris/javadoc.html#packagecomment] > ) > b) remove etc markup, Java release 13 complains. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6329) UIMA Java SDK 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6329:
-
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (/) Clean local m2 repository and build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} file
- (x) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update Jira version in POM for fixed-issues report
- (/) Update API comparison version in POM
- (x) Clean local m2 repository and build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build
- (x) Close the staging repository at {{http://repository.apache.org/}}
- (x) Check out release staging svn spot
{{https://dist.apache.org/repos/dist/dev/uima/}}
- (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
release staging spot and commit
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (x) Copy the update site to a subdirectory of the release staging spot and
commit
- (x) Call for a vote including URLs for
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (x) VOTE
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) Release staging repository at {{http://repository.apache.org/}}
- (x) Update website
- (x) Publish release announcement
> UIMA Java SDK 3.2.0 release
> ---
>
> Key: UIMA-6329
> URL: https://issues.apache.org/jira/browse/UIMA-6329
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} file
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update Jira version in POM for fixed-issues report
> - (/) Update API comparison version in POM
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (x) Check the issues report in {{issuesFixed}} if it looks ok
> - (x) Do the release build
> - (x) Close the staging repository at {{http://repository.apache.org/}}
> - (x) Check out release staging svn spot
> {{https://dist.apache.org/repos/dist/dev/uima/}}
> - (x) Copy artifacts from {{target/checkout/target}} to a subdirectory of the
> release staging spot and commit
> - (x) Update the version in the {{uimaj-eclipse-update-site}}
> - (x) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
> - (x) Copy the update site to a subdirectory of the release staging spot and
> commit
> - (x) Call for a vote including URLs for
> ** Staging repository
> ** SVN staging spot (artifacts)
> ** SVN staging spot (update site)
> ** Git tag
> - (x) VOTE
> - (x) Copy the release artifacts from the staging spot to the dist spot in SVN
> - (x) Release staging repository at {{http://repository.apache.org/}}
> - (x) Update website
> - (x) Publish release announcement
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (UIMA-6349) japicmp post processing script fails with Java 16 (UIMAJ)
[
https://issues.apache.org/jira/browse/UIMA-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6349.
--
Resolution: Fixed
> japicmp post processing script fails with Java 16 (UIMAJ)
> -
>
> Key: UIMA-6349
> URL: https://issues.apache.org/jira/browse/UIMA-6349
> Project: UIMA
> Issue Type: Bug
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 2.11.0SDK, 3.2.0SDK
>
>
> When building the UIMA Java SDK with a Java 16 JDK, we get the following
> error:
> {quote}
> [ERROR] Failed to execute goal
> com.github.siom79.japicmp:japicmp-maven-plugin:0.14.4:cmp (default) on
> project uimaj-core: Execution of post-analysis script failed:
> javax.script.ScriptException: groovy.lang.MissingMethodException: No
> signature of method: java.lang.String.endsWith() is applicable for argument
> types: (java.lang.String) values: [_Type] -> [Help 1]
> {quote}
> Works with Java 15.
> The fix is apparently to force japicmp to use a new Groovy version:
> {code}
>
> com.github.siom79.japicmp
> japicmp-maven-plugin
> 0.15.3
>
>
> org.codehaus.groovy
> groovy-jsr223
> 2.5.14
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (UIMA-6351) japicmp post processing script fails with Java 16 (uimaFIT)
[
https://issues.apache.org/jira/browse/UIMA-6351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6351.
--
Resolution: Fixed
> japicmp post processing script fails with Java 16 (uimaFIT)
> ---
>
> Key: UIMA-6351
> URL: https://issues.apache.org/jira/browse/UIMA-6351
> Project: UIMA
> Issue Type: Bug
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 2.6.0uimaFIT, 3.2.0uimaFIT
>
>
> When building the UIMA Java SDK with a Java 16 JDK, we get the following
> error:
> {quote}
> [ERROR] Failed to execute goal
> com.github.siom79.japicmp:japicmp-maven-plugin:0.14.4:cmp (default) on
> project uimaj-core: Execution of post-analysis script failed:
> javax.script.ScriptException: groovy.lang.MissingMethodException: No
> signature of method: java.lang.String.endsWith() is applicable for argument
> types: (java.lang.String) values: [_Type] -> [Help 1]
> {quote}
> Works with Java 15.
> The fix is apparently to force japicmp to use a new Groovy version:
> {code}
>
> com.github.siom79.japicmp
> japicmp-maven-plugin
> 0.15.3
>
>
> org.codehaus.groovy
> groovy-jsr223
> 2.5.14
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work started] (UIMA-6351) CLONE - japicmp post processing script fails with Java 16 (uimaFIT)
[
https://issues.apache.org/jira/browse/UIMA-6351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-6351 started by Richard Eckart de Castilho.
> CLONE - japicmp post processing script fails with Java 16 (uimaFIT)
> ---
>
> Key: UIMA-6351
> URL: https://issues.apache.org/jira/browse/UIMA-6351
> Project: UIMA
> Issue Type: Bug
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 2.6.0uimaFIT, 3.2.0uimaFIT
>
>
> When building the UIMA Java SDK with a Java 16 JDK, we get the following
> error:
> {quote}
> [ERROR] Failed to execute goal
> com.github.siom79.japicmp:japicmp-maven-plugin:0.14.4:cmp (default) on
> project uimaj-core: Execution of post-analysis script failed:
> javax.script.ScriptException: groovy.lang.MissingMethodException: No
> signature of method: java.lang.String.endsWith() is applicable for argument
> types: (java.lang.String) values: [_Type] -> [Help 1]
> {quote}
> Works with Java 15.
> The fix is apparently to force japicmp to use a new Groovy version:
> {code}
>
> com.github.siom79.japicmp
> japicmp-maven-plugin
> 0.15.3
>
>
> org.codehaus.groovy
> groovy-jsr223
> 2.5.14
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (UIMA-6351) CLONE - japicmp post processing script fails with Java 16 (uimaFIT)
[
https://issues.apache.org/jira/browse/UIMA-6351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6351:
-
Component/s: uimaFIT
> CLONE - japicmp post processing script fails with Java 16 (uimaFIT)
> ---
>
> Key: UIMA-6351
> URL: https://issues.apache.org/jira/browse/UIMA-6351
> Project: UIMA
> Issue Type: Bug
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 2.6.0uimaFIT, 3.2.0uimaFIT
>
>
> When building the UIMA Java SDK with a Java 16 JDK, we get the following
> error:
> {quote}
> [ERROR] Failed to execute goal
> com.github.siom79.japicmp:japicmp-maven-plugin:0.14.4:cmp (default) on
> project uimaj-core: Execution of post-analysis script failed:
> javax.script.ScriptException: groovy.lang.MissingMethodException: No
> signature of method: java.lang.String.endsWith() is applicable for argument
> types: (java.lang.String) values: [_Type] -> [Help 1]
> {quote}
> Works with Java 15.
> The fix is apparently to force japicmp to use a new Groovy version:
> {code}
>
> com.github.siom79.japicmp
> japicmp-maven-plugin
> 0.15.3
>
>
> org.codehaus.groovy
> groovy-jsr223
> 2.5.14
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (UIMA-6351) japicmp post processing script fails with Java 16 (uimaFIT)
[
https://issues.apache.org/jira/browse/UIMA-6351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6351:
-
Summary: japicmp post processing script fails with Java 16 (uimaFIT) (was:
CLONE - japicmp post processing script fails with Java 16 (uimaFIT))
> japicmp post processing script fails with Java 16 (uimaFIT)
> ---
>
> Key: UIMA-6351
> URL: https://issues.apache.org/jira/browse/UIMA-6351
> Project: UIMA
> Issue Type: Bug
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 2.6.0uimaFIT, 3.2.0uimaFIT
>
>
> When building the UIMA Java SDK with a Java 16 JDK, we get the following
> error:
> {quote}
> [ERROR] Failed to execute goal
> com.github.siom79.japicmp:japicmp-maven-plugin:0.14.4:cmp (default) on
> project uimaj-core: Execution of post-analysis script failed:
> javax.script.ScriptException: groovy.lang.MissingMethodException: No
> signature of method: java.lang.String.endsWith() is applicable for argument
> types: (java.lang.String) values: [_Type] -> [Help 1]
> {quote}
> Works with Java 15.
> The fix is apparently to force japicmp to use a new Groovy version:
> {code}
>
> com.github.siom79.japicmp
> japicmp-maven-plugin
> 0.15.3
>
>
> org.codehaus.groovy
> groovy-jsr223
> 2.5.14
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (UIMA-6351) CLONE - japicmp post processing script fails with Java 16 (uimaFIT)
Richard Eckart de Castilho created UIMA-6351:
Summary: CLONE - japicmp post processing script fails with Java 16
(uimaFIT)
Key: UIMA-6351
URL: https://issues.apache.org/jira/browse/UIMA-6351
Project: UIMA
Issue Type: Bug
Reporter: Richard Eckart de Castilho
Assignee: Richard Eckart de Castilho
Fix For: 2.11.0SDK, 3.2.0SDK
When building the UIMA Java SDK with a Java 16 JDK, we get the following error:
{quote}
[ERROR] Failed to execute goal
com.github.siom79.japicmp:japicmp-maven-plugin:0.14.4:cmp (default) on project
uimaj-core: Execution of post-analysis script failed:
javax.script.ScriptException: groovy.lang.MissingMethodException: No signature
of method: java.lang.String.endsWith() is applicable for argument types:
(java.lang.String) values: [_Type] -> [Help 1]
{quote}
Works with Java 15.
The fix is apparently to force japicmp to use a new Groovy version:
{code}
com.github.siom79.japicmp
japicmp-maven-plugin
0.15.3
org.codehaus.groovy
groovy-jsr223
2.5.14
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (UIMA-6351) CLONE - japicmp post processing script fails with Java 16 (uimaFIT)
[
https://issues.apache.org/jira/browse/UIMA-6351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6351:
-
Fix Version/s: (was: 3.2.0SDK)
(was: 2.11.0SDK)
3.2.0uimaFIT
2.6.0uimaFIT
> CLONE - japicmp post processing script fails with Java 16 (uimaFIT)
> ---
>
> Key: UIMA-6351
> URL: https://issues.apache.org/jira/browse/UIMA-6351
> Project: UIMA
> Issue Type: Bug
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 2.6.0uimaFIT, 3.2.0uimaFIT
>
>
> When building the UIMA Java SDK with a Java 16 JDK, we get the following
> error:
> {quote}
> [ERROR] Failed to execute goal
> com.github.siom79.japicmp:japicmp-maven-plugin:0.14.4:cmp (default) on
> project uimaj-core: Execution of post-analysis script failed:
> javax.script.ScriptException: groovy.lang.MissingMethodException: No
> signature of method: java.lang.String.endsWith() is applicable for argument
> types: (java.lang.String) values: [_Type] -> [Help 1]
> {quote}
> Works with Java 15.
> The fix is apparently to force japicmp to use a new Groovy version:
> {code}
>
> com.github.siom79.japicmp
> japicmp-maven-plugin
> 0.15.3
>
>
> org.codehaus.groovy
> groovy-jsr223
> 2.5.14
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (UIMA-6350) japicmp post processing script fails with Java 16 (parent pom)
Richard Eckart de Castilho created UIMA-6350:
Summary: japicmp post processing script fails with Java 16 (parent
pom)
Key: UIMA-6350
URL: https://issues.apache.org/jira/browse/UIMA-6350
Project: UIMA
Issue Type: Bug
Components: Build, Packaging and Test
Reporter: Richard Eckart de Castilho
Assignee: Richard Eckart de Castilho
Fix For: parent-pom-15
When building the UIMA Java SDK with a Java 16 JDK, we get the following error:
{quote}
[ERROR] Failed to execute goal
com.github.siom79.japicmp:japicmp-maven-plugin:0.14.4:cmp (default) on project
uimaj-core: Execution of post-analysis script failed:
javax.script.ScriptException: groovy.lang.MissingMethodException: No signature
of method: java.lang.String.endsWith() is applicable for argument types:
(java.lang.String) values: [_Type] -> [Help 1]
{quote}
Works with Java 15.
The fix is apparently to force japicmp to use a new Groovy version:
{code}
com.github.siom79.japicmp
japicmp-maven-plugin
0.15.3
org.codehaus.groovy
groovy-jsr223
2.5.14
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (UIMA-6349) japicmp post processing script fails with Java 16 (UIMAJ)
[
https://issues.apache.org/jira/browse/UIMA-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6349:
-
Summary: japicmp post processing script fails with Java 16 (UIMAJ) (was:
japicmp post processing script fails with Java 16)
> japicmp post processing script fails with Java 16 (UIMAJ)
> -
>
> Key: UIMA-6349
> URL: https://issues.apache.org/jira/browse/UIMA-6349
> Project: UIMA
> Issue Type: Bug
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 2.11.0SDK, 3.2.0SDK
>
>
> When building the UIMA Java SDK with a Java 16 JDK, we get the following
> error:
> {quote}
> [ERROR] Failed to execute goal
> com.github.siom79.japicmp:japicmp-maven-plugin:0.14.4:cmp (default) on
> project uimaj-core: Execution of post-analysis script failed:
> javax.script.ScriptException: groovy.lang.MissingMethodException: No
> signature of method: java.lang.String.endsWith() is applicable for argument
> types: (java.lang.String) values: [_Type] -> [Help 1]
> {quote}
> Works with Java 15.
> The fix is apparently to force japicmp to use a new Groovy version:
> {code}
>
> com.github.siom79.japicmp
> japicmp-maven-plugin
> 0.15.3
>
>
> org.codehaus.groovy
> groovy-jsr223
> 2.5.14
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (UIMA-6349) japicmp post processing script fails with Java 16
[
https://issues.apache.org/jira/browse/UIMA-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17322081#comment-17322081
]
Richard Eckart de Castilho commented on UIMA-6349:
--
I will fix this locally in UIMAJ now and subsequently in uimaFIT and Ruta and
later fix it in the parent pom along with further updates for a future release.
> japicmp post processing script fails with Java 16
> -
>
> Key: UIMA-6349
> URL: https://issues.apache.org/jira/browse/UIMA-6349
> Project: UIMA
> Issue Type: Bug
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 2.11.0SDK, 3.2.0SDK
>
>
> When building the UIMA Java SDK with a Java 16 JDK, we get the following
> error:
> {quote}
> [ERROR] Failed to execute goal
> com.github.siom79.japicmp:japicmp-maven-plugin:0.14.4:cmp (default) on
> project uimaj-core: Execution of post-analysis script failed:
> javax.script.ScriptException: groovy.lang.MissingMethodException: No
> signature of method: java.lang.String.endsWith() is applicable for argument
> types: (java.lang.String) values: [_Type] -> [Help 1]
> {quote}
> Works with Java 15.
> The fix is apparently to force japicmp to use a new Groovy version:
> {code}
>
> com.github.siom79.japicmp
> japicmp-maven-plugin
> 0.15.3
>
>
> org.codehaus.groovy
> groovy-jsr223
> 2.5.14
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (UIMA-6349) japicmp post processing script fails with Java 16
[
https://issues.apache.org/jira/browse/UIMA-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6349:
-
Fix Version/s: 3.2.0SDK
2.11.0SDK
> japicmp post processing script fails with Java 16
> -
>
> Key: UIMA-6349
> URL: https://issues.apache.org/jira/browse/UIMA-6349
> Project: UIMA
> Issue Type: Bug
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 2.11.0SDK, 3.2.0SDK
>
>
> When building the UIMA Java SDK with a Java 16 JDK, we get the following
> error:
> {quote}
> [ERROR] Failed to execute goal
> com.github.siom79.japicmp:japicmp-maven-plugin:0.14.4:cmp (default) on
> project uimaj-core: Execution of post-analysis script failed:
> javax.script.ScriptException: groovy.lang.MissingMethodException: No
> signature of method: java.lang.String.endsWith() is applicable for argument
> types: (java.lang.String) values: [_Type] -> [Help 1]
> {quote}
> Works with Java 15.
> The fix is apparently to force japicmp to use a new Groovy version:
> {code}
>
> com.github.siom79.japicmp
> japicmp-maven-plugin
> 0.15.3
>
>
> org.codehaus.groovy
> groovy-jsr223
> 2.5.14
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (UIMA-6349) japicmp post processing script fails with Java 16
[
https://issues.apache.org/jira/browse/UIMA-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6349:
-
Description:
When building the UIMA Java SDK with a Java 16 JDK, we get the following error:
{quote}
[ERROR] Failed to execute goal
com.github.siom79.japicmp:japicmp-maven-plugin:0.14.4:cmp (default) on project
uimaj-core: Execution of post-analysis script failed:
javax.script.ScriptException: groovy.lang.MissingMethodException: No signature
of method: java.lang.String.endsWith() is applicable for argument types:
(java.lang.String) values: [_Type] -> [Help 1]
{quote}
Works with Java 15.
The fix is apparently to force japicmp to use a new Groovy version:
{code}
com.github.siom79.japicmp
japicmp-maven-plugin
0.15.3
org.codehaus.groovy
groovy-jsr223
2.5.14
{code}
was:
When building the UIMA Java SDK with a Java 16 JDK, we get the following error:
{quote}
[ERROR] Failed to execute goal
com.github.siom79.japicmp:japicmp-maven-plugin:0.14.4:cmp (default) on project
uimaj-core: Execution of post-analysis script failed:
javax.script.ScriptException: groovy.lang.MissingMethodException: No signature
of method: java.lang.String.endsWith() is applicable for argument types:
(java.lang.String) values: [_Type] -> [Help 1]
{quote}
Works with Java 15.
> japicmp post processing script fails with Java 16
> -
>
> Key: UIMA-6349
> URL: https://issues.apache.org/jira/browse/UIMA-6349
> Project: UIMA
> Issue Type: Bug
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> When building the UIMA Java SDK with a Java 16 JDK, we get the following
> error:
> {quote}
> [ERROR] Failed to execute goal
> com.github.siom79.japicmp:japicmp-maven-plugin:0.14.4:cmp (default) on
> project uimaj-core: Execution of post-analysis script failed:
> javax.script.ScriptException: groovy.lang.MissingMethodException: No
> signature of method: java.lang.String.endsWith() is applicable for argument
> types: (java.lang.String) values: [_Type] -> [Help 1]
> {quote}
> Works with Java 15.
> The fix is apparently to force japicmp to use a new Groovy version:
> {code}
>
> com.github.siom79.japicmp
> japicmp-maven-plugin
> 0.15.3
>
>
> org.codehaus.groovy
> groovy-jsr223
> 2.5.14
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (UIMA-6349) japicmp post processing script fails with Java 16
Richard Eckart de Castilho created UIMA-6349:
Summary: japicmp post processing script fails with Java 16
Key: UIMA-6349
URL: https://issues.apache.org/jira/browse/UIMA-6349
Project: UIMA
Issue Type: Bug
Reporter: Richard Eckart de Castilho
Assignee: Richard Eckart de Castilho
When building the UIMA Java SDK with a Java 16 JDK, we get the following error:
{quote}
[ERROR] Failed to execute goal
com.github.siom79.japicmp:japicmp-maven-plugin:0.14.4:cmp (default) on project
uimaj-core: Execution of post-analysis script failed:
javax.script.ScriptException: groovy.lang.MissingMethodException: No signature
of method: java.lang.String.endsWith() is applicable for argument types:
(java.lang.String) values: [_Type] -> [Help 1]
{quote}
Works with Java 15.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (UIMA-6348) Race-condition in TypeSystemImpl commit
[
https://issues.apache.org/jira/browse/UIMA-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6348.
--
Resolution: Fixed
> Race-condition in TypeSystemImpl commit
> ---
>
> Key: UIMA-6348
> URL: https://issues.apache.org/jira/browse/UIMA-6348
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.2.0SDK
>
>
> In principle, it is possible to obtain a type object from one CAS and to use
> that type object to create a feature structure in another CAS:
> {code}
> TypeSystemDescription tsdA = new TypeSystemDescription_impl();
> tsdA.addType(MY_TYPE, "", CAS.TYPE_NAME_ANNOTATION);
> TypeSystemDescription tsdB = new TypeSystemDescription_impl();
> tsdB.addType(MY_TYPE, "", CAS.TYPE_NAME_ANNOTATION);
> CAS casA = CasCreationUtils.createCas(tsdA, null, null, null);
> CAS casB = CasCreationUtils.createCas(tsdB, null, null, null);
>
> Type typeA = casA.getTypeSystem().getType(MY_TYPE);
> Annotation annB = (Annotation) casB.createAnnotation(typeA, 0, 0);
> annB.addToIndexes();
> casB.removeFsFromIndexes(annB);
> {code}
> If both CASes have been initialized with a semantically equivalent type
> system, UIMA will actually return the same type object in this case due to
> "typesystem consolidation" being performed in the TypeSystemImpl. However, if
> we turn off typesystem consolidation or if the type systems are different and
> just incidentally use the same type names, the type object is different.
> In highly concurrent situations, the synchronization in TypeSystemImpl.commit
> is insufficient to ensure that the consolidated type system is always
> returned. This leads to a situation where more than one type system instance
> with the same type may exist.
> Finally, there is a sanity check done in sorted FS indexes that the type of
> the index corresponds to the type of the feature structure being removed. If
> type consolidation worked, this is the case - but not if it failed due to the
> insufficient synchronization
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (UIMA-6348) Race-condition in TypeSystemImpl commit
[
https://issues.apache.org/jira/browse/UIMA-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17312321#comment-17312321
]
Richard Eckart de Castilho commented on UIMA-6348:
--
Consider the case where you have two CAS instances (cas1 and cas2) with the
same type system.
In this case, you can fetch a Type object from cas1 and use it to create
an annotation in cas2:
Type t = cas1.getTypeSystem().getType("my.Type");
AnnotationFS fs = cas2.createAnnotation(t);
cas2.addFsToIndexes(fs);
If the type systems in cas1 and cas2 are different, then this is can be
problematic
of course.
UIMAv3 tries to ensure that for two CASes that share a semantically equivalent
type system, the actual same TypeSystemImpl instance is used. So normally, we
see
that if the type systems are equivalent (even though the CASes may have been
created using different XML descriptor files (with the same content)). This
feature
of UIMAv3 is called "type system consolidation".
cas1.getTypeSystem().getType("my.Type") ==
cas2.getTypeSystem().getType("my.Type")
In principle, even without type system consolidation (if the type instances are
not
the same), the code usually works if the type definitions are semantically
equivalent.
But the user may not get notified about the problem or may just experience weird
behavior.
Incidentally, when an annotation is *removed* from the CAS, UIMAv3 actually
verifies
if the type of the annotation being removed matches the CAS type system - and
if this
is not the case, it throws an exception.
UIMA 3.1.1 has a BU WHERE TYPE CONSOLIDATION MAY FAIL in a multi-threaded
environment. This can later cause an exception to be thrown when this
annotation is
*removed* again from the CAS (because that is currently the only place where
this is
checked).
A fix for that multi-threading bug is en route.
Now, I would like to extend the check that is currently only being made in 1 of
2
possible cases of removal of annotations to:
- both removal cases
- also to the case of adding an annotations to the CAS
- and also to the case of creating an annotations from the CAS
In principle that could break user code that is currently working by chance.
For that reason, I would add a system property by which the check can be
DISABLED
if necessary until the problematic user code is fixed.
An alternative could be to not check by default and install a system property to
ENABLE the check - risking that user code could exhibit odd behavior without
quickly informing the user about the problem.
... actually, thinking of it after writing this longisch mail, I'll make it so
that
the checks are present, but instead of failing hard by default, they'll log
warnings.
That would alert users about the issue without breaking their code.
> Race-condition in TypeSystemImpl commit
> ---
>
> Key: UIMA-6348
> URL: https://issues.apache.org/jira/browse/UIMA-6348
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.2.0SDK
>
>
> In principle, it is possible to obtain a type object from one CAS and to use
> that type object to create a feature structure in another CAS:
> {code}
> TypeSystemDescription tsdA = new TypeSystemDescription_impl();
> tsdA.addType(MY_TYPE, "", CAS.TYPE_NAME_ANNOTATION);
> TypeSystemDescription tsdB = new TypeSystemDescription_impl();
> tsdB.addType(MY_TYPE, "", CAS.TYPE_NAME_ANNOTATION);
> CAS casA = CasCreationUtils.createCas(tsdA, null, null, null);
> CAS casB = CasCreationUtils.createCas(tsdB, null, null, null);
>
> Type typeA = casA.getTypeSystem().getType(MY_TYPE);
> Annotation annB = (Annotation) casB.createAnnotation(typeA, 0, 0);
> annB.addToIndexes();
> casB.removeFsFromIndexes(annB);
> {code}
> If both CASes have been initialized with a semantically equivalent type
> system, UIMA will actually return the same type object in this case due to
> "typesystem consolidation" being performed in the TypeSystemImpl. However, if
> we turn off typesystem consolidation or if the type systems are different and
> just incidentally use the same type names, the type object is different.
> In highly concurrent situations, the synchronization in TypeSystemImpl.commit
> is insufficient to ensure that the consolidated type system is always
> returned. This leads to a situation where more than one type system instance
> with the same type may exist.
> Finally, there is a sanity check done in sorted FS indexes that the type of
> the index corresponds to the type of the feature structure being removed. If
> type consolidation worked, this is the case - but not if it failed due to the
> insufficient synchronization
--
[jira] [Work started] (UIMA-6348) Race-condition in TypeSystemImpl commit
[
https://issues.apache.org/jira/browse/UIMA-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-6348 started by Richard Eckart de Castilho.
> Race-condition in TypeSystemImpl commit
> ---
>
> Key: UIMA-6348
> URL: https://issues.apache.org/jira/browse/UIMA-6348
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.2.0SDK
>
>
> In principle, it is possible to obtain a type object from one CAS and to use
> that type object to create a feature structure in another CAS:
> {code}
> TypeSystemDescription tsdA = new TypeSystemDescription_impl();
> tsdA.addType(MY_TYPE, "", CAS.TYPE_NAME_ANNOTATION);
> TypeSystemDescription tsdB = new TypeSystemDescription_impl();
> tsdB.addType(MY_TYPE, "", CAS.TYPE_NAME_ANNOTATION);
> CAS casA = CasCreationUtils.createCas(tsdA, null, null, null);
> CAS casB = CasCreationUtils.createCas(tsdB, null, null, null);
>
> Type typeA = casA.getTypeSystem().getType(MY_TYPE);
> Annotation annB = (Annotation) casB.createAnnotation(typeA, 0, 0);
> annB.addToIndexes();
> casB.removeFsFromIndexes(annB);
> {code}
> If both CASes have been initialized with a semantically equivalent type
> system, UIMA will actually return the same type object in this case due to
> "typesystem consolidation" being performed in the TypeSystemImpl. However, if
> we turn off typesystem consolidation or if the type systems are different and
> just incidentally use the same type names, the type object is different.
> In highly concurrent situations, the synchronization in TypeSystemImpl.commit
> is insufficient to ensure that the consolidated type system is always
> returned. This leads to a situation where more than one type system instance
> with the same type may exist.
> Finally, there is a sanity check done in sorted FS indexes that the type of
> the index corresponds to the type of the feature structure being removed. If
> type consolidation worked, this is the case - but not if it failed due to the
> insufficient synchronization
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (UIMA-6348) Race-condition in TypeSystemImpl commit
Richard Eckart de Castilho created UIMA-6348:
Summary: Race-condition in TypeSystemImpl commit
Key: UIMA-6348
URL: https://issues.apache.org/jira/browse/UIMA-6348
Project: UIMA
Issue Type: Bug
Components: Core Java Framework
Reporter: Richard Eckart de Castilho
Assignee: Richard Eckart de Castilho
Fix For: 3.2.0SDK
In principle, it is possible to obtain a type object from one CAS and to use
that type object to create a feature structure in another CAS:
{code}
TypeSystemDescription tsdA = new TypeSystemDescription_impl();
tsdA.addType(MY_TYPE, "", CAS.TYPE_NAME_ANNOTATION);
TypeSystemDescription tsdB = new TypeSystemDescription_impl();
tsdB.addType(MY_TYPE, "", CAS.TYPE_NAME_ANNOTATION);
CAS casA = CasCreationUtils.createCas(tsdA, null, null, null);
CAS casB = CasCreationUtils.createCas(tsdB, null, null, null);
Type typeA = casA.getTypeSystem().getType(MY_TYPE);
Annotation annB = (Annotation) casB.createAnnotation(typeA, 0, 0);
annB.addToIndexes();
casB.removeFsFromIndexes(annB);
{code}
If both CASes have been initialized with a semantically equivalent type system,
UIMA will actually return the same type object in this case due to "typesystem
consolidation" being performed in the TypeSystemImpl. However, if we turn off
typesystem consolidation or if the type systems are different and just
incidentally use the same type names, the type object is different.
In highly concurrent situations, the synchronization in TypeSystemImpl.commit
is insufficient to ensure that the consolidated type system is always returned.
This leads to a situation where more than one type system instance with the
same type may exist.
Finally, there is a sanity check done in sorted FS indexes that the type of the
index corresponds to the type of the feature structure being removed. If type
consolidation worked, this is the case - but not if it failed due to the
insufficient synchronization
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (UIMA-6299) Ensure that SNAPSHOT repos are commented out in POMs
[ https://issues.apache.org/jira/browse/UIMA-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6299. -- Resolution: Fixed > Ensure that SNAPSHOT repos are commented out in POMs > > > Key: UIMA-6299 > URL: https://issues.apache.org/jira/browse/UIMA-6299 > Project: UIMA > Issue Type: Task > Components: Core Java Framework, uimaFIT >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 2.6.0uimaFIT, 3.2.0uimaFIT, 2.11.0SDK, 3.2.0SDK > > > Ensure that SNAPSHOT repos are commented out in POMs. > - (/) for UIMA 2.11.0 > - (/) for UIMA 3.2.0 > - (/) for uimaFIT 2.6.0 > - (/) for uimaFIT 3.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6299) Ensure that SNAPSHOT repos are commented out in POMs
[ https://issues.apache.org/jira/browse/UIMA-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6299: - Description: Ensure that SNAPSHOT repos are commented out in POMs. - (/) for UIMA 2.11.0 - (/) for UIMA 3.2.0 - (/) for uimaFIT 2.6.0 - (/) for uimaFIT 3.2.0 was: Ensure that SNAPSHOT repos are commented out in POMs. - (/) for UIMA 2.11.0 - (/) for UIMA 3.2.0 - (/) for uimaFIT 2.6.0 - (x) for uimaFIT 3.2.0 > Ensure that SNAPSHOT repos are commented out in POMs > > > Key: UIMA-6299 > URL: https://issues.apache.org/jira/browse/UIMA-6299 > Project: UIMA > Issue Type: Task > Components: Core Java Framework, uimaFIT >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 2.6.0uimaFIT, 3.2.0uimaFIT, 2.11.0SDK, 3.2.0SDK > > > Ensure that SNAPSHOT repos are commented out in POMs. > - (/) for UIMA 2.11.0 > - (/) for UIMA 3.2.0 > - (/) for uimaFIT 2.6.0 > - (/) for uimaFIT 3.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (UIMA-6341) Try out p2-layout-resolver
[ https://issues.apache.org/jira/browse/UIMA-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6341. -- Resolution: Fixed > Try out p2-layout-resolver > -- > > Key: UIMA-6341 > URL: https://issues.apache.org/jira/browse/UIMA-6341 > Project: UIMA > Issue Type: Improvement > Components: Ruta >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 2.11.0SDK, 3.2.0SDK, 2.9.0ruta, 3.1.0ruta > > > Try out p2-layout-resolver for fetching Eclipse dependencies from P2 > repositories. > Right now, we get the dependencies for our Eclipse plugins from Maven > Central. This is a pain because every time that Eclipse issues a new release, > they push new dependencies to Maven Central causing that the dependency > ranges we have to resolve to different artifacts and the transitive > dependencies of these new artifacts may not be on Maven Central. > If we drop the ranges, we either have to re-add them at a different level > (i.e. when generating the Eclipse plugin descriptors) so that users can > actually install our plugins in different versions of Eclipse. > The hope is that using the p2-layout-resolve we can: > * obtain the Eclipse artifacts from P2 repository - so we are not limited to > what is available on Maven Central > * we can more easily bind to a particular Eclipse release by using the P2 > repo of that release > * our builds do not break every few months when new Eclipse releases are > pushed to Maven Central -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-5096) ExternalResourceFactory.createExternalResourceDescription does not accept non-string parameters
[
https://issues.apache.org/jira/browse/UIMA-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-5096:
-
Fix Version/s: (was: 3.2.0uimaFIT)
> ExternalResourceFactory.createExternalResourceDescription does not accept
> non-string parameters
> ---
>
> Key: UIMA-5096
> URL: https://issues.apache.org/jira/browse/UIMA-5096
> Project: UIMA
> Issue Type: Bug
> Components: uimaFIT
>Affects Versions: 2.2.0uimaFIT
> Environment: Java
>Reporter: Asher Stern
>Priority: Major
>
> In
> {noformat}
> org.apache.uima.fit.factory.ExternalResourceFactory
> {noformat}
> the method
> {noformat}
> public static ExternalResourceDescription
> createExternalResourceDescription(Class aInterface,
> Object... aParams)
> {noformat}
> does not accept non-string parameters.
> Example:
> The following works:
> Caller:
> {noformat}
> ExternalResourceDescription geographicalResourceDescription =
> ExternalResourceFactory.createExternalResourceDescription(
>
> GeographicalResourceImplementation.class,
> GeographicalResource.MAX_LENGTH_PARAMETER, String.valueOf(5),
> );
> {noformat}
> Resource:
> {noformat}
> @ConfigurationParameter(name = MAX_LENGTH_PARAMETER)
> private String maxLengthString;
> {noformat}
> The following fails:
> Caller:
> {noformat}
> ExternalResourceDescription geographicalResourceDescription =
> ExternalResourceFactory.createExternalResourceDescription(
>
> GeographicalResourceImplementation.class,
> GeographicalResource.MAX_LENGTH_PARAMETER, 5,
> );
> {noformat}
> Resource:
> {noformat}
> @ConfigurationParameter(name = MAX_LENGTH_PARAMETER)
> private int maxLength;
> {noformat}
> The exception is:
> {noformat}
> java.lang.ClassCastException: java.lang.Integer cannot be cast to
> java.lang.String
> at
> org.apache.uima.fit.factory.ExternalResourceFactory.createExternalResourceDescription(ExternalResourceFactory.java:177)
> at
> org.apache.uima.fit.factory.ExternalResourceFactory.createExternalResourceDescription(ExternalResourceFactory.java:122)
> ...
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (UIMA-4571) ConfigurationParameterFactory.setParameter() should attempt type coercion
[ https://issues.apache.org/jira/browse/UIMA-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-4571: - Fix Version/s: (was: 3.2.0uimaFIT) > ConfigurationParameterFactory.setParameter() should attempt type coercion > - > > Key: UIMA-4571 > URL: https://issues.apache.org/jira/browse/UIMA-4571 > Project: UIMA > Issue Type: Bug > Components: uimaFIT >Reporter: Richard Eckart de Castilho >Priority: Major > > ConfigurationParameterFactory.createConfigurationData() does try all kinds of > type conversions to coerce values that UIMA doesn't know into parameters. > However, ConfigurationParameterFactory.setParameter() doesn't try any of this > yet. At least for those cases where the resource specifiers accept > ConfigurationParameter-type parameters, this can be easily implemented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (UIMA-6342) Moving iterator beyond bounds does not invalidate it
[
https://issues.apache.org/jira/browse/UIMA-6342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6342.
--
Resolution: Fixed
> Moving iterator beyond bounds does not invalidate it
>
>
> Key: UIMA-6342
> URL: https://issues.apache.org/jira/browse/UIMA-6342
> Project: UIMA
> Issue Type: Bug
> Components: UIMA
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.2.0SDK
>
>
> {code}
> @Test
> public void thatSeekingIteratorToOutOfIndexPositionOnRightIsInvalid()
> throws Exception {
> TypeSystemDescription tsd =
> getResourceSpecifierFactory().createTypeSystemDescription();
> tsd.addType("test.Type1", "", CAS.TYPE_NAME_ANNOTATION);
> tsd.addType("test.Type2", "", CAS.TYPE_NAME_ANNOTATION);
> tsd.addType("test.Type3", "", CAS.TYPE_NAME_ANNOTATION);
>
> CAS cas = CasCreationUtils.createCas(tsd, null, null, null);
>
> Type type1 = cas.getTypeSystem().getType("test.Type1");
> Type type2 = cas.getTypeSystem().getType("test.Type2");
> Type type3 = cas.getTypeSystem().getType("test.Type3");
>
> AnnotationFS window, seekPoint;
> addToIndexes(
> window = cas.createAnnotation(type1, 0, 10),
> cas.createAnnotation(type2, 5, 6),
> seekPoint = cas.createAnnotation(type3, 8, 9),
> cas.createAnnotation(type2, 15, 16));
>
> FSIterator it =
> cas.getAnnotationIndex(type2).select().coveredBy(window).fsIterator();
>
> it.moveTo(seekPoint);
> // Iterator should be invalid at this point because the insertion points
> is right of [5,6]
> assertThat(it.isValid()).isFalse();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (UIMA-6341) Try out p2-layout-resolver
[ https://issues.apache.org/jira/browse/UIMA-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6341: - Fix Version/s: 2.11.0SDK > Try out p2-layout-resolver > -- > > Key: UIMA-6341 > URL: https://issues.apache.org/jira/browse/UIMA-6341 > Project: UIMA > Issue Type: Improvement > Components: Ruta >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 2.11.0SDK, 3.2.0SDK, 2.9.0ruta, 3.1.0ruta > > > Try out p2-layout-resolver for fetching Eclipse dependencies from P2 > repositories. > Right now, we get the dependencies for our Eclipse plugins from Maven > Central. This is a pain because every time that Eclipse issues a new release, > they push new dependencies to Maven Central causing that the dependency > ranges we have to resolve to different artifacts and the transitive > dependencies of these new artifacts may not be on Maven Central. > If we drop the ranges, we either have to re-add them at a different level > (i.e. when generating the Eclipse plugin descriptors) so that users can > actually install our plugins in different versions of Eclipse. > The hope is that using the p2-layout-resolve we can: > * obtain the Eclipse artifacts from P2 repository - so we are not limited to > what is available on Maven Central > * we can more easily bind to a particular Eclipse release by using the P2 > repo of that release > * our builds do not break every few months when new Eclipse releases are > pushed to Maven Central -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6341) Try out p2-layout-resolver
[ https://issues.apache.org/jira/browse/UIMA-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6341: - Description: Try out p2-layout-resolver for fetching Eclipse dependencies from P2 repositories. Right now, we get the dependencies for our Eclipse plugins from Maven Central. This is a pain because every time that Eclipse issues a new release, they push new dependencies to Maven Central causing that the dependency ranges we have to resolve to different artifacts and the transitive dependencies of these new artifacts may not be on Maven Central. If we drop the ranges, we either have to re-add them at a different level (i.e. when generating the Eclipse plugin descriptors) so that users can actually install our plugins in different versions of Eclipse. The hope is that using the p2-layout-resolve we can: * obtain the Eclipse artifacts from P2 repository - so we are not limited to what is available on Maven Central * we can more easily bind to a particular Eclipse release by using the P2 repo of that release * our builds do not break every few months when new Eclipse releases are pushed to Maven Central was: Try out p2-layout-resolver for fetching Eclipse dependencies from P2 repositories > Try out p2-layout-resolver > -- > > Key: UIMA-6341 > URL: https://issues.apache.org/jira/browse/UIMA-6341 > Project: UIMA > Issue Type: Improvement > Components: Ruta >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > > Try out p2-layout-resolver for fetching Eclipse dependencies from P2 > repositories. > Right now, we get the dependencies for our Eclipse plugins from Maven > Central. This is a pain because every time that Eclipse issues a new release, > they push new dependencies to Maven Central causing that the dependency > ranges we have to resolve to different artifacts and the transitive > dependencies of these new artifacts may not be on Maven Central. > If we drop the ranges, we either have to re-add them at a different level > (i.e. when generating the Eclipse plugin descriptors) so that users can > actually install our plugins in different versions of Eclipse. > The hope is that using the p2-layout-resolve we can: > * obtain the Eclipse artifacts from P2 repository - so we are not limited to > what is available on Maven Central > * we can more easily bind to a particular Eclipse release by using the P2 > repo of that release > * our builds do not break every few months when new Eclipse releases are > pushed to Maven Central -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6341) Try out p2-layout-resolver
[ https://issues.apache.org/jira/browse/UIMA-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6341: - Fix Version/s: 3.1.0ruta 3.2.0SDK > Try out p2-layout-resolver > -- > > Key: UIMA-6341 > URL: https://issues.apache.org/jira/browse/UIMA-6341 > Project: UIMA > Issue Type: Improvement > Components: Ruta >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.2.0SDK, 3.1.0ruta > > > Try out p2-layout-resolver for fetching Eclipse dependencies from P2 > repositories. > Right now, we get the dependencies for our Eclipse plugins from Maven > Central. This is a pain because every time that Eclipse issues a new release, > they push new dependencies to Maven Central causing that the dependency > ranges we have to resolve to different artifacts and the transitive > dependencies of these new artifacts may not be on Maven Central. > If we drop the ranges, we either have to re-add them at a different level > (i.e. when generating the Eclipse plugin descriptors) so that users can > actually install our plugins in different versions of Eclipse. > The hope is that using the p2-layout-resolve we can: > * obtain the Eclipse artifacts from P2 repository - so we are not limited to > what is available on Maven Central > * we can more easily bind to a particular Eclipse release by using the P2 > repo of that release > * our builds do not break every few months when new Eclipse releases are > pushed to Maven Central -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (UIMA-6341) Try out p2-layout-resolver
[ https://issues.apache.org/jira/browse/UIMA-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-6341 started by Richard Eckart de Castilho. > Try out p2-layout-resolver > -- > > Key: UIMA-6341 > URL: https://issues.apache.org/jira/browse/UIMA-6341 > Project: UIMA > Issue Type: Improvement > Components: Ruta >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > > Try out p2-layout-resolver for fetching Eclipse dependencies from P2 > repositories. > Right now, we get the dependencies for our Eclipse plugins from Maven > Central. This is a pain because every time that Eclipse issues a new release, > they push new dependencies to Maven Central causing that the dependency > ranges we have to resolve to different artifacts and the transitive > dependencies of these new artifacts may not be on Maven Central. > If we drop the ranges, we either have to re-add them at a different level > (i.e. when generating the Eclipse plugin descriptors) so that users can > actually install our plugins in different versions of Eclipse. > The hope is that using the p2-layout-resolve we can: > * obtain the Eclipse artifacts from P2 repository - so we are not limited to > what is available on Maven Central > * we can more easily bind to a particular Eclipse release by using the P2 > repo of that release > * our builds do not break every few months when new Eclipse releases are > pushed to Maven Central -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (UIMA-6342) Moving iterator beyond bounds does not invalidate it
Richard Eckart de Castilho created UIMA-6342:
Summary: Moving iterator beyond bounds does not invalidate it
Key: UIMA-6342
URL: https://issues.apache.org/jira/browse/UIMA-6342
Project: UIMA
Issue Type: Bug
Components: UIMA
Reporter: Richard Eckart de Castilho
Assignee: Richard Eckart de Castilho
Fix For: 3.2.0SDK
{code}
@Test
public void thatSeekingIteratorToOutOfIndexPositionOnRightIsInvalid() throws
Exception {
TypeSystemDescription tsd =
getResourceSpecifierFactory().createTypeSystemDescription();
tsd.addType("test.Type1", "", CAS.TYPE_NAME_ANNOTATION);
tsd.addType("test.Type2", "", CAS.TYPE_NAME_ANNOTATION);
tsd.addType("test.Type3", "", CAS.TYPE_NAME_ANNOTATION);
CAS cas = CasCreationUtils.createCas(tsd, null, null, null);
Type type1 = cas.getTypeSystem().getType("test.Type1");
Type type2 = cas.getTypeSystem().getType("test.Type2");
Type type3 = cas.getTypeSystem().getType("test.Type3");
AnnotationFS window, seekPoint;
addToIndexes(
window = cas.createAnnotation(type1, 0, 10),
cas.createAnnotation(type2, 5, 6),
seekPoint = cas.createAnnotation(type3, 8, 9),
cas.createAnnotation(type2, 15, 16));
FSIterator it =
cas.getAnnotationIndex(type2).select().coveredBy(window).fsIterator();
it.moveTo(seekPoint);
// Iterator should be invalid at this point because the insertion points is
right of [5,6]
assertThat(it.isValid()).isFalse();
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (UIMA-6341) Try out p2-layout-resolver
Richard Eckart de Castilho created UIMA-6341: Summary: Try out p2-layout-resolver Key: UIMA-6341 URL: https://issues.apache.org/jira/browse/UIMA-6341 Project: UIMA Issue Type: Improvement Components: Ruta Reporter: Richard Eckart de Castilho Assignee: Richard Eckart de Castilho Try out p2-layout-resolver for fetching Eclipse dependencies from P2 repositories -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (UIMA-6203) Add SerialFormat.XMI_PRETTY
[ https://issues.apache.org/jira/browse/UIMA-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6203. -- Resolution: Fixed > Add SerialFormat.XMI_PRETTY > --- > > Key: UIMA-6203 > URL: https://issues.apache.org/jira/browse/UIMA-6203 > Project: UIMA > Issue Type: New Feature > Components: Core Java Framework >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.2.0SDK > > > It would be nice to have a SerialFormat.XMI_PRETTY which pretty-prints the > written XMI. The SerialFormat.XMI writes everything into a single line which > is quite unreadable with the human eye. -- This message was sent by Atlassian Jira (v8.3.4#803005)
