reckart opened a new pull request, #295:
URL: https://github.com/apache/uima-uimaj/pull/295
**What's in the PR**
* Unprotect main-v2
**Automatic testing**
* [ ] PR adds/updates unit tests
**Documentation**
* [ ] PR adds/updates documentation
**Organizational**
reckart closed issue #289: Porting file-handling enhancements from main
URL: https://github.com/apache/uima-uimaj/issues/289
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To
reckart merged PR #294:
URL: https://github.com/apache/uima-uimaj/pull/294
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@uima.apache.o
reckart commented on PR #294:
URL: https://github.com/apache/uima-uimaj/pull/294#issuecomment-1401489275
This time the build went through :)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the sp
reckart commented on PR #294:
URL: https://github.com/apache/uima-uimaj/pull/294#issuecomment-1401464667
Thx. For some reason the build failed - I have triggered another build -
let's see if that goes through.
--
This is an automated message from the Apache Git Service.
To respond to the
bdeboe commented on issue #289:
URL: https://github.com/apache/uima-uimaj/issues/289#issuecomment-1400832777
Perhaps a little crude, but the easy way out for v2 is now in PR #294
> * [UIMA Log4jLogger_impl not compatible with log4j 2.18.0+
#267](https://github.com/apache/uima-uimaj/i
bdeboe opened a new pull request, #294:
URL: https://github.com/apache/uima-uimaj/pull/294
This change introduces file-handling enhancements from apache/uima-uimaj#209
and apache/uima-uimaj#211 to the main-v2 branch, including the fix addressing
CVE-2022-32287.
This meant porting the
reckart merged PR #290:
URL: https://github.com/apache/uima-uimaj/pull/290
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@uima.apache.o
reckart opened a new pull request, #293:
URL: https://github.com/apache/uima-uimaj/pull/293
**What's in the PR**
- run SerRef tests using a content comparison
**How to test manually**
* No specific test procedure
**Automatic testing**
* [x] PR adds/updates unit tests
reckart opened a new pull request, #291:
URL: https://github.com/apache/uima-uimaj/pull/291
**What's in the PR**
- Fix stream characteristics when using select on array or list
**How to test manually**
* See issue description
**Automatic testing**
* [ ] PR adds/updates
reckart commented on issue #289:
URL: https://github.com/apache/uima-uimaj/issues/289#issuecomment-1400427782
This issue contains the release checklist for UIMA 2.11.0 in case you are
interested:
https://issues.apache.org/jira/browse/UIMA-6328?jql=project%20%3D%20UIMA%20AND%20text%20~%20rel
[
https://issues.apache.org/jira/browse/UIMA-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6444:
-
Fix Version/s: 3.4.1SDK
(was: 3.4.0SDK)
> Automatic
reckart commented on issue #289:
URL: https://github.com/apache/uima-uimaj/issues/289#issuecomment-1400435657
Also, there might be a few additional issues to be backported in case
somebody wants to resurrect v2, e.g.
* https://github.com/apache/uima-uimaj/issues/267
* https://gith
reckart commented on issue #289:
URL: https://github.com/apache/uima-uimaj/issues/289#issuecomment-1400423264
> Again, we're happy to contribute to the actual bugfix, but don't have the
experience for driving a full release, I'm afraid
The fix is trivial, but the v2 release would
bdeboe commented on issue #289:
URL: https://github.com/apache/uima-uimaj/issues/289#issuecomment-1400393808
are there any UIMA committers that also work on / with Apache cTAKES? cTAKES
still uses UIMA v2 and I imagine converting all of that to use UIMA v3 would be
a very significant projec
[
https://issues.apache.org/jira/browse/UIMA-6442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6442:
-
Fix Version/s: 3.4.1SDK
(was: 3.4.0SDK)
> Avoid art
reckart commented on issue #289:
URL: https://github.com/apache/uima-uimaj/issues/289#issuecomment-1400403811
> I imagine converting all of that to use UIMA v3 would be a very
significant project.
Actually, converting a project from v2 to v3 shouldn't be too much effort.
The main eff
reckart commented on issue #289:
URL: https://github.com/apache/uima-uimaj/issues/289#issuecomment-1400400769
> are there any UIMA committers that also work on / with Apache cTAKES?
Not that I am aware of. Personally, I do occasionally have a look at cTAKES
and try providing helpful
reckart opened a new pull request, #290:
URL: https://github.com/apache/uima-uimaj/pull/290
**What's in the PR**
- parent-pom 16-SNAPSHOT -> 16
**How to test manually**
* No specific test procedure
**Automatic testing**
* [ ] PR adds/updates unit tests
**Document
[
https://issues.apache.org/jira/browse/UIMA-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6468:
-
Fix Version/s: 3.4.1SDK
(was: 3.4.0SDK)
> Problem w
[
https://issues.apache.org/jira/browse/UIMA-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6478.
--
Fix Version/s: (was: 3.4.0SDK)
Resolution: Not A Problem
> Ma
[
https://issues.apache.org/jira/browse/UIMA-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679776#comment-17679776
]
Richard Eckart de Castilho commented on UIMA-6486:
--
There are no plans to
reckart commented on issue #289:
URL: https://github.com/apache/uima-uimaj/issues/289#issuecomment-1400278890
I'll be happy to vote on a release, but I do not have the spare resources to
run another release of the v2 branch.
So if anybody wants to do that and take over responsibility
bdeboe opened a new issue, #289:
URL: https://github.com/apache/uima-uimaj/issues/289
Reposting [UIMA-6486](https://issues.apache.org/jira/browse/UIMA-6486) (JIRA
is no longer used)
> Hi,
>
> we distribute a custom annotator built on UIMA v2, which is affected by
https://nvd.
[
https://issues.apache.org/jira/browse/UIMA-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679777#comment-17679777
]
Benjamin De Boe commented on UIMA-6486:
---
It seems this was addressed for v3.3.* thro
[
https://issues.apache.org/jira/browse/UIMA-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6486.
--
Resolution: Abandoned
Marking issue as abandoned as Jira is no longer us
[
https://issues.apache.org/jira/browse/UIMA-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho reassigned UIMA-6486:
Assignee: Richard Eckart de Castilho
> Fix for FileUtil vulnerabili
Benjamin De Boe created UIMA-6486:
-
Summary: Fix for FileUtil vulnerability in UIMA 2.*?
Key: UIMA-6486
URL: https://issues.apache.org/jira/browse/UIMA-6486
Project: UIMA
Issue Type: Bug
reckart opened a new issue, #288:
URL: https://github.com/apache/uima-uimaj/issues/288
**Preparations**
- [ ] Create release issue and release preparation branch
- [ ] Update README.md file
- [ ] Update RELEASE_NOTES.md file
- [ ] Check the LICENSE and NOTICE files for the bin
reckart merged PR #287:
URL: https://github.com/apache/uima-uimaj/pull/287
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@uima.apache.o
30 matches
Mail list logo
