[jira] [Commented] (UIMA-6453) Invalid SHA512 generated for Maven artifacts
[
https://issues.apache.org/jira/browse/UIMA-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536559#comment-17536559
]
Richard Eckart de Castilho commented on UIMA-6453:
--
For good measure, I mirrored the {{org.apache.uima}} folder of Maven Central
and checked the GPG signatures. These appear to be fully present and valid.
> Invalid SHA512 generated for Maven artifacts
>
>
> Key: UIMA-6453
> URL: https://issues.apache.org/jira/browse/UIMA-6453
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test
>Affects Versions: 3.2.0uimaFIT, 3.2.0SDK, 3.1.0ruta, 3.3.0SDK
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.3.0uimaFIT, parent-pom-15, 3.3.1SDK, 3.2.0ruta
>
>
> The SHA512 signature files we generate for the Maven artifacts overwrite each
> other. E.g. in the recent uimaFIT 3.3.0 RC 2, I found:
> {noformat}
> % cat
> org/apache/uima/uimafit-maven-plugin/3.3.0/uimafit-maven-plugin-3.3.0.sha512
> 4db94daceccf1727b1620a20a708eb1830a95fa8ad967219ad7fff537bf845055174f659b43f3bb827cd1296d4608c10b3f36306a76da4dd27af50a45517bb2f
> uimafit-maven-plugin-3.3.0-javadoc.jar
> {noformat}
> Looking at Maven Central, I can see such bad signatures in multiple releases:
> *UIMAJ*
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.1.1/ - looks ok
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.2.0/ - BAD
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.3.0/ - BAD
> (latest version)
>
> *uimaFIT*
> * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.1.0/ - looks
> ok
> * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.2.0/ - BAD
> (latest version)
>
> *RUTA*
> * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.0.1/ - looks ok
> * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.1.0/ - BAD
> (latest version)
> *UIMA-AS*
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-as-core/2.9.0/ - last
> release seems to have been before the SHA512 requirement
> *DUCC*
> * https://repo1.maven.org/maven2/org/apache/uima/uima-ducc-common/3.0.0/ -
> looks ok (latest version)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Work started] (UIMA-6453) Invalid SHA512 generated for Maven artifacts
[
https://issues.apache.org/jira/browse/UIMA-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-6453 started by Richard Eckart de Castilho.
> Invalid SHA512 generated for Maven artifacts
>
>
> Key: UIMA-6453
> URL: https://issues.apache.org/jira/browse/UIMA-6453
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test
>Affects Versions: 3.2.0uimaFIT, 3.2.0SDK, 3.1.0ruta, 3.3.0SDK
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.3.0uimaFIT, parent-pom-15, 3.3.1SDK, 3.2.0ruta
>
>
> The SHA512 signature files we generate for the Maven artifacts overwrite each
> other. E.g. in the recent uimaFIT 3.3.0 RC 2, I found:
> {noformat}
> % cat
> org/apache/uima/uimafit-maven-plugin/3.3.0/uimafit-maven-plugin-3.3.0.sha512
> 4db94daceccf1727b1620a20a708eb1830a95fa8ad967219ad7fff537bf845055174f659b43f3bb827cd1296d4608c10b3f36306a76da4dd27af50a45517bb2f
> uimafit-maven-plugin-3.3.0-javadoc.jar
> {noformat}
> Looking at Maven Central, I can see such bad signatures in multiple releases:
> *UIMAJ*
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.1.1/ - looks ok
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.2.0/ - BAD
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.3.0/ - BAD
> (latest version)
>
> *uimaFIT*
> * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.1.0/ - looks
> ok
> * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.2.0/ - BAD
> (latest version)
>
> *RUTA*
> * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.0.1/ - looks ok
> * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.1.0/ - BAD
> (latest version)
> *UIMA-AS*
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-as-core/2.9.0/ - last
> release seems to have been before the SHA512 requirement
> *DUCC*
> * https://repo1.maven.org/maven2/org/apache/uima/uima-ducc-common/3.0.0/ -
> looks ok (latest version)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Work started] (UIMA-6450) Generated SHA512 files not verifiable using sha512sum --check
[
https://issues.apache.org/jira/browse/UIMA-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-6450 started by Richard Eckart de Castilho.
> Generated SHA512 files not verifiable using sha512sum --check
> -
>
> Key: UIMA-6450
> URL: https://issues.apache.org/jira/browse/UIMA-6450
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: parent-pom-15, 3.4.0SDK
>
>
> The generated SHA512 files not verifiable using {{sha512sum --check
> }}. They contain the hash. The expected format is the hash followed
> by the filename.
> It would be nice if {{sha512sum --check }} could be used to check
> the hashes.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (UIMA-6450) Generated SHA512 files not verifiable using sha512sum --check
[
https://issues.apache.org/jira/browse/UIMA-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536505#comment-17536505
]
Richard Eckart de Castilho commented on UIMA-6450:
--
This seems to affect in particular the hash files generated for the primary
source (binary) release artifacts - not the hash files that are attached to the
Maven artifact.
> Generated SHA512 files not verifiable using sha512sum --check
> -
>
> Key: UIMA-6450
> URL: https://issues.apache.org/jira/browse/UIMA-6450
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: parent-pom-15, 3.4.0SDK
>
>
> The generated SHA512 files not verifiable using {{sha512sum --check
> }}. They contain the hash. The expected format is the hash followed
> by the filename.
> It would be nice if {{sha512sum --check }} could be used to check
> the hashes.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (UIMA-6453) Invalid SHA512 generated for Maven artifacts
[
https://issues.apache.org/jira/browse/UIMA-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536504#comment-17536504
]
Richard Eckart de Castilho commented on UIMA-6453:
--
The problem seems to have been introduced when switching from {{parent-pom-13}}
to {{parent-pom-14}}.
> Invalid SHA512 generated for Maven artifacts
>
>
> Key: UIMA-6453
> URL: https://issues.apache.org/jira/browse/UIMA-6453
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test
>Affects Versions: 3.2.0uimaFIT, 3.2.0SDK, 3.1.0ruta, 3.3.0SDK
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.3.0uimaFIT, parent-pom-15, 3.3.1SDK, 3.2.0ruta
>
>
> The SHA512 signature files we generate for the Maven artifacts overwrite each
> other. E.g. in the recent uimaFIT 3.3.0 RC 2, I found:
> {noformat}
> % cat
> org/apache/uima/uimafit-maven-plugin/3.3.0/uimafit-maven-plugin-3.3.0.sha512
> 4db94daceccf1727b1620a20a708eb1830a95fa8ad967219ad7fff537bf845055174f659b43f3bb827cd1296d4608c10b3f36306a76da4dd27af50a45517bb2f
> uimafit-maven-plugin-3.3.0-javadoc.jar
> {noformat}
> Looking at Maven Central, I can see such bad signatures in multiple releases:
> *UIMAJ*
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.1.1/ - looks ok
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.2.0/ - BAD
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.3.0/ - BAD
> (latest version)
>
> *uimaFIT*
> * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.1.0/ - looks
> ok
> * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.2.0/ - BAD
> (latest version)
>
> *RUTA*
> * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.0.1/ - looks ok
> * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.1.0/ - BAD
> (latest version)
> *UIMA-AS*
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-as-core/2.9.0/ - last
> release seems to have been before the SHA512 requirement
> *DUCC*
> * https://repo1.maven.org/maven2/org/apache/uima/uima-ducc-common/3.0.0/ -
> looks ok (latest version)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (UIMA-6453) Invalid SHA512 generated for Maven artifacts
[
https://issues.apache.org/jira/browse/UIMA-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6453:
-
Fix Version/s: 3.3.0uimaFIT
parent-pom-15
3.3.1SDK
3.2.0ruta
> Invalid SHA512 generated for Maven artifacts
>
>
> Key: UIMA-6453
> URL: https://issues.apache.org/jira/browse/UIMA-6453
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test
>Affects Versions: 3.2.0uimaFIT, 3.2.0SDK, 3.1.0ruta, 3.3.0SDK
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.3.0uimaFIT, parent-pom-15, 3.3.1SDK, 3.2.0ruta
>
>
> The SHA512 signature files we generate for the Maven artifacts overwrite each
> other. E.g. in the recent uimaFIT 3.3.0 RC 2, I found:
> {noformat}
> % cat
> org/apache/uima/uimafit-maven-plugin/3.3.0/uimafit-maven-plugin-3.3.0.sha512
> 4db94daceccf1727b1620a20a708eb1830a95fa8ad967219ad7fff537bf845055174f659b43f3bb827cd1296d4608c10b3f36306a76da4dd27af50a45517bb2f
> uimafit-maven-plugin-3.3.0-javadoc.jar
> {noformat}
> Looking at Maven Central, I can see such bad signatures in multiple releases:
> *UIMAJ*
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.1.1/ - looks ok
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.2.0/ - BAD
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.3.0/ - BAD
> (latest version)
>
> *uimaFIT*
> * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.1.0/ - looks
> ok
> * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.2.0/ - BAD
> (latest version)
>
> *RUTA*
> * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.0.1/ - looks ok
> * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.1.0/ - BAD
> (latest version)
> *UIMA-AS*
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-as-core/2.9.0/ - last
> release seems to have been before the SHA512 requirement
> *DUCC*
> * https://repo1.maven.org/maven2/org/apache/uima/uima-ducc-common/3.0.0/ -
> looks ok (latest version)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (UIMA-6453) Invalid SHA512 generated for Maven artifacts
[
https://issues.apache.org/jira/browse/UIMA-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6453:
-
Affects Version/s: 3.2.0uimaFIT
> Invalid SHA512 generated for Maven artifacts
>
>
> Key: UIMA-6453
> URL: https://issues.apache.org/jira/browse/UIMA-6453
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test
>Affects Versions: 3.2.0uimaFIT, 3.2.0SDK, 3.1.0ruta, 3.3.0SDK
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> The SHA512 signature files we generate for the Maven artifacts overwrite each
> other. E.g. in the recent uimaFIT 3.3.0 RC 2, I found:
> {noformat}
> % cat
> org/apache/uima/uimafit-maven-plugin/3.3.0/uimafit-maven-plugin-3.3.0.sha512
> 4db94daceccf1727b1620a20a708eb1830a95fa8ad967219ad7fff537bf845055174f659b43f3bb827cd1296d4608c10b3f36306a76da4dd27af50a45517bb2f
> uimafit-maven-plugin-3.3.0-javadoc.jar
> {noformat}
> Looking at Maven Central, I can see such bad signatures in multiple releases:
> *UIMAJ*
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.1.1/ - looks ok
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.2.0/ - BAD
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.3.0/ - BAD
> (latest version)
>
> *uimaFIT*
> * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.1.0/ - looks
> ok
> * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.2.0/ - BAD
> (latest version)
>
> *RUTA*
> * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.0.1/ - looks ok
> * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.1.0/ - BAD
> (latest version)
> *UIMA-AS*
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-as-core/2.9.0/ - last
> release seems to have been before the SHA512 requirement
> *DUCC*
> * https://repo1.maven.org/maven2/org/apache/uima/uima-ducc-common/3.0.0/ -
> looks ok (latest version)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (UIMA-6453) Invalid SHA512 generated for Maven artifacts
[
https://issues.apache.org/jira/browse/UIMA-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6453:
-
Affects Version/s: 3.3.0SDK
3.1.0ruta
3.2.0SDK
> Invalid SHA512 generated for Maven artifacts
>
>
> Key: UIMA-6453
> URL: https://issues.apache.org/jira/browse/UIMA-6453
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test
>Affects Versions: 3.2.0SDK, 3.1.0ruta, 3.3.0SDK
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> The SHA512 signature files we generate for the Maven artifacts overwrite each
> other. E.g. in the recent uimaFIT 3.3.0 RC 2, I found:
> {noformat}
> % cat
> org/apache/uima/uimafit-maven-plugin/3.3.0/uimafit-maven-plugin-3.3.0.sha512
> 4db94daceccf1727b1620a20a708eb1830a95fa8ad967219ad7fff537bf845055174f659b43f3bb827cd1296d4608c10b3f36306a76da4dd27af50a45517bb2f
> uimafit-maven-plugin-3.3.0-javadoc.jar
> {noformat}
> Looking at Maven Central, I can see such bad signatures in multiple releases:
> *UIMAJ*
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.1.1/ - looks ok
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.2.0/ - BAD
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.3.0/ - BAD
> (latest version)
>
> *uimaFIT*
> * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.1.0/ - looks
> ok
> * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.2.0/ - BAD
> (latest version)
>
> *RUTA*
> * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.0.1/ - looks ok
> * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.1.0/ - BAD
> (latest version)
> *UIMA-AS*
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-as-core/2.9.0/ - last
> release seems to have been before the SHA512 requirement
> *DUCC*
> * https://repo1.maven.org/maven2/org/apache/uima/uima-ducc-common/3.0.0/ -
> looks ok (latest version)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (UIMA-6453) Invalid SHA512 generated for Maven artifacts
[ https://issues.apache.org/jira/browse/UIMA-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6453: - Description: The SHA512 signature files we generate for the Maven artifacts overwrite each other. E.g. in the recent uimaFIT 3.3.0 RC 2, I found: ``` % cat org/apache/uima/uimafit-maven-plugin/3.3.0/uimafit-maven-plugin-3.3.0.sha512 4db94daceccf1727b1620a20a708eb1830a95fa8ad967219ad7fff537bf845055174f659b43f3bb827cd1296d4608c10b3f36306a76da4dd27af50a45517bb2f uimafit-maven-plugin-3.3.0-javadoc.jar ``` Looking at Maven Central, I can see such bad signatures in multiple releases: *UIMAJ* * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.1.1/ - looks ok * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.2.0/ - BAD * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.3.0/ - BAD (latest version) *uimaFIT* * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.1.0/ - looks ok * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.2.0/ - BAD (latest version) *RUTA* * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.0.1/ - looks ok * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.1.0/ - BAD (latest version) *UIMA-AS* * https://repo1.maven.org/maven2/org/apache/uima/uimaj-as-core/2.9.0/ - last release seems to have been before the SHA512 requirement *DUCC* * https://repo1.maven.org/maven2/org/apache/uima/uima-ducc-common/3.0.0/ - looks ok (latest version) was: The SHA512 signature files we generate for the Maven artifacts overwrite each other. E.g. in the recent uimaFIT 3.3.0 RC 2, I found: ``` % cat org/apache/uima/uimafit-maven-plugin/3.3.0/uimafit-maven-plugin-3.3.0.sha512 4db94daceccf1727b1620a20a708eb1830a95fa8ad967219ad7fff537bf845055174f659b43f3bb827cd1296d4608c10b3f36306a76da4dd27af50a45517bb2f uimafit-maven-plugin-3.3.0-javadoc.jar ``` Looking at Maven Central, I can see such bad signatures in multiple releases: *UIMAJ* * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.1.1/ - looks ok * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.2.0/ - BAD * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.3.0/ - BAD (latest version) *uimaFIT* * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.1.0/ - looks ok * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.2.0/ - BAD (latest version) *RUTA* * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.0.1/ - looks ok * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.1.0/ - BAD (latest version *UIMA-AS* * https://repo1.maven.org/maven2/org/apache/uima/uimaj-as-core/2.9.0/ - last release seems to have been before the SHA512 requiremen *DUCC* * https://repo1.maven.org/maven2/org/apache/uima/uima-ducc-common/3.0.0/ - looks ok (latest version) > Invalid SHA512 generated for Maven artifacts > > > Key: UIMA-6453 > URL: https://issues.apache.org/jira/browse/UIMA-6453 > Project: UIMA > Issue Type: Bug > Components: Build, Packaging and Test >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > > The SHA512 signature files we generate for the Maven artifacts overwrite each > other. E.g. in the recent uimaFIT 3.3.0 RC 2, I found: > ``` > % cat > org/apache/uima/uimafit-maven-plugin/3.3.0/uimafit-maven-plugin-3.3.0.sha512 > 4db94daceccf1727b1620a20a708eb1830a95fa8ad967219ad7fff537bf845055174f659b43f3bb827cd1296d4608c10b3f36306a76da4dd27af50a45517bb2f > uimafit-maven-plugin-3.3.0-javadoc.jar > ``` > Looking at Maven Central, I can see such bad signatures in multiple releases: > *UIMAJ* > * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.1.1/ - looks ok > * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.2.0/ - BAD > * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.3.0/ - BAD > (latest version) > > *uimaFIT* > * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.1.0/ - looks > ok > * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.2.0/ - BAD > (latest version) > > *RUTA* > * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.0.1/ - looks ok > * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.1.0/ - BAD > (latest version) > *UIMA-AS* > * https://repo1.maven.org/maven2/org/apache/uima/uimaj-as-core/2.9.0/ - last > release seems to have been before the SHA512 requirement > *DUCC* > * https://repo1.maven.org/maven2/org/apache/uima/uima-ducc-common/3.0.0/ - > looks ok (latest version) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6453) Invalid SHA512 generated for Maven artifacts
[
https://issues.apache.org/jira/browse/UIMA-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6453:
-
Description:
The SHA512 signature files we generate for the Maven artifacts overwrite each
other. E.g. in the recent uimaFIT 3.3.0 RC 2, I found:
{noformat}
% cat
org/apache/uima/uimafit-maven-plugin/3.3.0/uimafit-maven-plugin-3.3.0.sha512
4db94daceccf1727b1620a20a708eb1830a95fa8ad967219ad7fff537bf845055174f659b43f3bb827cd1296d4608c10b3f36306a76da4dd27af50a45517bb2f
uimafit-maven-plugin-3.3.0-javadoc.jar
{noformat}
Looking at Maven Central, I can see such bad signatures in multiple releases:
*UIMAJ*
* https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.1.1/ - looks ok
* https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.2.0/ - BAD
* https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.3.0/ - BAD
(latest version)
*uimaFIT*
* https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.1.0/ - looks ok
* https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.2.0/ - BAD
(latest version)
*RUTA*
* https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.0.1/ - looks ok
* https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.1.0/ - BAD (latest
version)
*UIMA-AS*
* https://repo1.maven.org/maven2/org/apache/uima/uimaj-as-core/2.9.0/ - last
release seems to have been before the SHA512 requirement
*DUCC*
* https://repo1.maven.org/maven2/org/apache/uima/uima-ducc-common/3.0.0/ -
looks ok (latest version)
was:
The SHA512 signature files we generate for the Maven artifacts overwrite each
other. E.g. in the recent uimaFIT 3.3.0 RC 2, I found:
```
% cat
org/apache/uima/uimafit-maven-plugin/3.3.0/uimafit-maven-plugin-3.3.0.sha512
4db94daceccf1727b1620a20a708eb1830a95fa8ad967219ad7fff537bf845055174f659b43f3bb827cd1296d4608c10b3f36306a76da4dd27af50a45517bb2f
uimafit-maven-plugin-3.3.0-javadoc.jar
```
Looking at Maven Central, I can see such bad signatures in multiple releases:
*UIMAJ*
* https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.1.1/ - looks ok
* https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.2.0/ - BAD
* https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.3.0/ - BAD
(latest version)
*uimaFIT*
* https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.1.0/ - looks ok
* https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.2.0/ - BAD
(latest version)
*RUTA*
* https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.0.1/ - looks ok
* https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.1.0/ - BAD (latest
version)
*UIMA-AS*
* https://repo1.maven.org/maven2/org/apache/uima/uimaj-as-core/2.9.0/ - last
release seems to have been before the SHA512 requirement
*DUCC*
* https://repo1.maven.org/maven2/org/apache/uima/uima-ducc-common/3.0.0/ -
looks ok (latest version)
> Invalid SHA512 generated for Maven artifacts
>
>
> Key: UIMA-6453
> URL: https://issues.apache.org/jira/browse/UIMA-6453
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> The SHA512 signature files we generate for the Maven artifacts overwrite each
> other. E.g. in the recent uimaFIT 3.3.0 RC 2, I found:
> {noformat}
> % cat
> org/apache/uima/uimafit-maven-plugin/3.3.0/uimafit-maven-plugin-3.3.0.sha512
> 4db94daceccf1727b1620a20a708eb1830a95fa8ad967219ad7fff537bf845055174f659b43f3bb827cd1296d4608c10b3f36306a76da4dd27af50a45517bb2f
> uimafit-maven-plugin-3.3.0-javadoc.jar
> {noformat}
> Looking at Maven Central, I can see such bad signatures in multiple releases:
> *UIMAJ*
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.1.1/ - looks ok
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.2.0/ - BAD
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.3.0/ - BAD
> (latest version)
>
> *uimaFIT*
> * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.1.0/ - looks
> ok
> * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.2.0/ - BAD
> (latest version)
>
> *RUTA*
> * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.0.1/ - looks ok
> * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.1.0/ - BAD
> (latest version)
> *UIMA-AS*
> * https://repo1.maven.org/maven2/org/apache/uima/uimaj-as-core/2.9.0/ - last
> release seems to have been before the SHA512 requirement
> *DUCC*
> * https://repo1.maven.org/maven2/org/apache/uima/uima-ducc-common/3.0.0/ -
> looks ok (latest version)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (UIMA-6453) Invalid SHA512 generated for Maven artifacts
[ https://issues.apache.org/jira/browse/UIMA-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6453: - Description: The SHA512 signature files we generate for the Maven artifacts overwrite each other. E.g. in the recent uimaFIT 3.3.0 RC 2, I found: ``` % cat org/apache/uima/uimafit-maven-plugin/3.3.0/uimafit-maven-plugin-3.3.0.sha512 4db94daceccf1727b1620a20a708eb1830a95fa8ad967219ad7fff537bf845055174f659b43f3bb827cd1296d4608c10b3f36306a76da4dd27af50a45517bb2f uimafit-maven-plugin-3.3.0-javadoc.jar ``` Looking at Maven Central, I can see such bad signatures in multiple releases: *UIMAJ* * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.1.1/ - looks ok * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.2.0/ - BAD * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.3.0/ - BAD (latest version) *uimaFIT* * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.1.0/ - looks ok * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.2.0/ - BAD (latest version) *RUTA* * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.0.1/ - looks ok * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.1.0/ - BAD (latest version *UIMA-AS* * https://repo1.maven.org/maven2/org/apache/uima/uimaj-as-core/2.9.0/ - last release seems to have been before the SHA512 requiremen *DUCC* * https://repo1.maven.org/maven2/org/apache/uima/uima-ducc-common/3.0.0/ - looks ok (latest version) > Invalid SHA512 generated for Maven artifacts > > > Key: UIMA-6453 > URL: https://issues.apache.org/jira/browse/UIMA-6453 > Project: UIMA > Issue Type: Bug > Components: Build, Packaging and Test >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > > The SHA512 signature files we generate for the Maven artifacts overwrite each > other. E.g. in the recent uimaFIT 3.3.0 RC 2, I found: > ``` > % cat > org/apache/uima/uimafit-maven-plugin/3.3.0/uimafit-maven-plugin-3.3.0.sha512 > 4db94daceccf1727b1620a20a708eb1830a95fa8ad967219ad7fff537bf845055174f659b43f3bb827cd1296d4608c10b3f36306a76da4dd27af50a45517bb2f > uimafit-maven-plugin-3.3.0-javadoc.jar > ``` > Looking at Maven Central, I can see such bad signatures in multiple releases: > *UIMAJ* > * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.1.1/ - looks ok > * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.2.0/ - BAD > * https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/3.3.0/ - BAD > (latest version) > > *uimaFIT* > * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.1.0/ - looks > ok > * https://repo1.maven.org/maven2/org/apache/uima/uimafit-core/3.2.0/ - BAD > (latest version) > > *RUTA* > * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.0.1/ - looks ok > * https://repo1.maven.org/maven2/org/apache/uima/ruta-core/3.1.0/ - BAD > (latest version > *UIMA-AS* > * https://repo1.maven.org/maven2/org/apache/uima/uimaj-as-core/2.9.0/ - last > release seems to have been before the SHA512 requiremen > *DUCC* > * https://repo1.maven.org/maven2/org/apache/uima/uima-ducc-common/3.0.0/ - > looks ok (latest version) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (UIMA-6453) Invalid SHA512 generated for Maven artifacts
Richard Eckart de Castilho created UIMA-6453: Summary: Invalid SHA512 generated for Maven artifacts Key: UIMA-6453 URL: https://issues.apache.org/jira/browse/UIMA-6453 Project: UIMA Issue Type: Bug Components: Build, Packaging and Test Reporter: Richard Eckart de Castilho Assignee: Richard Eckart de Castilho -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6425) uimaFIT 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6425:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (/) 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
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (/) Close the staging repository at {{https://repository.apache.org/}} ->
https://repository.apache.org/content/repositories/orgapacheuima-1273
- (/) 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 ->
https://dist.apache.org/repos/dist/dev/uima/uimafit-3.3.0-rc-2/
*Vote*
- (/) Call for a vote
- (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)
*Publish release*
- (x) Move the release artifacts from the staging spot to the dist spot in SVN:
{{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (x) Create new maintenance branch (when doing feature releases)
- (x) Update the version on the development branch (when doing feature releases)
- (x) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (x) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (x) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (x) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (x) Close release in Jira and GitHub
- (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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (/) 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
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (/) Close the staging repository at {{https://repository.apache.org/}} ->
https://repository.apache.org/content/repositories/orgapacheuima-1273
- (/) 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 ->
https://dist.apache.org/repos/dist/dev/uima/uimafit-3.3.0-rc-2/
*Vote*
- (x) Call for a vote
- (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)
*Publish release*
- (x) Move the release artifacts from the staging spot to the dist spot in SVN:
{{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://repository.apache.org/}}
- (x) Create a new git tag e.g. {{re
[jira] [Updated] (UIMA-6425) uimaFIT 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6425:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (/) 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
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (/) Close the staging repository at {{https://repository.apache.org/}} ->
https://repository.apache.org/content/repositories/orgapacheuima-1273
- (/) 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 ->
https://dist.apache.org/repos/dist/dev/uima/uimafit-3.3.0-rc-2/
*Vote*
- (x) Call for a vote
- (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)
*Publish release*
- (x) Move the release artifacts from the staging spot to the dist spot in SVN:
{{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (x) Create new maintenance branch (when doing feature releases)
- (x) Update the version on the development branch (when doing feature releases)
- (x) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (x) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (x) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (x) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (x) Close release in Jira and GitHub
- (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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (/) 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
*Release build*
- (x) Clean local m2 repository
- (x) Do a test build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (x) Close the staging repository at {{https://repository.apache.org/}} ->
https://repository.apache.org/content/repositories/orgapacheuima-1272
- (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 ->
https://dist.apache.org/repos/dist/dev/uima/uimafit-3.3.0-rc-1/
*Vote*
- (x) Call for a vote
- (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)
*Publish release*
- (x) Move the release artifacts from the staging spot to the dist spot in SVN:
{{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://repository.apache.org/}}
- (x) Create a new git tag e.g. {{re
[jira] [Resolved] (UIMA-6452) Some tests fail cleaning up their temporary data
[
https://issues.apache.org/jira/browse/UIMA-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6452.
--
Resolution: Fixed
> Some tests fail cleaning up their temporary data
>
>
> Key: UIMA-6452
> URL: https://issues.apache.org/jira/browse/UIMA-6452
> Project: UIMA
> Issue Type: Bug
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.3.0uimaFIT
>
>
> These tests for some reason fail cleaning up after themselves - but only on
> Windows:
> {noformat}
> Build / Matrix - PLATFORM = 'Windows' / PR build /
> org.apache.uima.fit.component.CasDumpWriterTest.test{Path}
> Build / Matrix - PLATFORM = 'Windows' / PR build /
> org.apache.uima.fit.factory.JCasBuilderTest.test{Path}
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (UIMA-6425) uimaFIT 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6425:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (/) 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
*Release build*
- (x) Clean local m2 repository
- (x) Do a test build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (x) Close the staging repository at {{https://repository.apache.org/}} ->
https://repository.apache.org/content/repositories/orgapacheuima-1272
- (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 ->
https://dist.apache.org/repos/dist/dev/uima/uimafit-3.3.0-rc-1/
*Vote*
- (x) Call for a vote
- (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)
*Publish release*
- (x) Move the release artifacts from the staging spot to the dist spot in SVN:
{{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (x) Create new maintenance branch (when doing feature releases)
- (x) Update the version on the development branch (when doing feature releases)
- (x) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (x) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (x) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (x) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (x) Close release in Jira and GitHub
- (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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (/) 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
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (/) Close the staging repository at {{https://repository.apache.org/}} ->
https://repository.apache.org/content/repositories/orgapacheuima-1272
- (/) 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 ->
https://dist.apache.org/repos/dist/dev/uima/uimafit-3.3.0-rc-1/
*Vote*
- (/) Call for a vote
- (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)
*Publish release*
- (x) Move the release artifacts from the staging spot to the dist spot in SVN:
{{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://repository.apache.org/}}
- (x) Create a new git tag e.g. {{re
[jira] [Updated] (UIMA-6444) Automatically sign Eclipse plugins during release builds
[ https://issues.apache.org/jira/browse/UIMA-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6444: - Description: *Note:* we do have detached PGP signatures for the Eclipse update site artifacts - it is mandatory according to the ASF release policy - but they are currently not included in such a way that Eclipse can verify them and offer the user to trust them during the plugin installation process. Currently, we do not sign the Eclipse plugins because it is extra effort and the old way of using the Symantec Service are gone anyway. There is a new jarsigning approach which could be used. Alternatively, it is meanwhile possible to embed PGP signatures in P2 repositories. Let's see which of these options are viable for us. was: Currently, we do not sign the Eclipse plugins because it is extra effort and the old way of using the Symantec Service are gone anyway. There is a new jarsigning approach which could be used. Alternatively, it is meanwhile possible to embed PGP signatures in P2 repositories. Let's see which of these options are viable for us. > Automatically sign Eclipse plugins during release builds > > > Key: UIMA-6444 > URL: https://issues.apache.org/jira/browse/UIMA-6444 > Project: UIMA > Issue Type: Improvement >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.4.0SDK > > > *Note:* we do have detached PGP signatures for the Eclipse update site > artifacts - it is mandatory according to the ASF release policy - but they > are currently not included in such a way that Eclipse can verify them and > offer the user to trust them during the plugin installation process. > > Currently, we do not sign the Eclipse plugins because it is extra effort and > the old way of using the Symantec Service are gone anyway. > There is a new jarsigning approach which could be used. > Alternatively, it is meanwhile possible to embed PGP signatures in P2 > repositories. > Let's see which of these options are viable for us. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6335) Optimize release process
[
https://issues.apache.org/jira/browse/UIMA-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6335:
-
Description:
The release checklist is pretty long. To facilitate releases, we should see
what can be optimized / cut.
- (/) {{README.md}} becomes version-independent and contains a proper project
description suitable as a GitHub repo landing page
- (/) {{RELEASE_NOTES.md}} contains only version-specific release notes and can
be largely copy/pasted to the release announcments mail/website/etc.
- (/) [uimaFIT] Drop the binary release package of uimaFIT - the source release
and obtaining the artifacts via Maven Central should be sufficient (UIMA-6448)
- (/) [UIMAJ] Integrate building of Eclipse update sites into the build
(UIMA-6443)
- (x) [RUTA] Integrate building of Eclipse update sites into the build
- (x) [UIMAJ] Put the examples in the UIMA Java SDK into a form where they are
convenient to use form the source distribution or find some other way of
providing them which does not require binary release package. In particular,
they should not be Eclipse projects but rather regular Maven projects
- (x) [UIMAJ] Drop the binary release package of UIMA Java SDK - the source
release and obtaining the artifacts via Maven Central should be sufficient -
will safe us from having to maintain the LICENSE/NOTICE files for binary
releases
was:
The release checklist is pretty long. To facilitate releases, we should see
what can be optimized / cut.
- (/) {{README.md}} becomes version-independent and contains a proper project
description suitable as a GitHub repo landing page
- (/) {{RELEASE_NOTES.md}} contains only version-specific release notes and can
be largely copy/pasted to the release announcments mail/website/etc.
- (/) Drop the binary release package of uimaFIT - the source release and
obtaining the artifacts via Maven Central should be sufficient (UIMA-6448)
- Drop (most) binary ZIP releases and only offer source, Maven and for the Java
SDK / Ruta the Eclipse update site:
-- Rationale: The binary ZIPs use separate LICENSE/NOTICE files which need to
be checked/maintained - and this cannot be easily done automatically
> Optimize release process
>
>
> Key: UIMA-6335
> URL: https://issues.apache.org/jira/browse/UIMA-6335
> Project: UIMA
> Issue Type: Improvement
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> The release checklist is pretty long. To facilitate releases, we should see
> what can be optimized / cut.
> - (/) {{README.md}} becomes version-independent and contains a proper project
> description suitable as a GitHub repo landing page
> - (/) {{RELEASE_NOTES.md}} contains only version-specific release notes and
> can be largely copy/pasted to the release announcments mail/website/etc.
> - (/) [uimaFIT] Drop the binary release package of uimaFIT - the source
> release and obtaining the artifacts via Maven Central should be sufficient
> (UIMA-6448)
> - (/) [UIMAJ] Integrate building of Eclipse update sites into the build
> (UIMA-6443)
> - (x) [RUTA] Integrate building of Eclipse update sites into the build
> - (x) [UIMAJ] Put the examples in the UIMA Java SDK into a form where they
> are convenient to use form the source distribution or find some other way of
> providing them which does not require binary release package. In particular,
> they should not be Eclipse projects but rather regular Maven projects
> - (x) [UIMAJ] Drop the binary release package of UIMA Java SDK - the source
> release and obtaining the artifacts via Maven Central should be sufficient -
> will safe us from having to maintain the LICENSE/NOTICE files for binary
> releases
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (UIMA-6335) Optimize release process
[
https://issues.apache.org/jira/browse/UIMA-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6335:
-
Description:
The release checklist is pretty long. To facilitate releases, we should see
what can be optimized / cut.
- (/) {{README.md}} becomes version-independent and contains a proper project
description suitable as a GitHub repo landing page
- (/) {{RELEASE_NOTES.md}} contains only version-specific release notes and can
be largely copy/pasted to the release announcments mail/website/etc.
- (/) Drop the binary release package of uimaFIT - the source release and
obtaining the artifacts via Maven Central should be sufficient (UIMA-6448)
- Drop (most) binary ZIP releases and only offer source, Maven and for the Java
SDK / Ruta the Eclipse update site:
-- Rationale: The binary ZIPs use separate LICENSE/NOTICE files which need to
be checked/maintained - and this cannot be easily done automatically
was:
The release checklist is pretty long. To facilitate releases, we should see
what can be optimized / cut.
- (/) {{README.md}} becomes version-independent and contains a proper project
description suitable as a GitHub repo landing page
- (/) {{RELEASE_NOTES.md}} contains only version-specific release notes and can
be largely copy/pasted to the release announcments mail/website/etc.
- (/) Drop the binary release package of uimaFIT - the source release and
obtaining the artifacts via Maven Central should be sufficient
- Drop (most) binary ZIP releases and only offer source, Maven and for the Java
SDK / Ruta the Eclipse update site:
-- Rationale: The binary ZIPs use separate LICENSE/NOTICE files which need to
be checked/maintained - and this cannot be easily done automatically
> Optimize release process
>
>
> Key: UIMA-6335
> URL: https://issues.apache.org/jira/browse/UIMA-6335
> Project: UIMA
> Issue Type: Improvement
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> The release checklist is pretty long. To facilitate releases, we should see
> what can be optimized / cut.
> - (/) {{README.md}} becomes version-independent and contains a proper project
> description suitable as a GitHub repo landing page
> - (/) {{RELEASE_NOTES.md}} contains only version-specific release notes and
> can be largely copy/pasted to the release announcments mail/website/etc.
> - (/) Drop the binary release package of uimaFIT - the source release and
> obtaining the artifacts via Maven Central should be sufficient (UIMA-6448)
>
> - Drop (most) binary ZIP releases and only offer source, Maven and for the
> Java SDK / Ruta the Eclipse update site:
> -- Rationale: The binary ZIPs use separate LICENSE/NOTICE files which need to
> be checked/maintained - and this cannot be easily done automatically
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (UIMA-6335) Optimize release process
[
https://issues.apache.org/jira/browse/UIMA-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6335:
-
Description:
The release checklist is pretty long. To facilitate releases, we should see
what can be optimized / cut.
- (/) {{README.md}} becomes version-independent and contains a proper project
description suitable as a GitHub repo landing page
- (/) {{RELEASE_NOTES.md}} contains only version-specific release notes and can
be largely copy/pasted to the release announcments mail/website/etc.
- (/) Drop the binary release package of uimaFIT - the source release and
obtaining the artifacts via Maven Central should be sufficient
- Drop (most) binary ZIP releases and only offer source, Maven and for the Java
SDK / Ruta the Eclipse update site:
-- Rationale: The binary ZIPs use separate LICENSE/NOTICE files which need to
be checked/maintained - and this cannot be easily done automatically
was:
The release checklist is pretty long. To facilitate releases, we should see
what can be optimized / cut.
- (/) {{README.md}} becomes version-independent and contains a proper project
description suitable as a GitHub repo landing page
- (/) {{RELEASE_NOTES.md}} contains only version-specific release notes and can
be largely copy/pasted to the release announcments mail/website/etc.
- Drop (most) binary ZIP releases and only offer source, Maven and for the Java
SDK / Ruta the Eclipse update site:
-- Rationale: The binary ZIPs use separate LICENSE/NOTICE files which need to
be checked/maintained - and this cannot be easily done automatically
> Optimize release process
>
>
> Key: UIMA-6335
> URL: https://issues.apache.org/jira/browse/UIMA-6335
> Project: UIMA
> Issue Type: Improvement
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> The release checklist is pretty long. To facilitate releases, we should see
> what can be optimized / cut.
> - (/) {{README.md}} becomes version-independent and contains a proper project
> description suitable as a GitHub repo landing page
> - (/) {{RELEASE_NOTES.md}} contains only version-specific release notes and
> can be largely copy/pasted to the release announcments mail/website/etc.
> - (/) Drop the binary release package of uimaFIT - the source release and
> obtaining the artifacts via Maven Central should be sufficient
>
> - Drop (most) binary ZIP releases and only offer source, Maven and for the
> Java SDK / Ruta the Eclipse update site:
> -- Rationale: The binary ZIPs use separate LICENSE/NOTICE files which need to
> be checked/maintained - and this cannot be easily done automatically
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Work started] (UIMA-6452) Some tests fail cleaning up their temporary data
[
https://issues.apache.org/jira/browse/UIMA-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-6452 started by Richard Eckart de Castilho.
> Some tests fail cleaning up their temporary data
>
>
> Key: UIMA-6452
> URL: https://issues.apache.org/jira/browse/UIMA-6452
> Project: UIMA
> Issue Type: Bug
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.3.0uimaFIT
>
>
> These tests for some reason fail cleaning up after themselves - but only on
> Windows:
> {noformat}
> Build / Matrix - PLATFORM = 'Windows' / PR build /
> org.apache.uima.fit.component.CasDumpWriterTest.test{Path}
> Build / Matrix - PLATFORM = 'Windows' / PR build /
> org.apache.uima.fit.factory.JCasBuilderTest.test{Path}
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (UIMA-6452) Some tests fail cleaning up their temporary data
Richard Eckart de Castilho created UIMA-6452:
Summary: Some tests fail cleaning up their temporary data
Key: UIMA-6452
URL: https://issues.apache.org/jira/browse/UIMA-6452
Project: UIMA
Issue Type: Bug
Components: uimaFIT
Reporter: Richard Eckart de Castilho
Assignee: Richard Eckart de Castilho
Fix For: 3.3.0uimaFIT
These tests for some reason fail cleaning up after themselves - but only on
Windows:
{noformat}
Build / Matrix - PLATFORM = 'Windows' / PR build /
org.apache.uima.fit.component.CasDumpWriterTest.test{Path}
Build / Matrix - PLATFORM = 'Windows' / PR build /
org.apache.uima.fit.factory.JCasBuilderTest.test{Path}
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (UIMA-6451) Jenkins builds should run against multiple platforms
[ https://issues.apache.org/jira/browse/UIMA-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6451. -- Resolution: Fixed > Jenkins builds should run against multiple platforms > > > Key: UIMA-6451 > URL: https://issues.apache.org/jira/browse/UIMA-6451 > Project: UIMA > Issue Type: Improvement > Components: Build, Packaging and Test >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > > Currently, the jenkins builds run on whatever build node is available - > usually a linux one. However, during releases, we often note that a build on > Windows fails. That is inconvient. It would be better if builds would > regularly run also against Windows. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (UIMA-6451) Jenkins builds should run against multiple platforms
Richard Eckart de Castilho created UIMA-6451: Summary: Jenkins builds should run against multiple platforms Key: UIMA-6451 URL: https://issues.apache.org/jira/browse/UIMA-6451 Project: UIMA Issue Type: Improvement Components: Build, Packaging and Test Reporter: Richard Eckart de Castilho Assignee: Richard Eckart de Castilho Currently, the jenkins builds run on whatever build node is available - usually a linux one. However, during releases, we often note that a build on Windows fails. That is inconvient. It would be better if builds would regularly run also against Windows. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6425) uimaFIT 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6425:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (/) 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
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (/) Close the staging repository at {{https://repository.apache.org/}} ->
https://repository.apache.org/content/repositories/orgapacheuima-1272
- (/) 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 ->
https://dist.apache.org/repos/dist/dev/uima/uimafit-3.3.0-rc-1/
*Vote*
- (/) Call for a vote
- (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)
*Publish release*
- (x) Move the release artifacts from the staging spot to the dist spot in SVN:
{{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (x) Create new maintenance branch (when doing feature releases)
- (x) Update the version on the development branch (when doing feature releases)
- (x) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (x) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (x) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (x) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (x) Close release in Jira and GitHub
- (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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (/) 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
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (/) Close the staging repository at {{https://repository.apache.org/}} ->
https://repository.apache.org/content/repositories/orgapacheuima-1272
- (/) 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 ->
https://dist.apache.org/repos/dist/dev/uima/uimafit-3.3.0-rc-1/
*Vote*
- (x) Call for a vote
- (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)
*Publish release*
- (x) Move the release artifacts from the staging spot to the dist spot in SVN:
{{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://repository.apache.org/}}
- (x) Create a new git tag e.g. {{re
[jira] [Updated] (UIMA-6425) uimaFIT 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6425:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (/) 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
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (/) Close the staging repository at {{https://repository.apache.org/}} ->
https://repository.apache.org/content/repositories/orgapacheuima-1272
- (/) 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 ->
https://dist.apache.org/repos/dist/dev/uima/uimafit-3.3.0-rc-1/
*Vote*
- (x) Call for a vote
- (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)
*Publish release*
- (x) Move the release artifacts from the staging spot to the dist spot in SVN:
{{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (x) Create new maintenance branch (when doing feature releases)
- (x) Update the version on the development branch (when doing feature releases)
- (x) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (x) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (x) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (x) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (x) Close release in Jira and GitHub
- (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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (/) 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
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (/) Close the staging repository at {{https://repository.apache.org/}} ->
https://repository.apache.org/content/repositories/orgapacheuima-1272
- (/) 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 ->
https://dist.apache.org/repos/dist/dev/uima/uimafit-3.3.0-rc-1/
*Vote*
- (x) Call for a vote including URLs for
- (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)
*Publish release*
- (x) Move the release artifacts from the staging spot to the dist spot in SVN:
{{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://repository.apache.org/}}
- (x) Create a ne
[jira] [Updated] (UIMA-6425) uimaFIT 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6425:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (/) 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
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (/) Close the staging repository at {{https://repository.apache.org/}} ->
https://repository.apache.org/content/repositories/orgapacheuima-1272
- (/) 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 ->
https://dist.apache.org/repos/dist/dev/uima/uimafit-3.3.0-rc-1/
*Vote*
- (x) Call for a vote including URLs for
- (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)
*Publish release*
- (x) Move the release artifacts from the staging spot to the dist spot in SVN:
{{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (x) Create new maintenance branch (when doing feature releases)
- (x) Update the version on the development branch (when doing feature releases)
- (x) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (x) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (x) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (x) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (x) Close release in Jira and GitHub
- (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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (/) 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
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (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) 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!)
*Vote*
- (x) Call for a vote including URLs for
- (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)
*Publish release*
- (x) Move the release artifacts from the staging spot to the dist spot in SVN:
{{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://repositor
[jira] [Created] (UIMA-6450) Generated SHA512 files not verifiable using sha512sum --check
Richard Eckart de Castilho created UIMA-6450:
Summary: Generated SHA512 files not verifiable using sha512sum
--check
Key: UIMA-6450
URL: https://issues.apache.org/jira/browse/UIMA-6450
Project: UIMA
Issue Type: Improvement
Components: Build, Packaging and Test
Reporter: Richard Eckart de Castilho
Assignee: Richard Eckart de Castilho
Fix For: parent-pom-15, 3.4.0SDK
The generated SHA512 files not verifiable using {{sha512sum --check
}}. They contain the hash. The expected format is the hash followed
by the filename.
It would be nice if {{sha512sum --check }} could be used to check the
hashes.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (UIMA-6425) uimaFIT 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6425:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (/) 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
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (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) 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!)
*Vote*
- (x) Call for a vote including URLs for
- (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)
*Publish release*
- (x) Move the release artifacts from the staging spot to the dist spot in SVN:
{{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (x) Create new maintenance branch (when doing feature releases)
- (x) Update the version on the development branch (when doing feature releases)
- (x) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (x) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (x) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (x) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (x) Close release in Jira and GitHub
- (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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (/) 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
*Release build*
- (x) Clean local m2 repository
- (x) Do a test build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (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) 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!)
*Vote*
- (x) Call for a vote including URLs for
- (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)
*Publish release*
- (x) Move the release artifacts from the staging spot to the dist spot in SVN:
{{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository a
[jira] [Updated] (UIMA-6447) Update dependencies (Ruta 3.2.0)
[
https://issues.apache.org/jira/browse/UIMA-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6447:
-
Description:
* (/) Apache UIMA Java SDK 3.20 -> 3.3.0
* (x) Apache UIMA uimaFIT 3.2.0 -> 3.3.0
* (/) ANTLR 3.5.2 -> 3.5.3
* (/) Caffeine 2.8.3 -> 2.9.3 (3.x requires Java 11)
* (/) Commons Collections 3.2.2 -> 4.4 (remove usages of Commons Collections 3
in the Ruta Code)
* (/) JUnit 4.12 -> 4.13.2
* (/) Spring 4.3.30 -> 5.3.19
* (/) SLF4J 1.7.24 -> 1.7.36
Ruta has no binary tarball release in which we would have to update
LICENSE/NOTICE files. However, it has the {{ruta-ep-engine}} module which
bundles third-party JARs also used by the other Ruta bundles. It is the only
bundle that declares {{Embed-Dependency}}. So when updating dependencies, we
need to check the files in {{ruta-ep-engine/src/main/readme_bin}} are
up-to-date.
* (-) Apache UIMA Java SDK - not bundled
* (x) Apache UIMA uimaFIT
* (x) ANTLR
* (x) Caffeine
* (x) Commons Collections 4
* (-) JUnit - not bundled
* (x) Spring
* (x) SLF4J
was:
* (/) Apache UIMA Java SDK -> 3.3.0
* (/) Spring 4.3.30 -> 5.3.19
* (/) JUnit 4.12 -> 4.13.2
* (/) SLF4J 1.7.24 -> 1.7.36
* (/) ANTLR 3.5.2 -> 3.5.3
* (/) Caffeine 2.8.3 -> 2.9.3 (3.x requires Java 11)
* (/) Commons Collections 3.2.2 -> 4.4 (remove usages of Commons Collections 3
in the Ruta Code)
Ruta has no binary tarball release in which we would have to update
LICENSE/NOTICE files. However, it has the {{ruta-ep-engine}} module which
bundles third-party JARs also used by the other Ruta bundles. It is the only
bundle that declares {{Embed-Dependency}}. So when updating dependencies, we
need to check the files in {{ruta-ep-engine/src/main/readme_bin}} are
up-to-date.
> Update dependencies (Ruta 3.2.0)
>
>
> Key: UIMA-6447
> URL: https://issues.apache.org/jira/browse/UIMA-6447
> Project: UIMA
> Issue Type: Improvement
> Components: Ruta
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.2.0ruta
>
>
> * (/) Apache UIMA Java SDK 3.20 -> 3.3.0
> * (x) Apache UIMA uimaFIT 3.2.0 -> 3.3.0
> * (/) ANTLR 3.5.2 -> 3.5.3
> * (/) Caffeine 2.8.3 -> 2.9.3 (3.x requires Java 11)
> * (/) Commons Collections 3.2.2 -> 4.4 (remove usages of Commons Collections
> 3 in the Ruta Code)
> * (/) JUnit 4.12 -> 4.13.2
> * (/) Spring 4.3.30 -> 5.3.19
> * (/) SLF4J 1.7.24 -> 1.7.36
> Ruta has no binary tarball release in which we would have to update
> LICENSE/NOTICE files. However, it has the {{ruta-ep-engine}} module which
> bundles third-party JARs also used by the other Ruta bundles. It is the only
> bundle that declares {{Embed-Dependency}}. So when updating dependencies, we
> need to check the files in {{ruta-ep-engine/src/main/readme_bin}} are
> up-to-date.
> * (-) Apache UIMA Java SDK - not bundled
> * (x) Apache UIMA uimaFIT
> * (x) ANTLR
> * (x) Caffeine
> * (x) Commons Collections 4
> * (-) JUnit - not bundled
> * (x) Spring
> * (x) SLF4J
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (UIMA-6447) Update dependencies (Ruta 3.2.0)
[
https://issues.apache.org/jira/browse/UIMA-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6447:
-
Description:
* (/) Apache UIMA Java SDK -> 3.3.0
* (/) Spring 4.3.30 -> 5.3.19
* (/) JUnit 4.12 -> 4.13.2
* (/) SLF4J 1.7.24 -> 1.7.36
* (/) ANTLR 3.5.2 -> 3.5.3
* (/) Caffeine 2.8.3 -> 2.9.3 (3.x requires Java 11)
* (/) Commons Collections 3.2.2 -> 4.4 (remove usages of Commons Collections 3
in the Ruta Code)
Ruta has no binary tarball release in which we would have to update
LICENSE/NOTICE files. However, it has the {{ruta-ep-engine}} module which
bundles third-party JARs also used by the other Ruta bundles. It is the only
bundle that declares {{Embed-Dependency}}. So when updating dependencies, we
need to check the files in {{ruta-ep-engine/src/main/readme_bin}} are
up-to-date.
was:
* (/) Apache UIMA Java SDK -> 3.3.0
* (/) Spring 4.3.30 -> 5.3.19
* (/) JUnit 4.12 -> 4.13.2
* (/) SLF4J 1.7.24 -> 1.7.36
* (/) ANTLR 3.5.2 -> 3.5.3
* (/) Caffeine 2.8.3 -> 2.9.3 (3.x requires Java 11)
* (/) Commons Collections 3.2.2 -> 4.4 (remove usages of Commons Collections 3
in the Ruta Code)
> Update dependencies (Ruta 3.2.0)
>
>
> Key: UIMA-6447
> URL: https://issues.apache.org/jira/browse/UIMA-6447
> Project: UIMA
> Issue Type: Improvement
> Components: Ruta
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.2.0ruta
>
>
> * (/) Apache UIMA Java SDK -> 3.3.0
> * (/) Spring 4.3.30 -> 5.3.19
> * (/) JUnit 4.12 -> 4.13.2
> * (/) SLF4J 1.7.24 -> 1.7.36
> * (/) ANTLR 3.5.2 -> 3.5.3
> * (/) Caffeine 2.8.3 -> 2.9.3 (3.x requires Java 11)
> * (/) Commons Collections 3.2.2 -> 4.4 (remove usages of Commons Collections
> 3 in the Ruta Code)
> Ruta has no binary tarball release in which we would have to update
> LICENSE/NOTICE files. However, it has the {{ruta-ep-engine}} module which
> bundles third-party JARs also used by the other Ruta bundles. It is the only
> bundle that declares {{Embed-Dependency}}. So when updating dependencies, we
> need to check the files in {{ruta-ep-engine/src/main/readme_bin}} are
> up-to-date.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (UIMA-6449) Ruta 3.2.0 release
[
https://issues.apache.org/jira/browse/UIMA-6449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6449:
-
Description: Ruta has no binary tarball release in which we would have to
update LICENSE/NOTICE files. However, it has the {{ruta-ep-engine}} module
which bundles third-party JARs also used by the other Ruta bundles. It is the
only bundle that declares {{Embed-Dependency}}. So when updating dependencies,
we need to check the files in {{ruta-ep-engine/src/main/readme_bin}} are
up-to-date.
> Ruta 3.2.0 release
> --
>
> Key: UIMA-6449
> URL: https://issues.apache.org/jira/browse/UIMA-6449
> Project: UIMA
> Issue Type: Task
> Components: Ruta
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> Ruta has no binary tarball release in which we would have to update
> LICENSE/NOTICE files. However, it has the {{ruta-ep-engine}} module which
> bundles third-party JARs also used by the other Ruta bundles. It is the only
> bundle that declares {{Embed-Dependency}}. So when updating dependencies, we
> need to check the files in {{ruta-ep-engine/src/main/readme_bin}} are
> up-to-date.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Work started] (UIMA-6449) Ruta 3.2.0 release
[ https://issues.apache.org/jira/browse/UIMA-6449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-6449 started by Richard Eckart de Castilho. > Ruta 3.2.0 release > -- > > Key: UIMA-6449 > URL: https://issues.apache.org/jira/browse/UIMA-6449 > Project: UIMA > Issue Type: Task > Components: Ruta >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (UIMA-6449) Ruta 3.2.0 release
Richard Eckart de Castilho created UIMA-6449: Summary: Ruta 3.2.0 release Key: UIMA-6449 URL: https://issues.apache.org/jira/browse/UIMA-6449 Project: UIMA Issue Type: Task Components: Ruta Reporter: Richard Eckart de Castilho Assignee: Richard Eckart de Castilho -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Reopened] (UIMA-6447) Update dependencies (Ruta 3.2.0)
[ https://issues.apache.org/jira/browse/UIMA-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho reopened UIMA-6447: -- Also need to update the archetypes... > Update dependencies (Ruta 3.2.0) > > > Key: UIMA-6447 > URL: https://issues.apache.org/jira/browse/UIMA-6447 > Project: UIMA > Issue Type: Improvement > Components: Ruta >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.2.0ruta > > > * (/) Apache UIMA Java SDK -> 3.3.0 > * (/) Spring 4.3.30 -> 5.3.19 > * (/) JUnit 4.12 -> 4.13.2 > * (/) SLF4J 1.7.24 -> 1.7.36 > * (/) ANTLR 3.5.2 -> 3.5.3 > * (/) Caffeine 2.8.3 -> 2.9.3 (3.x requires Java 11) > * (/) Commons Collections 3.2.2 -> 4.4 (remove usages of Commons Collections > 3 in the Ruta Code) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6447) Update dependencies (Ruta 3.2.0)
[ https://issues.apache.org/jira/browse/UIMA-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6447: - Description: * (/) Apache UIMA Java SDK -> 3.3.0 * (/) Spring 4.3.30 -> 5.3.19 * (/) JUnit 4.12 -> 4.13.2 * (/) SLF4J 1.7.24 -> 1.7.36 * (/) ANTLR 3.5.2 -> 3.5.3 * (/) Caffeine 2.8.3 -> 2.9.3 (3.x requires Java 11) * (/) Commons Collections 3.2.2 -> 4.4 (remove usages of Commons Collections 3 in the Ruta Code) was: * (/) Apache UIMA Java SDK -> 3.3.0 * (/) Spring 4.3.30 -> 5.3.19 * (/) JUnit 4.12 -> 4.13.2 * (/) SLF4J 1.7.24 -> 1.7.36 * (/) ANTLR 3.5.2 -> 3.5.3 * (/) Caffeine 2.8.3 -> 2.9.3 (3.x requires Java 11) Upgrade to commons-collections4? > Update dependencies (Ruta 3.2.0) > > > Key: UIMA-6447 > URL: https://issues.apache.org/jira/browse/UIMA-6447 > Project: UIMA > Issue Type: Improvement > Components: Ruta >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.2.0ruta > > > * (/) Apache UIMA Java SDK -> 3.3.0 > * (/) Spring 4.3.30 -> 5.3.19 > * (/) JUnit 4.12 -> 4.13.2 > * (/) SLF4J 1.7.24 -> 1.7.36 > * (/) ANTLR 3.5.2 -> 3.5.3 > * (/) Caffeine 2.8.3 -> 2.9.3 (3.x requires Java 11) > * (/) Commons Collections 3.2.2 -> 4.4 (remove usages of Commons Collections > 3 in the Ruta Code) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (UIMA-6447) Update dependencies (Ruta 3.2.0)
[ https://issues.apache.org/jira/browse/UIMA-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6447. -- Resolution: Fixed > Update dependencies (Ruta 3.2.0) > > > Key: UIMA-6447 > URL: https://issues.apache.org/jira/browse/UIMA-6447 > Project: UIMA > Issue Type: Improvement > Components: Ruta >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.2.0ruta > > > * (/) Apache UIMA Java SDK -> 3.3.0 > * (/) Spring 4.3.30 -> 5.3.19 > * (/) JUnit 4.12 -> 4.13.2 > * (/) SLF4J 1.7.24 -> 1.7.36 > * (/) ANTLR 3.5.2 -> 3.5.3 > * (/) Caffeine 2.8.3 -> 2.9.3 (3.x requires Java 11) > * (/) Commons Collections 3.2.2 -> 4.4 (remove usages of Commons Collections > 3 in the Ruta Code) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (UIMA-6429) uima-uimaj uses axis 1 (end of life with open security issues)
[ https://issues.apache.org/jira/browse/UIMA-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17535122#comment-17535122 ] PJ Fanning commented on UIMA-6429: -- thanks [~rec] > uima-uimaj uses axis 1 (end of life with open security issues) > -- > > Key: UIMA-6429 > URL: https://issues.apache.org/jira/browse/UIMA-6429 > Project: UIMA > Issue Type: Improvement > Components: Transport Adapters - SOAP, Vinci >Reporter: PJ Fanning >Assignee: Richard Eckart de Castilho >Priority: Major > > [https://github.com/apache/uima-uimaj/blob/main/uimaj-adapter-soap/pom.xml] > > eg https://github.com/advisories/GHSA-55w9-c3g2-4rrh -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (UIMA-6432) Upgrade dependencies (uimaFIT 3.3.0)
[ https://issues.apache.org/jira/browse/UIMA-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6432. -- Resolution: Fixed > Upgrade dependencies (uimaFIT 3.3.0) > > > Key: UIMA-6432 > URL: https://issues.apache.org/jira/browse/UIMA-6432 > Project: UIMA > Issue Type: Improvement > Components: uimaFIT >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.3.0uimaFIT > > > Upgrade dependencies. > - Apache UIMA Java SDK 3.2.0 -> 3.3.0 > - Spring 4.3.30 -> 5.3.19 > - Commons IO 2.8.0 -> 2.11.0 > - Mockito 3.2.4 -> 4.4.0 (test) > - japicmp-maven-plugin 0.15.3 -> 0.15.7 (build) > - groovy-jsr223 2.5.14 -> 2.5.16 (build) > - groovy-all 3.0.7 -> 3.0.17 (build) > - maven-gpg-plugin 1.6 -> 3.0.1 (build) > - doxia-core 1.7 -> 1.11.1 (build) > - maven-compiler-plugin 3.8.1 -> 3.10.1 (build) > - maven-javadoc-plugin 3.1.0 -> 3.3.2 (build) > - maven-enforcer-plugin 3.0.0-M3 -> 3.0.0 (build) > - groovy-jsr223 2.5.14 -> 3.0.10 (build) > - groovy-all 3.0.7 -> 3.0.10 (build) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6432) Upgrade dependencies (uimaFIT 3.3.0)
[ https://issues.apache.org/jira/browse/UIMA-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6432: - Description: Upgrade dependencies. - Apache UIMA Java SDK 3.2.0 -> 3.3.0 - Spring 4.3.30 -> 5.3.19 - Commons IO 2.8.0 -> 2.11.0 - Mockito 3.2.4 -> 4.4.0 (test) - japicmp-maven-plugin 0.15.3 -> 0.15.7 (build) - groovy-jsr223 2.5.14 -> 2.5.16 (build) - groovy-all 3.0.7 -> 3.0.17 (build) - maven-gpg-plugin 1.6 -> 3.0.1 (build) - doxia-core 1.7 -> 1.11.1 (build) - maven-compiler-plugin 3.8.1 -> 3.10.1 (build) - maven-javadoc-plugin 3.1.0 -> 3.3.2 (build) - maven-enforcer-plugin 3.0.0-M3 -> 3.0.0 (build) - groovy-jsr223 2.5.14 -> 3.0.10 (build) - groovy-all 3.0.7 -> 3.0.10 (build) was: Upgrade dependencies. - Spring 4.3.30 -> 5.3.18 - Commons IO 2.8.0 -> 2.11.0 - Mockito 3.2.4 -> 4.4.0 (test) - japicmp-maven-plugin 0.15.3 -> 0.15.7 (build) - groovy-jsr223 2.5.14 -> 2.5.16 (build) - groovy-all 3.0.7 -> 3.0.17 (build) - maven-gpg-plugin 1.6 -> 3.0.1 (build) - doxia-core 1.7 -> 1.11.1 (build) - maven-compiler-plugin 3.8.1 -> 3.10.1 (build) - maven-javadoc-plugin 3.1.0 -> 3.3.2 (build) - maven-enforcer-plugin 3.0.0-M3 -> 3.0.0 (build) - groovy-jsr223 2.5.14 -> 3.0.10 (build) - groovy-all 3.0.7 -> 3.0.10 (build) > Upgrade dependencies (uimaFIT 3.3.0) > ---- > > Key: UIMA-6432 > URL: https://issues.apache.org/jira/browse/UIMA-6432 > Project: UIMA > Issue Type: Improvement > Components: uimaFIT >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.3.0uimaFIT > > > Upgrade dependencies. > - Apache UIMA Java SDK 3.2.0 -> 3.3.0 > - Spring 4.3.30 -> 5.3.19 > - Commons IO 2.8.0 -> 2.11.0 > - Mockito 3.2.4 -> 4.4.0 (test) > - japicmp-maven-plugin 0.15.3 -> 0.15.7 (build) > - groovy-jsr223 2.5.14 -> 2.5.16 (build) > - groovy-all 3.0.7 -> 3.0.17 (build) > - maven-gpg-plugin 1.6 -> 3.0.1 (build) > - doxia-core 1.7 -> 1.11.1 (build) > - maven-compiler-plugin 3.8.1 -> 3.10.1 (build) > - maven-javadoc-plugin 3.1.0 -> 3.3.2 (build) > - maven-enforcer-plugin 3.0.0-M3 -> 3.0.0 (build) > - groovy-jsr223 2.5.14 -> 3.0.10 (build) > - groovy-all 3.0.7 -> 3.0.10 (build) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (UIMA-6448) Remove binary release ZIP build from uimaFIT
[ https://issues.apache.org/jira/browse/UIMA-6448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6448. -- Resolution: Fixed > Remove binary release ZIP build from uimaFIT > > > Key: UIMA-6448 > URL: https://issues.apache.org/jira/browse/UIMA-6448 > Project: UIMA > Issue Type: Task > Components: uimaFIT >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.3.0uimaFIT > > > uimaFIT is basically exclusively used via the Maven dependency mechanism. > Having an additional binary ZIP/TGZ convenience artifact is adding more > effort to the release and reviewing process than it actually benefits > downstream users. > Remove the ZIP/TGZ assembly from the uimaFIT build. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6425) uimaFIT 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6425:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (/) 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
*Release build*
- (x) Clean local m2 repository
- (x) Do a test build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (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) 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!)
*Vote*
- (x) Call for a vote including URLs for
- (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)
*Publish release*
- (x) Move the release artifacts from the staging spot to the dist spot in SVN:
{{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (x) Create new maintenance branch (when doing feature releases)
- (x) Update the version on the development branch (when doing feature releases)
- (x) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (x) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (x) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (x) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (x) Close release in Jira and GitHub
- (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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (x) Check the LICENSE and NOTICE files for the binary release
- (x) 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) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (x) Clean local m2 repository
- (x) Do a test build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (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) 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!)
*Vote*
- (x) Call for a vote including URLs for
- (x) VOTE (wait at least fo
[jira] [Updated] (UIMA-6425) uimaFIT 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6425:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (x) Check the LICENSE and NOTICE files for the binary release
- (x) 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) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (x) Clean local m2 repository
- (x) Do a test build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (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) 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!)
*Vote*
- (x) Call for a vote including URLs for
- (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)
*Publish release*
- (x) Copy existing Eclipse update site to the archive spot: {{svn copy -m
"create eclipse plugin archive for uimaj-3.0.0-3.2.0"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0}}
- (x) Remove old Eclipse update site: {{svn rm -m "Removing previous UIMAJ
update site to make space for new one"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (x) Move new Eclipse update site from the staging to the release spot: {{svn
mv -m "Installing UIMAJ 3.3.0 update site from accepted RC3"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (x) Move the other release artifacts from the staging spot to the dist spot
in SVN: {{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (x) Create new maintenance branch (when doing feature releases)
- (x) Update the version on the development branch (when doing feature releases)
- (x) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (x) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (x) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (x) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (x) Close release in Jira and GitHub
- (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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (x) Check the LICENSE and NOTICE files for the binary release
- (x) Make sure to remove all SNAPSHOT repositories and SNAPSH
[jira] [Created] (UIMA-6448) Remove binary release ZIP build from uimaFIT
Richard Eckart de Castilho created UIMA-6448: Summary: Remove binary release ZIP build from uimaFIT Key: UIMA-6448 URL: https://issues.apache.org/jira/browse/UIMA-6448 Project: UIMA Issue Type: Task Components: uimaFIT Reporter: Richard Eckart de Castilho Assignee: Richard Eckart de Castilho Fix For: 3.3.0uimaFIT uimaFIT is basically exclusively used via the Maven dependency mechanism. Having an additional binary ZIP/TGZ convenience artifact is adding more effort to the release and reviewing process than it actually benefits downstream users. Remove the ZIP/TGZ assembly from the uimaFIT build. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6425) uimaFIT 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6425:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README.md}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (x) Check the LICENSE and NOTICE files for the binary release
- (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) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (x) Clean local m2 repository
- (x) Do a test build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (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) 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!)
*Vote*
- (x) Call for a vote including URLs for
- (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)
*Publish release*
- (x) Copy existing Eclipse update site to the archive spot: {{svn copy -m
"create eclipse plugin archive for uimaj-3.0.0-3.2.0"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0}}
- (x) Remove old Eclipse update site: {{svn rm -m "Removing previous UIMAJ
update site to make space for new one"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (x) Move new Eclipse update site from the staging to the release spot: {{svn
mv -m "Installing UIMAJ 3.3.0 update site from accepted RC3"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (x) Move the other release artifacts from the staging spot to the dist spot
in SVN: {{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (x) Create new maintenance branch (when doing feature releases)
- (x) Update the version on the development branch (when doing feature releases)
- (x) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (x) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (x) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (x) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (x) Close release in Jira and GitHub
- (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:
*Prepare the code*
- (/) Create release branch
- (x) Update {{README.md}} file
- (x) Update {{RELEASE_NOTES.md}} file
- (x) Check the LICENSE and NOTICE files for the binary release
- (x) Make sure to remove all SNAPSHOT repositories and SNAPSH
[jira] [Updated] (UIMA-6425) uimaFIT 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6425:
-
Description:
*Prepare the code*
- (/) Create release branch
- (x) Update {{README}} file
- (x) Update {{RELEASE_NOTES.md}} file
- (x) Check the LICENSE and NOTICE files for the binary release
- (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) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (x) Clean local m2 repository
- (x) Do a test build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (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) 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!)
*Vote*
- (x) Call for a vote including URLs for
- (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)
*Publish release*
- (x) Copy existing Eclipse update site to the archive spot: {{svn copy -m
"create eclipse plugin archive for uimaj-3.0.0-3.2.0"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0}}
- (x) Remove old Eclipse update site: {{svn rm -m "Removing previous UIMAJ
update site to make space for new one"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (x) Move new Eclipse update site from the staging to the release spot: {{svn
mv -m "Installing UIMAJ 3.3.0 update site from accepted RC3"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (x) Move the other release artifacts from the staging spot to the dist spot
in SVN: {{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (x) Create new maintenance branch (when doing feature releases)
- (x) Update the version on the development branch (when doing feature releases)
- (x) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (x) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (x) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (x) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (x) Close release in Jira and GitHub
- (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:
*Prepare the code*
- (x) Create release branch
- (x) Update {{README}} file
- (x) Update {{RELEASE_NOTES.md}} file
- (x) Check the LICENSE and NOTICE files for the binary release
- (x) Make sure to remove all SNAPSHOT repositories and SNAPSHOT depen
[jira] [Updated] (UIMA-6425) uimaFIT 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6425:
-
Description:
*Prepare the code*
- (x) Create release branch
- (x) Update {{README}} file
- (x) Update {{RELEASE_NOTES.md}} file
- (x) Check the LICENSE and NOTICE files for the binary release
- (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) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (x) Clean local m2 repository
- (x) Do a test build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (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) 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!)
*Vote*
- (x) Call for a vote including URLs for
- (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)
*Publish release*
- (x) Copy existing Eclipse update site to the archive spot: {{svn copy -m
"create eclipse plugin archive for uimaj-3.0.0-3.2.0"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0}}
- (x) Remove old Eclipse update site: {{svn rm -m "Removing previous UIMAJ
update site to make space for new one"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (x) Move new Eclipse update site from the staging to the release spot: {{svn
mv -m "Installing UIMAJ 3.3.0 update site from accepted RC3"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (x) Move the other release artifacts from the staging spot to the dist spot
in SVN: {{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (x) Create new maintenance branch (when doing feature releases)
- (x) Update the version on the development branch (when doing feature releases)
- (x) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (x) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (x) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (x) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (x) Close release in Jira and GitHub
- (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.md}} 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) Update
[jira] [Updated] (UIMA-6425) uimaFIT 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6425:
-
Description:
*Prepare the code*
- (/) Create release branch
- (x) Update {{README.md}} file
- (x) Update {{RELEASE_NOTES.md}} file
- (x) Check the LICENSE and NOTICE files for the binary release
- (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) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (x) Update the version in the {{uimaj-eclipse-update-site}}
- (x) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (x) Clean local m2 repository
- (x) Do a test build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (x) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (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) 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!)
*Vote*
- (x) Call for a vote including URLs for
- (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)
*Publish release*
- (x) Copy existing Eclipse update site to the archive spot: {{svn copy -m
"create eclipse plugin archive for uimaj-3.0.0-3.2.0"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0}}
- (x) Remove old Eclipse update site: {{svn rm -m "Removing previous UIMAJ
update site to make space for new one"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (x) Move new Eclipse update site from the staging to the release spot: {{svn
mv -m "Installing UIMAJ 3.3.0 update site from accepted RC3"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (x) Move the other release artifacts from the staging spot to the dist spot
in SVN: {{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (x) Create new maintenance branch (when doing feature releases)
- (x) Update the version on the development branch (when doing feature releases)
- (x) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (x) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (x) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (x) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (x) Close release in Jira and GitHub
- (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:
*Prepare the code*
- (/) Create release branch
- (x) Update {{README}} file
- (x) Update {{RELEASE_NOTES.md}} file
- (x) Check the LICENSE and NOTICE files for the binary release
- (x) Make sure to remove all SNAPSHOT repositories and SNAPSHOT depen
[jira] [Resolved] (UIMA-6426) Upgrade to UIMA Java SDK 3.3.0
[ https://issues.apache.org/jira/browse/UIMA-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6426. -- Resolution: Fixed > Upgrade to UIMA Java SDK 3.3.0 > -- > > Key: UIMA-6426 > URL: https://issues.apache.org/jira/browse/UIMA-6426 > Project: UIMA > Issue Type: Improvement > Components: uimaFIT >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.3.0uimaFIT, 3.1.1ruta, 0.4.0jsoncas > > > Upgrade to UIMA Java SDK 3.3.0 > * (/) uimaFIT > * (/) ruta > * (/) jsoncas -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (UIMA-6379) Drop uimaj-adapter-soap due to Java 16 issues in Eclipse
[
https://issues.apache.org/jira/browse/UIMA-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6379.
--
Assignee: Richard Eckart de Castilho
Resolution: Duplicate
> Drop uimaj-adapter-soap due to Java 16 issues in Eclipse
>
>
> Key: UIMA-6379
> URL: https://issues.apache.org/jira/browse/UIMA-6379
> Project: UIMA
> Issue Type: Bug
> Components: Transport Adapters - SOAP, Vinci
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> uimaj-adapter-soap does not build in Eclipse against Java 16.
> When changing the Java source/target level in Maven Build from 1.8 to 16, the
> uimaj-adapter-soap displays errors: "QName cannot be resolved to a type".
> The reason for this is that the module has multiple dependencies including
> the JDK itself which provides this class and in Java Modules, a package must
> be exclusive to a certain module.
> In particular, the module depends on Apache Axis JAX-RPC which contains
> {{javax.xml.namespace.QName}}.
> I wonder if the SOAP module is actually still used by anybody - I'd
> personally tend towards dropping it.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (UIMA-6447) Update dependencies (Ruta 3.2.0)
[ https://issues.apache.org/jira/browse/UIMA-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6447: - Description: * (/) Apache UIMA Java SDK -> 3.3.0 * (/) Spring 4.3.30 -> 5.3.19 * (/) JUnit 4.12 -> 4.13.2 * (/) SLF4J 1.7.24 -> 1.7.36 * (/) ANTLR 3.5.2 -> 3.5.3 * (/) Caffeine 2.8.3 -> 2.9.3 (3.x requires Java 11) Upgrade to commons-collections4? was: * (/) Apache UIMA Java SDK -> 3.3.0 * ... Upgrade to commons-collections4? > Update dependencies (Ruta 3.2.0) > > > Key: UIMA-6447 > URL: https://issues.apache.org/jira/browse/UIMA-6447 > Project: UIMA > Issue Type: Improvement > Components: Ruta >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.2.0ruta > > > * (/) Apache UIMA Java SDK -> 3.3.0 > * (/) Spring 4.3.30 -> 5.3.19 > * (/) JUnit 4.12 -> 4.13.2 > * (/) SLF4J 1.7.24 -> 1.7.36 > * (/) ANTLR 3.5.2 -> 3.5.3 > * (/) Caffeine 2.8.3 -> 2.9.3 (3.x requires Java 11) > Upgrade to commons-collections4? -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Work started] (UIMA-6426) Upgrade to UIMA Java SDK 3.3.0
[ https://issues.apache.org/jira/browse/UIMA-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-6426 started by Richard Eckart de Castilho. > Upgrade to UIMA Java SDK 3.3.0 > -- > > Key: UIMA-6426 > URL: https://issues.apache.org/jira/browse/UIMA-6426 > Project: UIMA > Issue Type: Improvement > Components: uimaFIT >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.3.0uimaFIT, 3.1.1ruta, 0.4.0jsoncas > > > Upgrade to UIMA Java SDK 3.3.0 > * (/) uimaFIT > * (/) ruta > * (/) jsoncas -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Work started] (UIMA-6436) Move maintainer documentation from website into maintainer guide
[ https://issues.apache.org/jira/browse/UIMA-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-6436 started by Richard Eckart de Castilho. > Move maintainer documentation from website into maintainer guide > > > Key: UIMA-6436 > URL: https://issues.apache.org/jira/browse/UIMA-6436 > Project: UIMA > Issue Type: Bug >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.4.0SDK > > > Move maintainer documentation from website into maintainer guide which will > for the time being be located in the UIMA Java SDK as being the main project. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Work started] (UIMA-6447) Update dependencies (Ruta 3.2.0)
[ https://issues.apache.org/jira/browse/UIMA-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-6447 started by Richard Eckart de Castilho. > Update dependencies (Ruta 3.2.0) > > > Key: UIMA-6447 > URL: https://issues.apache.org/jira/browse/UIMA-6447 > Project: UIMA > Issue Type: Improvement > Components: Ruta >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.2.0ruta > > > * (/) Apache UIMA Java SDK -> 3.3.0 > * ... > Upgrade to commons-collections4? -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Work started] (UIMA-6444) Automatically sign Eclipse plugins during release builds
[ https://issues.apache.org/jira/browse/UIMA-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-6444 started by Richard Eckart de Castilho. > Automatically sign Eclipse plugins during release builds > > > Key: UIMA-6444 > URL: https://issues.apache.org/jira/browse/UIMA-6444 > Project: UIMA > Issue Type: Improvement >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.4.0SDK > > > Currently, we do not sign the Eclipse plugins because it is extra effort and > the old way of using the Symantec Service are gone anyway. > There is a new jarsigning approach which could be used. > Alternatively, it is meanwhile possible to embed PGP signatures in P2 > repositories. > Let's see which of these options are viable for us. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (UIMA-6220) README files for Ruta example projects
[ https://issues.apache.org/jira/browse/UIMA-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6220. -- Resolution: Duplicate > README files for Ruta example projects > -- > > Key: UIMA-6220 > URL: https://issues.apache.org/jira/browse/UIMA-6220 > Project: UIMA > Issue Type: Improvement > Components: Ruta >Reporter: Richard Eckart de Castilho >Priority: Minor > > As a new user, I import the example projects that come with Ruta into the > workspace, but then I have no idea what to do with them. It would be nice if > there was at least some README file in the root of each example project > briefly explaining what to run and where/how to look for the output. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6428) cas.select(TOP.class).count() has unexpected result
[ https://issues.apache.org/jira/browse/UIMA-6428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6428: - Fix Version/s: 3.4.0SDK > cas.select(TOP.class).count() has unexpected result > --- > > Key: UIMA-6428 > URL: https://issues.apache.org/jira/browse/UIMA-6428 > Project: UIMA > Issue Type: Bug > Components: Core Java Framework >Reporter: Richard Eckart de Castilho >Priority: Major > Fix For: 3.4.0SDK > > > Calling cas.select(TOP.class).count() returns a very large long number - > probably Long.MAX_VALUE. It is a bit unexpected... To get an accurate number, > one has to call cas.select(TOP.class).asList().size(). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6335) Optimize release process
[
https://issues.apache.org/jira/browse/UIMA-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6335:
-
Description:
The release checklist is pretty long. To facilitate releases, we should see
what can be optimized / cut.
- (/) {{README.md}} becomes version-independent and contains a proper project
description suitable as a GitHub repo landing page
- (/) {{RELEASE_NOTES.md}} contains only version-specific release notes and can
be largely copy/pasted to the release announcments mail/website/etc.
- Drop (most) binary ZIP releases and only offer source, Maven and for the Java
SDK / Ruta the Eclipse update site:
-- Rationale: The binary ZIPs use separate LICENSE/NOTICE files which need to
be checked/maintained - and this cannot be easily done automatically
was:
The release checklist is pretty long. To facilitate releases, we should see
what can be optimized / cut.
Ideas:
- Drop (most) binary ZIP releases and only offer source, Maven and for the Java
SDK / Ruta the Eclipse update site:
-- Rationale: The binary ZIPs use separate LICENSE/NOTICE files which need to
be checked/maintained - and this cannot be easily done automatically
- Integrate RELEASE_NOTES.html into the README file
-- Rationale: one less file to update
- Have a README.md or README.asciidoc file instead of a plain text file
-- Rationale: looks better in GitHub
- Reduce instances of the version string in the README file
-- Rationale: less chance to miss a version string when preparing a release
> Optimize release process
>
>
> Key: UIMA-6335
> URL: https://issues.apache.org/jira/browse/UIMA-6335
> Project: UIMA
> Issue Type: Improvement
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> The release checklist is pretty long. To facilitate releases, we should see
> what can be optimized / cut.
> - (/) {{README.md}} becomes version-independent and contains a proper project
> description suitable as a GitHub repo landing page
> - (/) {{RELEASE_NOTES.md}} contains only version-specific release notes and
> can be largely copy/pasted to the release announcments mail/website/etc.
>
> - Drop (most) binary ZIP releases and only offer source, Maven and for the
> Java SDK / Ruta the Eclipse update site:
> -- Rationale: The binary ZIPs use separate LICENSE/NOTICE files which need to
> be checked/maintained - and this cannot be easily done automatically
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (UIMA-6335) Optimize release process
[ https://issues.apache.org/jira/browse/UIMA-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho reassigned UIMA-6335: Assignee: Richard Eckart de Castilho > Optimize release process > > > Key: UIMA-6335 > URL: https://issues.apache.org/jira/browse/UIMA-6335 > Project: UIMA > Issue Type: Improvement >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > > The release checklist is pretty long. To facilitate releases, we should see > what can be optimized / cut. > Ideas: > - Drop (most) binary ZIP releases and only offer source, Maven and for the > Java SDK / Ruta the Eclipse update site: > -- Rationale: The binary ZIPs use separate LICENSE/NOTICE files which need to > be checked/maintained - and this cannot be easily done automatically > - Integrate RELEASE_NOTES.html into the README file > -- Rationale: one less file to update > - Have a README.md or README.asciidoc file instead of a plain text file > -- Rationale: looks better in GitHub > - Reduce instances of the version string in the README file > -- Rationale: less chance to miss a version string when preparing a release -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Work started] (UIMA-6335) Optimize release process
[ https://issues.apache.org/jira/browse/UIMA-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-6335 started by Richard Eckart de Castilho. > Optimize release process > > > Key: UIMA-6335 > URL: https://issues.apache.org/jira/browse/UIMA-6335 > Project: UIMA > Issue Type: Improvement >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > > The release checklist is pretty long. To facilitate releases, we should see > what can be optimized / cut. > Ideas: > - Drop (most) binary ZIP releases and only offer source, Maven and for the > Java SDK / Ruta the Eclipse update site: > -- Rationale: The binary ZIPs use separate LICENSE/NOTICE files which need to > be checked/maintained - and this cannot be easily done automatically > - Integrate RELEASE_NOTES.html into the README file > -- Rationale: one less file to update > - Have a README.md or README.asciidoc file instead of a plain text file > -- Rationale: looks better in GitHub > - Reduce instances of the version string in the README file > -- Rationale: less chance to miss a version string when preparing a release -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Work started] (UIMA-6427) Clean up update sites
[ https://issues.apache.org/jira/browse/UIMA-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-6427 started by Richard Eckart de Castilho. > Clean up update sites > - > > Key: UIMA-6427 > URL: https://issues.apache.org/jira/browse/UIMA-6427 > Project: UIMA > Issue Type: Task > Components: Core Java Framework, Ruta >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > > The UIMA project dist area [1] appears to have more versions present > than it should. > The policy can be found at [2] under the "Current and older releases" heading. > In particular, there appear to be lots of versions of the individual > components > under the Eclipse Update V3 site. > Any versions that are not being developed should please be removed > from the dist area, and please also update any download pages and > release process documentation accordingly. > [1] https://dist.apache.org/repos/dist/release/uima > [2] https://infra.apache.org/release-download-pages.html > > * (/) UIMA Java SDK Update Site > * (x) UIMA Ruta Update Site > * (x) UIMA-AS Update Site(?) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (UIMA-6427) Clean up update sites
[ https://issues.apache.org/jira/browse/UIMA-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho reassigned UIMA-6427: Assignee: Richard Eckart de Castilho (was: Peter Klügl) > Clean up update sites > - > > Key: UIMA-6427 > URL: https://issues.apache.org/jira/browse/UIMA-6427 > Project: UIMA > Issue Type: Task > Components: Core Java Framework, Ruta >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > > The UIMA project dist area [1] appears to have more versions present > than it should. > The policy can be found at [2] under the "Current and older releases" heading. > In particular, there appear to be lots of versions of the individual > components > under the Eclipse Update V3 site. > Any versions that are not being developed should please be removed > from the dist area, and please also update any download pages and > release process documentation accordingly. > [1] https://dist.apache.org/repos/dist/release/uima > [2] https://infra.apache.org/release-download-pages.html > > * (/) UIMA Java SDK Update Site > * (x) UIMA Ruta Update Site > * (x) UIMA-AS Update Site(?) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6427) Clean up update sites
[ https://issues.apache.org/jira/browse/UIMA-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6427: - Description: The UIMA project dist area [1] appears to have more versions present than it should. The policy can be found at [2] under the "Current and older releases" heading. In particular, there appear to be lots of versions of the individual components under the Eclipse Update V3 site. Any versions that are not being developed should please be removed from the dist area, and please also update any download pages and release process documentation accordingly. [1] https://dist.apache.org/repos/dist/release/uima [2] https://infra.apache.org/release-download-pages.html * (/) UIMA Java SDK Update Site * (x) UIMA Ruta Update Site * (x) UIMA-AS Update Site(?) was: The UIMA project dist area [1] appears to have more versions present than it should. The policy can be found at [2] under the "Current and older releases" heading. In particular, there appear to be lots of versions of the individual components under the Eclipse Update V3 site. Any versions that are not being developed should please be removed from the dist area, and please also update any download pages and release process documentation accordingly. [1] https://dist.apache.org/repos/dist/release/uima [2] https://infra.apache.org/release-download-pages.html > Clean up update sites > - > > Key: UIMA-6427 > URL: https://issues.apache.org/jira/browse/UIMA-6427 > Project: UIMA > Issue Type: Task > Components: Core Java Framework, Ruta >Reporter: Richard Eckart de Castilho >Assignee: Peter Klügl >Priority: Major > > The UIMA project dist area [1] appears to have more versions present > than it should. > The policy can be found at [2] under the "Current and older releases" heading. > In particular, there appear to be lots of versions of the individual > components > under the Eclipse Update V3 site. > Any versions that are not being developed should please be removed > from the dist area, and please also update any download pages and > release process documentation accordingly. > [1] https://dist.apache.org/repos/dist/release/uima > [2] https://infra.apache.org/release-download-pages.html > > * (/) UIMA Java SDK Update Site > * (x) UIMA Ruta Update Site > * (x) UIMA-AS Update Site(?) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (UIMA-6427) Clean up update sites
[ https://issues.apache.org/jira/browse/UIMA-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17534918#comment-17534918 ] Richard Eckart de Castilho commented on UIMA-6427: -- The UIMA Java SDK update site has been cleaned up and now only contains the 3.3.0 release. > Clean up update sites > - > > Key: UIMA-6427 > URL: https://issues.apache.org/jira/browse/UIMA-6427 > Project: UIMA > Issue Type: Task > Components: Core Java Framework, Ruta >Reporter: Richard Eckart de Castilho >Assignee: Peter Klügl >Priority: Major > > The UIMA project dist area [1] appears to have more versions present > than it should. > The policy can be found at [2] under the "Current and older releases" heading. > In particular, there appear to be lots of versions of the individual > components > under the Eclipse Update V3 site. > Any versions that are not being developed should please be removed > from the dist area, and please also update any download pages and > release process documentation accordingly. > [1] https://dist.apache.org/repos/dist/release/uima > [2] https://infra.apache.org/release-download-pages.html -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (UIMA-6429) uima-uimaj uses axis 1 (end of life with open security issues)
[ https://issues.apache.org/jira/browse/UIMA-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho reassigned UIMA-6429: Assignee: Richard Eckart de Castilho > uima-uimaj uses axis 1 (end of life with open security issues) > -- > > Key: UIMA-6429 > URL: https://issues.apache.org/jira/browse/UIMA-6429 > Project: UIMA > Issue Type: Improvement > Components: Transport Adapters - SOAP, Vinci >Reporter: PJ Fanning >Assignee: Richard Eckart de Castilho >Priority: Major > > [https://github.com/apache/uima-uimaj/blob/main/uimaj-adapter-soap/pom.xml] > > eg https://github.com/advisories/GHSA-55w9-c3g2-4rrh -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (UIMA-6429) uima-uimaj uses axis 1 (end of life with open security issues)
[ https://issues.apache.org/jira/browse/UIMA-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6429. -- Resolution: Done > uima-uimaj uses axis 1 (end of life with open security issues) > -- > > Key: UIMA-6429 > URL: https://issues.apache.org/jira/browse/UIMA-6429 > Project: UIMA > Issue Type: Improvement > Components: Transport Adapters - SOAP, Vinci >Reporter: PJ Fanning >Priority: Major > > [https://github.com/apache/uima-uimaj/blob/main/uimaj-adapter-soap/pom.xml] > > eg https://github.com/advisories/GHSA-55w9-c3g2-4rrh -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6429) uima-uimaj uses axis 1 (end of life with open security issues)
[ https://issues.apache.org/jira/browse/UIMA-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6429: - Component/s: Transport Adapters - SOAP, Vinci > uima-uimaj uses axis 1 (end of life with open security issues) > -- > > Key: UIMA-6429 > URL: https://issues.apache.org/jira/browse/UIMA-6429 > Project: UIMA > Issue Type: Improvement > Components: Transport Adapters - SOAP, Vinci >Reporter: PJ Fanning >Priority: Major > > [https://github.com/apache/uima-uimaj/blob/main/uimaj-adapter-soap/pom.xml] > > eg https://github.com/advisories/GHSA-55w9-c3g2-4rrh -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (UIMA-6429) uima-uimaj uses axis 1 (end of life with open security issues)
[ https://issues.apache.org/jira/browse/UIMA-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17534917#comment-17534917 ] Richard Eckart de Castilho commented on UIMA-6429: -- No longer included with UIMA 3.3.0 (see UIMA-6265). > uima-uimaj uses axis 1 (end of life with open security issues) > -- > > Key: UIMA-6429 > URL: https://issues.apache.org/jira/browse/UIMA-6429 > Project: UIMA > Issue Type: Improvement >Reporter: PJ Fanning >Priority: Major > > [https://github.com/apache/uima-uimaj/blob/main/uimaj-adapter-soap/pom.xml] > > eg https://github.com/advisories/GHSA-55w9-c3g2-4rrh -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6447) Update dependencies (Ruta 3.2.0)
[ https://issues.apache.org/jira/browse/UIMA-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6447: - Description: * (/) Apache UIMA Java SDK -> 3.3.0 * ... Upgrade to commons-collections4? was: * (/) Apache UIMA Java SDK -> 3.3.0 * ... > Update dependencies (Ruta 3.2.0) > > > Key: UIMA-6447 > URL: https://issues.apache.org/jira/browse/UIMA-6447 > Project: UIMA > Issue Type: Improvement > Components: Ruta >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.2.0ruta > > > * (/) Apache UIMA Java SDK -> 3.3.0 > * ... > Upgrade to commons-collections4? -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6432) Upgrade dependencies (uimaFIT 3.3.0)
[ https://issues.apache.org/jira/browse/UIMA-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6432: - Summary: Upgrade dependencies (uimaFIT 3.3.0) (was: Upgrade dependencies) > Upgrade dependencies (uimaFIT 3.3.0) > > > Key: UIMA-6432 > URL: https://issues.apache.org/jira/browse/UIMA-6432 > Project: UIMA > Issue Type: Improvement > Components: uimaFIT >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.3.0uimaFIT > > > Upgrade dependencies. > - Spring 4.3.30 -> 5.3.18 > - Commons IO 2.8.0 -> 2.11.0 > - Mockito 3.2.4 -> 4.4.0 (test) > - japicmp-maven-plugin 0.15.3 -> 0.15.7 (build) > - groovy-jsr223 2.5.14 -> 2.5.16 (build) > - groovy-all 3.0.7 -> 3.0.17 (build) > - maven-gpg-plugin 1.6 -> 3.0.1 (build) > - doxia-core 1.7 -> 1.11.1 (build) > - maven-compiler-plugin 3.8.1 -> 3.10.1 (build) > - maven-javadoc-plugin 3.1.0 -> 3.3.2 (build) > - maven-enforcer-plugin 3.0.0-M3 -> 3.0.0 (build) > - groovy-jsr223 2.5.14 -> 3.0.10 (build) > - groovy-all 3.0.7 -> 3.0.10 (build) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (UIMA-6447) Update dependencies (Ruta 3.2.0)
Richard Eckart de Castilho created UIMA-6447: Summary: Update dependencies (Ruta 3.2.0) Key: UIMA-6447 URL: https://issues.apache.org/jira/browse/UIMA-6447 Project: UIMA Issue Type: Improvement Components: Ruta Reporter: Richard Eckart de Castilho Assignee: Richard Eckart de Castilho Fix For: 3.2.0ruta * (/) Apache UIMA Java SDK -> 3.3.0 * ... -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6426) Upgrade to UIMA Java SDK 3.3.0
[ https://issues.apache.org/jira/browse/UIMA-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6426: - Description: Upgrade to UIMA Java SDK 3.3.0 * (/) uimaFIT * (/) ruta * (/) jsoncas was: Upgrade to UIMA Java SDK 3.3.0 * (/) uimaFIT * (x) ruta * (/) jsoncas > Upgrade to UIMA Java SDK 3.3.0 > -- > > Key: UIMA-6426 > URL: https://issues.apache.org/jira/browse/UIMA-6426 > Project: UIMA > Issue Type: Improvement > Components: uimaFIT >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.3.0uimaFIT, 3.1.1ruta, 0.4.0jsoncas > > > Upgrade to UIMA Java SDK 3.3.0 > * (/) uimaFIT > * (/) ruta > * (/) jsoncas -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6426) Upgrade to UIMA Java SDK 3.3.0
[ https://issues.apache.org/jira/browse/UIMA-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6426: - Description: Upgrade to UIMA Java SDK 3.3.0 * (/) uimaFIT * (x) ruta * (/) jsoncas was: Upgrade to UIMA Java SDK 3.3.0 * (/) uimaFIT * (x) ruta * (x) jsoncas > Upgrade to UIMA Java SDK 3.3.0 > -- > > Key: UIMA-6426 > URL: https://issues.apache.org/jira/browse/UIMA-6426 > Project: UIMA > Issue Type: Improvement > Components: uimaFIT >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.3.0uimaFIT, 3.1.1ruta, 0.4.0jsoncas > > > Upgrade to UIMA Java SDK 3.3.0 > * (/) uimaFIT > * (x) ruta > * (/) jsoncas -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6426) Upgrade to UIMA Java SDK 3.3.0
[ https://issues.apache.org/jira/browse/UIMA-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6426: - Description: Upgrade to UIMA Java SDK 3.3.0 * (/) uimaFIT * (x) ruta * (x) jsoncas was:Upgrade to UIMA Java SDK 3.3.0 > Upgrade to UIMA Java SDK 3.3.0 > -- > > Key: UIMA-6426 > URL: https://issues.apache.org/jira/browse/UIMA-6426 > Project: UIMA > Issue Type: Improvement > Components: uimaFIT >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.3.0uimaFIT, 3.1.1ruta, 0.4.0jsoncas > > > Upgrade to UIMA Java SDK 3.3.0 > * (/) uimaFIT > * (x) ruta > * (x) jsoncas -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (UIMA-6330) uimaFIT 2.6.0 release
[
https://issues.apache.org/jira/browse/UIMA-6330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6330.
--
Resolution: Won't Fix
> uimaFIT 2.6.0 release
> -
>
> Key: UIMA-6330
> URL: https://issues.apache.org/jira/browse/UIMA-6330
> Project: UIMA
> Issue Type: Task
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README.md}} file
> - (/) 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
> - (/) Update LICENSE and NOTICE files used for binary distribution
> ({{src/main/dist-bin}})
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) 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
> - (/) Call for a vote including URLs for
> ** Staging repository
> ** SVN staging spot (artifacts)
> ** 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.20.7#820007)
[jira] [Commented] (UIMA-6330) uimaFIT 2.6.0 release
[
https://issues.apache.org/jira/browse/UIMA-6330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17534798#comment-17534798
]
Richard Eckart de Castilho commented on UIMA-6330:
--
Keeping this branch around for a while - but... considering the recent security
issues in the Spring Library that is used by uimaFIT, I would like to
indefinitely postpone any uimaFIT v2 releases. The version of Spring that
uimaFIT v2 uses is two major versions behind and there are no fixes anymore for
the recent issues.
So unless somebody steps up with a strong interest in a uimaFIT v2 release and
a good suggestion regarding what to do wrt Spring, there probably won't be
further uimaFIT v2 releases.
Please all upgrade to UIMA/uimaFIT v3.
> uimaFIT 2.6.0 release
> -
>
> Key: UIMA-6330
> URL: https://issues.apache.org/jira/browse/UIMA-6330
> Project: UIMA
> Issue Type: Task
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README.md}} file
> - (/) 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
> - (/) Update LICENSE and NOTICE files used for binary distribution
> ({{src/main/dist-bin}})
> - (/) Clean local m2 repository and build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) 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
> - (/) Call for a vote including URLs for
> ** Staging repository
> ** SVN staging spot (artifacts)
> ** 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.20.7#820007)
[jira] [Updated] (UIMA-6445) CPE not calling destroy if there was an exception
[ https://issues.apache.org/jira/browse/UIMA-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6445: - Fix Version/s: 3.3.1SDK > CPE not calling destroy if there was an exception > - > > Key: UIMA-6445 > URL: https://issues.apache.org/jira/browse/UIMA-6445 > Project: UIMA > Issue Type: Bug > Components: Collection Processing >Affects Versions: 3.3.0SDK >Reporter: Richard Eckart de Castilho >Priority: Major > Fix For: 3.3.1SDK > > > There are indications that the CPE is not calling destroy if there was an > exception. > Need a test case for this. > Need to think if calling destroy is ok or whether it might disrupt some > functionality of CPEs (checkpoints?). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6395) Apache UIMA Java SDK 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6395:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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
- (/) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (/) 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
- (/) 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!)
*Vote*
- (/) Call for a vote including URLs for
- (/) 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)
*Publish release*
- (/) Copy existing Eclipse update site to the archive spot: {{svn copy -m
"create eclipse plugin archive for uimaj-3.0.0-3.2.0"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0}}
- (/) Remove old Eclipse update site: {{svn rm -m "Removing previous UIMAJ
update site to make space for new one"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (/) Move new Eclipse update site from the staging to the release spot: {{svn
mv -m "Installing UIMAJ 3.3.0 update site from accepted RC3"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (/) Move the other release artifacts from the staging spot to the dist spot
in SVN: {{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (/) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (/) Create new maintenance branch (when doing feature releases)
- (/) Update the version on the development branch (when doing feature releases)
- (/) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (/) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (/) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (/) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (/) Close release in Jira and GitHub
- (/) 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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} file
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT depen
[jira] [Updated] (UIMA-6395) Apache UIMA Java SDK 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6395:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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
- (/) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (/) 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
- (/) 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!)
*Vote*
- (/) Call for a vote including URLs for
- (/) 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)
*Publish release*
- (/) Copy existing Eclipse update site to the archive spot: {{svn copy -m
"create eclipse plugin archive for uimaj-3.0.0-3.2.0"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0}}
- (/) Remove old Eclipse update site: {{svn rm -m "Removing previous UIMAJ
update site to make space for new one"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (/) Move new Eclipse update site from the staging to the release spot: {{svn
mv -m "Installing UIMAJ 3.3.0 update site from accepted RC3"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (/) Move the other release artifacts from the staging spot to the dist spot
in SVN: {{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (/) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (/) Update the version on the development branch
- (/) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (/) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (/) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (/) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (/) Close release in Jira and GitHub
- (/) 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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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] [Resolved] (UIMA-6446) Complexities around enhancing classes with their resource name
[
https://issues.apache.org/jira/browse/UIMA-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6446.
--
Fix Version/s: 3.3.0uimaFIT
Resolution: Fixed
> Complexities around enhancing classes with their resource name
> --
>
> Key: UIMA-6446
> URL: https://issues.apache.org/jira/browse/UIMA-6446
> Project: UIMA
> Issue Type: Bug
> Components: uimaFIT, uimaFIT-Maven-Plugin
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.3.0uimaFIT
>
>
> The uimaFIT Maven Plugin contains a mojo called {{enhance}}. This mojo adds a
> {{ResourceMetaData}} annotation to every class that does not already have one.
> In that case, it also sets the {{name}} field using the resource class name.
> Now consider the following scenario:
> * component class {{Child}} inherits from (abstract) component class
> {{Parent}}
> * for some reason, the class {{Parent}} has been enhanced and therefore
> carries an auto-generated {{ResourceMetaData("Parent")}} annotation
> * for some reason, the class {{Child}} has not been enhanced and also does
> not carry a {{ResourceMetaData}} annotation
> When generating a descriptor for the component now, e.g. using
> {{createEngineDescription(Child.class}}, the name of the resulting component
> will be {{Parent}}.
> It would seem the approach to solve this problem is to only consider the
> {{ResourceMetaData.name}} field when it is defined directly on a component.
> However, for the other fields like {{copyright, description, vendor,
> version}} it would likewise seem problematic to look them up in parent
> classes. In many cases, the parent and the child will be in the same project
> - but in many other cases, they may also not be.
> It would seem the bug is not in the uimaFIT Maven Plugin for generating the
> {{ResourceMetaData}} annotation (even on abstract classes), but rather in
> {{createEngineDescription}}-and-friends for looking in superclasses for
> {{ResourceMetaData}} annotations.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (UIMA-6374) Create CAS (de)serialization test suite
[ https://issues.apache.org/jira/browse/UIMA-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6374. -- Resolution: Fixed > Create CAS (de)serialization test suite > --- > > Key: UIMA-6374 > URL: https://issues.apache.org/jira/browse/UIMA-6374 > Project: UIMA > Issue Type: New Feature > Components: Core Java Framework >Reporter: Richard Eckart de Castilho >Assignee: Peter Klügl >Priority: Major > Fix For: 3.3.0SDK > > > Create a test suite for checking (de)serialization mechanisms. The suite > should allow to easily configure a particular (de)serialization mechansim and > to check different (de)serialization round-trip scenarios. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6395) Apache UIMA Java SDK 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6395:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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
- (/) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (/) 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
- (/) 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!)
*Vote*
- (/) Call for a vote including URLs for
- (/) 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)
*Publish release*
- (/) Copy existing Eclipse update site to the archive spot: {{svn copy -m
"create eclipse plugin archive for uimaj-3.0.0-3.2.0"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0}}
- (/) Remove old Eclipse update site: {{svn rm -m "Removing previous UIMAJ
update site to make space for new one"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (/) Move new Eclipse update site from the staging to the release spot: {{svn
mv -m "Installing UIMAJ 3.3.0 update site from accepted RC3"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (/) Move the other release artifacts from the staging spot to the dist spot
in SVN: {{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (/) Release staging repository at {{https://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 the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (/) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (/) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (/) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (/) Close release in Jira and GitHub
- (/) 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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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
- (/) Check that the Eclipse `classpath` files which are checked in as part of
the exa
[jira] [Updated] (UIMA-6395) Apache UIMA Java SDK 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6395:
-
Fix Version/s: 3.3.0SDK
> Apache UIMA Java SDK 3.3.0 release
> --
>
> Key: UIMA-6395
> URL: https://issues.apache.org/jira/browse/UIMA-6395
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.3.0SDK
>
>
> *Prepare the code*
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.md}} 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
> - (/) Check that the Eclipse `classpath` files which are checked in as part
> of the examples have the proper version numbers for their JARs
> - (/) Update the version in the {{uimaj-eclipse-update-site}}
> - (/) Set {{dropPrevVersions}} to {{true}} in the
> {{uimaj-eclipse-update-site}} POM
> *Release build*
> - (/) Clean local m2 repository
> - (/) Do a test build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> - (/) Build the Eclipse update site using {{mvn -f
> uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
> *Stage release candidate*
> - (/) 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
> - (/) 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!)
> *Vote*
> - (/) Call for a vote including URLs for
> - (/) 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)
> *Publish release*
> - (/) Copy existing Eclipse update site to the archive spot: {{svn copy -m
> "create eclipse plugin archive for uimaj-3.0.0-3.2.0"
> https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
> https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0}}
> - (/) Remove old Eclipse update site: {{svn rm -m "Removing previous UIMAJ
> update site to make space for new one"
> https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
> - (/) Move new Eclipse update site from the staging to the release spot:
> {{svn mv -m "Installing UIMAJ 3.3.0 update site from accepted RC3"
> https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3/eclipse-update-site-v3/uimaj
>
> https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
> - (/) Move the other release artifacts from the staging spot to the dist spot
> in SVN: {{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
> https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
> https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
> - (/) Release staging repository at {{https://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 the "current" release on the website with the new content (and
> delete anything no longer part of the "current" release)
> - (/) Copy the "current" release to a versioned release {{svn copy -m
> "Current UIMAJ release is 3.3.0"
> https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
>
> https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
> - (/) Copy the versioned release to the archive spot already: {{svn copy -m
> "Archiving UIMAJ 3.3.0 documentation"
> https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
> https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
> - (/) Delete the previous version documentation: {{svn rm -m "Deleting
> documentation for previous release"
> h
[jira] [Resolved] (UIMA-6395) Apache UIMA Java SDK 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6395.
--
Resolution: Fixed
> Apache UIMA Java SDK 3.3.0 release
> --
>
> Key: UIMA-6395
> URL: https://issues.apache.org/jira/browse/UIMA-6395
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 3.3.0SDK
>
>
> *Prepare the code*
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.md}} 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
> - (/) Check that the Eclipse `classpath` files which are checked in as part
> of the examples have the proper version numbers for their JARs
> - (/) Update the version in the {{uimaj-eclipse-update-site}}
> - (/) Set {{dropPrevVersions}} to {{true}} in the
> {{uimaj-eclipse-update-site}} POM
> *Release build*
> - (/) Clean local m2 repository
> - (/) Do a test build locally with {{-Papache-release}}
> - (/) Check the issues report in {{issuesFixed}} if it looks ok
> - (/) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> - (/) Build the Eclipse update site using {{mvn -f
> uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
> *Stage release candidate*
> - (/) 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
> - (/) 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!)
> *Vote*
> - (/) Call for a vote including URLs for
> - (/) 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)
> *Publish release*
> - (/) Copy existing Eclipse update site to the archive spot: {{svn copy -m
> "create eclipse plugin archive for uimaj-3.0.0-3.2.0"
> https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
> https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0}}
> - (/) Remove old Eclipse update site: {{svn rm -m "Removing previous UIMAJ
> update site to make space for new one"
> https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
> - (/) Move new Eclipse update site from the staging to the release spot:
> {{svn mv -m "Installing UIMAJ 3.3.0 update site from accepted RC3"
> https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3/eclipse-update-site-v3/uimaj
>
> https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
> - (/) Move the other release artifacts from the staging spot to the dist spot
> in SVN: {{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
> https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
> https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
> - (/) Release staging repository at {{https://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 the "current" release on the website with the new content (and
> delete anything no longer part of the "current" release)
> - (/) Copy the "current" release to a versioned release {{svn copy -m
> "Current UIMAJ release is 3.3.0"
> https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
>
> https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
> - (/) Copy the versioned release to the archive spot already: {{svn copy -m
> "Archiving UIMAJ 3.3.0 documentation"
> https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
> https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
> - (/) Delete the previous version documentation: {{svn rm -m "Deleting
> documentation for previous release"
> h
[jira] [Updated] (UIMA-6446) Complexities around enhancing classes with their resource name
[
https://issues.apache.org/jira/browse/UIMA-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6446:
-
Description:
The uimaFIT Maven Plugin contains a mojo called {{enhance}}. This mojo adds a
{{ResourceMetaData}} annotation to every class that does not already have one.
In that case, it also sets the {{name}} field using the resource class name.
Now consider the following scenario:
* component class {{Child}} inherits from (abstract) component class {{Parent}}
* for some reason, the class {{Parent}} has been enhanced and therefore carries
an auto-generated {{ResourceMetaData("Parent")}} annotation
* for some reason, the class {{Child}} has not been enhanced and also does not
carry a {{ResourceMetaData}} annotation
When generating a descriptor for the component now, e.g. using
{{createEngineDescription(Child.class}}, the name of the resulting component
will be {{Parent}}.
It would seem the approach to solve this problem is to only consider the
{{ResourceMetaData.name}} field when it is defined directly on a component.
However, for the other fields like {{copyright, description, vendor, version}}
it would likewise seem problematic to look them up in parent classes. In many
cases, the parent and the child will be in the same project - but in many other
cases, they may also not be.
It would seem the bug is not in the uimaFIT Maven Plugin for generating the
{{ResourceMetaData}} annotation (even on abstract classes), but rather in
{{createEngineDescription}}-and-friends for looking in superclasses for
{{ResourceMetaData}} annotations.
was:
The uimaFIT Maven Plugin contains a mojo called {{enhance}}. This mojo adds a
{{ResourceMetaData}} annotation to every class that does not already have one.
In that case, it also sets the {{name}} field using the resource class name.
Now consider the following scenario:
* component class {{Child}} inherits from (abstract) component class {{Parent}}
* for some reason, the class {{Parent}} has been enhanced and therefore carries
an auto-generated {{ResourceMetaData("Parent")}} annotation
* for some reason, the class {{Child}} has not been enhanced and also does not
carry a {{ResourceMetaData}} annotation
When generating a descriptor for the component now, e.g. using
{{createEngineDescription(Child.class}}, the name of the resulting component
will be {{Parent}}.
It would seem the approach to solve this problem is to only consider the
{{ResourceMetaData.name}} field when it is defined directly on a component.
However, for the other fields like {{copyright, description, vendor, version}}
it would likewise seem problematic to look them up in parent classes. In many
cases, the parent and the child will be in the same project - but in many other
cases, they may also not be.
> Complexities around enhancing classes with their resource name
> --
>
> Key: UIMA-6446
> URL: https://issues.apache.org/jira/browse/UIMA-6446
> Project: UIMA
> Issue Type: Bug
> Components: uimaFIT, uimaFIT-Maven-Plugin
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> The uimaFIT Maven Plugin contains a mojo called {{enhance}}. This mojo adds a
> {{ResourceMetaData}} annotation to every class that does not already have one.
> In that case, it also sets the {{name}} field using the resource class name.
> Now consider the following scenario:
> * component class {{Child}} inherits from (abstract) component class
> {{Parent}}
> * for some reason, the class {{Parent}} has been enhanced and therefore
> carries an auto-generated {{ResourceMetaData("Parent")}} annotation
> * for some reason, the class {{Child}} has not been enhanced and also does
> not carry a {{ResourceMetaData}} annotation
> When generating a descriptor for the component now, e.g. using
> {{createEngineDescription(Child.class}}, the name of the resulting component
> will be {{Parent}}.
> It would seem the approach to solve this problem is to only consider the
> {{ResourceMetaData.name}} field when it is defined directly on a component.
> However, for the other fields like {{copyright, description, vendor,
> version}} it would likewise seem problematic to look them up in parent
> classes. In many cases, the parent and the child will be in the same project
> - but in many other cases, they may also not be.
> It would seem the bug is not in the uimaFIT Maven Plugin for generating the
> {{ResourceMetaData}} annotation (even on abstract classes), but rather in
> {{createEngineDescription}}-and-friends for looking in superclasses for
> {{ResourceMetaData}} annotations.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (UIMA-6446) Complexities around enhancing classes with their resource name
Richard Eckart de Castilho created UIMA-6446:
Summary: Complexities around enhancing classes with their resource
name
Key: UIMA-6446
URL: https://issues.apache.org/jira/browse/UIMA-6446
Project: UIMA
Issue Type: Bug
Components: uimaFIT-Maven-Plugin
Reporter: Richard Eckart de Castilho
Assignee: Richard Eckart de Castilho
The uimaFIT Maven Plugin contains a mojo called {{enhance}}. This mojo adds a
{{ResourceMetaData}} annotation to every class that does not already have one.
In that case, it also sets the {{name}} field using the resource class name.
Now consider the following scenario:
* component class {{Child}} inherits from (abstract) component class {{Parent}}
* for some reason, the class {{Parent}} has been enhanced and therefore carries
an auto-generated {{ResourceMetaData("Parent")}} annotation
* for some reason, the class {{Child}} has not been enhanced and also does not
carry a {{ResourceMetaData}} annotation
When generating a descriptor for the component now, e.g. using
{{createEngineDescription(Child.class}}, the name of the resulting component
will be {{Parent}}.
It would seem the approach to solve this problem is to only consider the
{{ResourceMetaData.name}} field when it is defined directly on a component.
However, for the other fields like {{copyright, description, vendor, version}}
it would likewise seem problematic to look them up in parent classes. In many
cases, the parent and the child will be in the same project - but in many other
cases, they may also not be.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (UIMA-6446) Complexities around enhancing classes with their resource name
[
https://issues.apache.org/jira/browse/UIMA-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6446:
-
Component/s: uimaFIT
> Complexities around enhancing classes with their resource name
> --
>
> Key: UIMA-6446
> URL: https://issues.apache.org/jira/browse/UIMA-6446
> Project: UIMA
> Issue Type: Bug
> Components: uimaFIT, uimaFIT-Maven-Plugin
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> The uimaFIT Maven Plugin contains a mojo called {{enhance}}. This mojo adds a
> {{ResourceMetaData}} annotation to every class that does not already have one.
> In that case, it also sets the {{name}} field using the resource class name.
> Now consider the following scenario:
> * component class {{Child}} inherits from (abstract) component class
> {{Parent}}
> * for some reason, the class {{Parent}} has been enhanced and therefore
> carries an auto-generated {{ResourceMetaData("Parent")}} annotation
> * for some reason, the class {{Child}} has not been enhanced and also does
> not carry a {{ResourceMetaData}} annotation
> When generating a descriptor for the component now, e.g. using
> {{createEngineDescription(Child.class}}, the name of the resulting component
> will be {{Parent}}.
> It would seem the approach to solve this problem is to only consider the
> {{ResourceMetaData.name}} field when it is defined directly on a component.
> However, for the other fields like {{copyright, description, vendor,
> version}} it would likewise seem problematic to look them up in parent
> classes. In many cases, the parent and the child will be in the same project
> - but in many other cases, they may also not be.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (UIMA-6395) Apache UIMA Java SDK 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6395:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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
- (/) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (/) 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
- (/) 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!)
*Vote*
- (/) Call for a vote including URLs for
- (/) 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)
*Publish release*
- (/) Copy existing Eclipse update site to the archive spot: {{svn copy -m
"create eclipse plugin archive for uimaj-3.0.0-3.2.0"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0}}
- (/) Remove old Eclipse update site: {{svn rm -m "Removing previous UIMAJ
update site to make space for new one"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (/) Move new Eclipse update site from the staging to the release spot: {{svn
mv -m "Installing UIMAJ 3.3.0 update site from accepted RC3"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (/) Move the other release artifacts from the staging spot to the dist spot
in SVN: {{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (/) Release staging repository at {{https://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 the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (/) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (/) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (/) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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
- (/) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper ver
[jira] [Updated] (UIMA-6445) CPE not calling destroy if there was an exception
[ https://issues.apache.org/jira/browse/UIMA-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6445: - Affects Version/s: 3.3.0SDK > CPE not calling destroy if there was an exception > - > > Key: UIMA-6445 > URL: https://issues.apache.org/jira/browse/UIMA-6445 > Project: UIMA > Issue Type: Bug > Components: Collection Processing >Affects Versions: 3.3.0SDK >Reporter: Richard Eckart de Castilho >Priority: Major > > There are indications that the CPE is not calling destroy if there was an > exception. > Need a test case for this. > Need to think if calling destroy is ok or whether it might disrupt some > functionality of CPEs (checkpoints?). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (UIMA-6445) CPE not calling destroy if there was an exception
Richard Eckart de Castilho created UIMA-6445: Summary: CPE not calling destroy if there was an exception Key: UIMA-6445 URL: https://issues.apache.org/jira/browse/UIMA-6445 Project: UIMA Issue Type: Bug Components: Collection Processing Reporter: Richard Eckart de Castilho There are indications that the CPE is not calling destroy if there was an exception. Need a test case for this. Need to think if calling destroy is ok or whether it might disrupt some functionality of CPEs (checkpoints?). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (UIMA-6395) Apache UIMA Java SDK 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6395:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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
- (/) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (/) 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
- (/) 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!)
*Vote*
- (/) Call for a vote including URLs for
- (/) 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)
*Publish release*
- (/) Copy existing Eclipse update site to the archive spot: {{svn copy -m
"create eclipse plugin archive for uimaj-3.0.0-3.2.0"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0}}
- (/) Remove old Eclipse update site: {{svn rm -m "Removing previous UIMAJ
update site to make space for new one"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (/) Move new Eclipse update site from the staging to the release spot: {{svn
mv -m "Installing UIMAJ 3.3.0 update site from accepted RC3"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (/) Move the other release artifacts from the staging spot to the dist spot
in SVN: {{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (/) Release staging repository at {{https://repository.apache.org/}}
- (/) 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 the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (/) Copy the "current" release to a versioned release {{svn copy -m "Current
UIMAJ release is 3.3.0"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0}}
- (/) Copy the versioned release to the archive spot already: {{svn copy -m
"Archiving UIMAJ 3.3.0 documentation"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0}}
- (/) Delete the previous version documentation: {{svn rm -m "Deleting
documentation for previous release"
https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0}}
- (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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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
- (/) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper ver
[jira] [Updated] (UIMA-6395) Apache UIMA Java SDK 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6395:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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
- (/) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (/) 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
- (/) 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!)
*Vote*
- (/) Call for a vote including URLs for
- (/) 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)
*Publish release*
- (/) Copy existing Eclipse update site to the archive spot: {{svn copy -m
"create eclipse plugin archive for uimaj-3.0.0-3.2.0"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0}}
- (/) Remove old Eclipse update site: {{svn rm -m "Removing previous UIMAJ
update site to make space for new one"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (/) Move new Eclipse update site from the staging to the release spot: {{svn
mv -m "Installing UIMAJ 3.3.0 update site from accepted RC3"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (/) Move the other release artifacts from the staging spot to the dist spot
in SVN: {{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (/) Release staging repository at {{https://repository.apache.org/}}
- (/) 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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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
- (/) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (/) 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
- (/) Copy the update site to a subdirectory of the release staging s
[jira] [Updated] (UIMA-6395) Apache UIMA Java SDK 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6395:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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
- (/) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (/) 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
- (/) 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!)
*Vote*
- (/) Call for a vote including URLs for
- (/) 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)
*Publish release*
- (/) Copy existing Eclipse update site to the archive spot: {{svn copy -m
"create eclipse plugin archive for uimaj-3.0.0-3.2.0"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0}}
- (/) Remove old Eclipse update site: {{svn rm -m "Removing previous UIMAJ
update site to make space for new one"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (/) Move new Eclipse update site from the staging to the release spot: {{svn
mv -m "Installing UIMAJ 3.3.0 update site from accepted RC3"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (/) Move the other release artifacts from the staging spot to the dist spot
in SVN: {{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (/) Release staging repository at {{https://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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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
- (/) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (/) 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
- (/) Copy the update site to a subdirectory of the release staging s
[jira] [Updated] (UIMA-6395) Apache UIMA Java SDK 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6395:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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
- (/) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (/) 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
- (/) 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!)
*Vote*
- (/) Call for a vote including URLs for
- (/) 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)
*Publish release*
- (/) Copy existing Eclipse update site to the archive spot: {{svn copy -m
"create eclipse plugin archive for uimaj-3.0.0-3.2.0"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0}}
- (/) Remove old Eclipse update site: {{svn rm -m "Removing previous UIMAJ
update site to make space for new one"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (/) Move new Eclipse update site from the staging to the release spot: {{svn
mv -m "Installing UIMAJ 3.3.0 update site from accepted RC3"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (/) Move the other release artifacts from the staging spot to the dist spot
in SVN: {{svn mv -m "Installing UIMAJ 3.3.0 final to release spot"
https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3
https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0}}
- (x) Release staging repository at {{https://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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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
- (/) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (/) 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
- (/) Copy the update site to a subdirectory of the release staging s
[jira] [Updated] (UIMA-6395) Apache UIMA Java SDK 3.3.0 release
[
https://issues.apache.org/jira/browse/UIMA-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6395:
-
Description:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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
- (/) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (/) 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
- (/) 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!)
*Vote*
- (/) Call for a vote including URLs for
- (/) 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)
*Publish release*
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (/) Copy existing Eclipse update site to the archive spot {{svn copy -m
"create eclipse plugin archive for uimaj-3.0.0-3.2.0"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0}}
- (x) Delete existing Eclipse update site {{svn delete -m "reset main Eclipse
update subsite for uimaj - delete old one"
https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}}
- (x) FIXME 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:
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} 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
- (/) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Set {{dropPrevVersions}} to {{true}} in the {{uimaj-eclipse-update-site}}
POM
*Release build*
- (/) Clean local m2 repository
- (/) Do a test build locally with {{-Papache-release}}
- (/) Check the issues report in {{issuesFixed}} if it looks ok
- (/) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
- (/) Build the Eclipse update site using {{mvn -f
uimaj-eclipse-update-site/pom.xml clean install -Papache-release}}
*Stage release candidate*
- (/) 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
- (/) 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!)
*Vote*
- (/) Call for a vote including URLs for
- (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)
*Publish release*
- (x) Copy the release artifacts from the staging s
[jira] [Created] (UIMA-6444) Automatically sign Eclipse plugins during release builds
Richard Eckart de Castilho created UIMA-6444: Summary: Automatically sign Eclipse plugins during release builds Key: UIMA-6444 URL: https://issues.apache.org/jira/browse/UIMA-6444 Project: UIMA Issue Type: Improvement Reporter: Richard Eckart de Castilho Assignee: Richard Eckart de Castilho Fix For: 3.4.0SDK Currently, we do not sign the Eclipse plugins because it is extra effort and the old way of using the Symantec Service are gone anyway. There is a new jarsigning approach which could be used. Alternatively, it is meanwhile possible to embed PGP signatures in P2 repositories. Let's see which of these options are viable for us. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (UIMA-5583) create new webpage documenting Symantec code signing for Eclipse Plugins
[ https://issues.apache.org/jira/browse/UIMA-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5583. -- Resolution: Won't Fix > create new webpage documenting Symantec code signing for Eclipse Plugins > > > Key: UIMA-5583 > URL: https://issues.apache.org/jira/browse/UIMA-5583 > Project: UIMA > Issue Type: Task > Components: Build, Packaging and Test, Website >Reporter: Marshall Schor >Priority: Minor > > Do a "dev" page documenting the Eclipse Plugin release process with code > signing. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (UIMA-5583) create new webpage documenting Symantec code signing for Eclipse Plugins
[ https://issues.apache.org/jira/browse/UIMA-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17533661#comment-17533661 ] Richard Eckart de Castilho commented on UIMA-5583: -- The Symantic Service is no more. There is a replacement service though. The alternative could be using PGP signatures for the Eclipse plugins. In both cases, hopefully we can integrate it properly into the Maven build such that extra manual steps and related documentation can be avoided. > create new webpage documenting Symantec code signing for Eclipse Plugins > > > Key: UIMA-5583 > URL: https://issues.apache.org/jira/browse/UIMA-5583 > Project: UIMA > Issue Type: Task > Components: Build, Packaging and Test, Website >Reporter: Marshall Schor >Priority: Minor > > Do a "dev" page documenting the Eclipse Plugin release process with code > signing. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (UIMA-6443) Fresh Eclipse update site for every release
[ https://issues.apache.org/jira/browse/UIMA-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531733#comment-17531733 ] Richard Eckart de Castilho commented on UIMA-6443: -- Related discussions in trying to get this fly with Tycho * https://github.com/eclipse/tycho/discussions/931 * https://github.com/eclipse/tycho/discussions/925 > Fresh Eclipse update site for every release > --- > > Key: UIMA-6443 > URL: https://issues.apache.org/jira/browse/UIMA-6443 > Project: UIMA > Issue Type: Improvement > Components: Build, Packaging and Test >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.4.0SDK > > > we have recently been reminded that cleaning up old releases from our website > would be a good thing. > https://issues.apache.org/jira/browse/UIMA-6427 > I have done that for the source/binary releases, but the question how to > handle the Eclipse udpate sites is still somewhat open. > It seems that currently, our Eclipse update sites contain multiple releases. > I.e. whenever we do a new release of the UIMA > Java SDK or UIMA Ruta or such, the existing update site is checked out from > SVN, the new release is added to it, and then > the updated site is committed back. > When I speak of "update site" in this mail, I actually mean the "sub-sites" > we maintain for uimaj, ruta, uima-as, etc. and > *not* the generic top-level "composite update site" that is usually not > touched at all during releases. > We have a process described on the website to regularly "archive" update > sites and start them freshly: > https://uima.apache.org/dev-eclipse-plugin-archiving > But this is something raising the question of: when should we "archive" the > update site? > I believe things would be cleaner if we didn't update the update sites at all > but instead *always* archived the > previous update site and created a fresh update site with every release. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Work started] (UIMA-6443) Fresh Eclipse update site for every release
[ https://issues.apache.org/jira/browse/UIMA-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-6443 started by Richard Eckart de Castilho. > Fresh Eclipse update site for every release > --- > > Key: UIMA-6443 > URL: https://issues.apache.org/jira/browse/UIMA-6443 > Project: UIMA > Issue Type: Improvement > Components: Build, Packaging and Test >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.4.0SDK > > > we have recently been reminded that cleaning up old releases from our website > would be a good thing. > https://issues.apache.org/jira/browse/UIMA-6427 > I have done that for the source/binary releases, but the question how to > handle the Eclipse udpate sites is still somewhat open. > It seems that currently, our Eclipse update sites contain multiple releases. > I.e. whenever we do a new release of the UIMA > Java SDK or UIMA Ruta or such, the existing update site is checked out from > SVN, the new release is added to it, and then > the updated site is committed back. > When I speak of "update site" in this mail, I actually mean the "sub-sites" > we maintain for uimaj, ruta, uima-as, etc. and > *not* the generic top-level "composite update site" that is usually not > touched at all during releases. > We have a process described on the website to regularly "archive" update > sites and start them freshly: > https://uima.apache.org/dev-eclipse-plugin-archiving > But this is something raising the question of: when should we "archive" the > update site? > I believe things would be cleaner if we didn't update the update sites at all > but instead *always* archived the > previous update site and created a fresh update site with every release. -- This message was sent by Atlassian Jira (v8.20.7#820007)
