Great, Thank you, Tim!
Em qua., 15 de dez. de 2021 às 16:50, Tim Allison
escreveu:
> I've merged Lewis's edits to the README and added the EOL. Let's do
> what both Konstantin and Nick recommend: README, notifications to
> user/dev lists x months out and include EOL in all release messages?
>
[
https://issues.apache.org/jira/browse/TIKA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460262#comment-17460262
]
Hudson commented on TIKA-3446:
--
UNSTABLE: Integrated in Jenkins build Tika » tika-branch1x-jdk8 #153 (See
[
https://issues.apache.org/jira/browse/TIKA-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460229#comment-17460229
]
Hudson commented on TIKA-3619:
--
FAILURE: Integrated in Jenkins build Tika » tika-main-jdk8 #390 (See
[
https://issues.apache.org/jira/browse/TIKA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460222#comment-17460222
]
ASF GitHub Bot commented on TIKA-3446:
--
nddipiazza merged pull request #465:
URL:
nddipiazza merged pull request #465:
URL: https://github.com/apache/tika/pull/465
--
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:
I've merged Lewis's edits to the README and added the EOL. Let's do
what both Konstantin and Nick recommend: README, notifications to
user/dev lists x months out and include EOL in all release messages?
Please let me know/edit the README if there are other improvements we
should make.
Thank
[
https://issues.apache.org/jira/browse/TIKA-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460210#comment-17460210
]
ASF GitHub Bot commented on TIKA-3619:
--
tballison merged pull request #464:
URL:
tballison merged pull request #464:
URL: https://github.com/apache/tika/pull/464
--
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:
[
https://issues.apache.org/jira/browse/TIKA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460209#comment-17460209
]
ASF GitHub Bot commented on TIKA-3446:
--
tballison commented on pull request #465:
URL:
tballison commented on pull request #465:
URL: https://github.com/apache/tika/pull/465#issuecomment-995141124
Looks good to me. Y, go for it.
--
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
[
https://issues.apache.org/jira/browse/TIKA-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460203#comment-17460203
]
Tim Allison edited comment on TIKA-491 at 12/15/21, 7:31 PM:
-
This module in
[
https://issues.apache.org/jira/browse/TIKA-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460203#comment-17460203
]
Tim Allison commented on TIKA-491:
--
This module in Tika 2.x does distinguish between those two languages:
[
https://issues.apache.org/jira/browse/TIKA-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460180#comment-17460180
]
Tim Allison commented on TIKA-3616:
---
Thank you for looking at this carefully, [~grossws]!
> Upgrade
[
https://issues.apache.org/jira/browse/TIKA-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460168#comment-17460168
]
Konstantin Gribov commented on TIKA-3616:
-
I looked a bit how Tika and it's upstream dependencies
My +1 to EOL on September 30, 2022 with effective backport submission
freeze 3 months before that.
I think it would be better if we mention the EOL timeline at least in 3
places: in each release announcement, in README and on the site (on the
main page or in release news articles). Different
[
https://issues.apache.org/jira/browse/TIKA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460152#comment-17460152
]
ASF GitHub Bot commented on TIKA-3446:
--
nddipiazza commented on pull request #465:
URL:
nddipiazza commented on pull request #465:
URL: https://github.com/apache/tika/pull/465#issuecomment-995047236
OK @tballison got a moment for a quick review on this one? Is this OK to add
into the upcoming 1.x release?
--
This is an automated message from the Apache Git Service.
To
[
https://issues.apache.org/jira/browse/TIKA-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460150#comment-17460150
]
Tim Allison commented on TIKA-3616:
---
2.15's vulnerability seemed to require extra complexity
On Wed, 15 Dec 2021, Tim Allison wrote:
Sounds good, Nick. Unless there are objections, I'll add an EOL
September 30, 2022 for the 1.x branch on our github README and maybe our
site somewhere?
Maybe just mention it in the news section at the end any 1.x fix releases?
Nick
[
https://issues.apache.org/jira/browse/TIKA-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460140#comment-17460140
]
Dan Switzer commented on TIKA-3616:
---
Is Tika being upgraded to Log4j v2.16, since 2.15 still has a
Sounds good, Nick. Unless there are objections, I'll add an EOL
September 30, 2022 for the 1.x branch on our github README and maybe
our site somewhere?
>I'm not keen on adding new features to 1.x, as that'll only encourage
people to stick on the old one, but I wouldn't go as far as -1'ing other
Lewis John McGibbney created TIKA-3620:
--
Summary: Language detection documentation needs attention
Key: TIKA-3620
URL: https://issues.apache.org/jira/browse/TIKA-3620
Project: Tika
[
https://issues.apache.org/jira/browse/TIKA-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney reassigned TIKA-3620:
--
Assignee: Lewis John McGibbney
> Language detection documentation needs
[
https://issues.apache.org/jira/browse/TIKA-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-3241.
---
Fix Version/s: 2.0.0-ALPHA
Resolution: Fixed
Y, thanks [~lewismc]
> Clarify parser module
[
https://issues.apache.org/jira/browse/TIKA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460068#comment-17460068
]
ASF GitHub Bot commented on TIKA-3446:
--
tballison commented on pull request #465:
URL:
tballison commented on pull request #465:
URL: https://github.com/apache/tika/pull/465#issuecomment-994938829
@nddipiazza I think the goal is to keep tika-core as slim as possible, but
you can put whatever you need in tika-parsers, as long as we don't have any
conflicts.
--
This is an
[
https://issues.apache.org/jira/browse/TIKA-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460066#comment-17460066
]
Lewis John McGibbney commented on TIKA-3241:
Hi [~tallison] can this ticket be closed?
>
[
https://issues.apache.org/jira/browse/TIKA-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460065#comment-17460065
]
Lewis John McGibbney commented on TIKA-3229:
[~Simmo] are you able to reproduce this/
[
https://issues.apache.org/jira/browse/TIKA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460064#comment-17460064
]
ASF GitHub Bot commented on TIKA-3446:
--
nddipiazza commented on pull request #465:
URL:
[
https://issues.apache.org/jira/browse/TIKA-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney resolved TIKA-491.
---
Resolution: Won't Fix
Cleanup [~kkrugler] [~pandermusubi]
> Add language
nddipiazza commented on pull request #465:
URL: https://github.com/apache/tika/pull/465#issuecomment-994933278
@tballison am I OK to use stringutils3 in the 1.x branch?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
[
https://issues.apache.org/jira/browse/TIKA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460062#comment-17460062
]
ASF GitHub Bot commented on TIKA-3446:
--
nddipiazza opened a new pull request #465:
URL:
nddipiazza opened a new pull request #465:
URL: https://github.com/apache/tika/pull/465
Porting https://github.com/apache/tika/pull/461 to Tika 1.x
--
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
[
https://issues.apache.org/jira/browse/TIKA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney resolved TIKA-369.
---
Resolution: Fixed
Cleaning this one up [~kkrugler]
> Improve accuracy of language
On Wed, 15 Dec 2021, Tim Allison wrote:
I think we should keep the 1.x branch open for security upgrades for a
bit...middle of next year? I have _not_ been adding new features or
even some bug fixes to 1.x, and I encourage people to migrate to 2.x.
We've seen quite a few queries from people
[
https://issues.apache.org/jira/browse/TIKA-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1746#comment-1746
]
David Pilato commented on TIKA-3610:
That's very good. So I believe we are all set and we can close
[
https://issues.apache.org/jira/browse/TIKA-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459998#comment-17459998
]
Tim Allison edited comment on TIKA-3610 at 12/15/21, 2:37 PM:
--
Hi
[
https://issues.apache.org/jira/browse/TIKA-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459998#comment-17459998
]
Tim Allison commented on TIKA-3610:
---
Hi [~dadoonet], at the meetup, I forgot that I already added a
[
https://issues.apache.org/jira/browse/TIKA-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459931#comment-17459931
]
Subhajit Das commented on TIKA-3618:
Yes, I will check and push.
> Upgrade to log4j2 in 1.x branch
>
[
https://issues.apache.org/jira/browse/TIKA-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459917#comment-17459917
]
Tim Allison commented on TIKA-3618:
---
[~subhajitdas298] once you’ve had a chance to review branch_1x, we
It didn't take too long, and as long as the original author of the
metrics stuff in tika-server isn't too concerned about breaking
changes, let's hope for the best. Log4j 1.x is so far beyond its EOL,
it is embarrassing.
I think we should keep the 1.x branch open for security upgrades for a
Howdy,
There were some Maven Central issues in the past few days, hopefully fixed.
https://status.maven.org/#week
Thanks
Tamas
On Mon, Dec 13, 2021 at 11:18 PM Lewis John McGibbney
wrote:
> I performed another build of the tika-2.2.0-src.zip artifact which failed.
> I've captured the failure
[
https://issues.apache.org/jira/browse/TIKA-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilman Hausherr updated TIKA-3615:
--
Issue Type: Bug (was: Test)
> Missing class file while upgrade to TIka 2.1.0
>
[
https://issues.apache.org/jira/browse/TIKA-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilman Hausherr closed TIKA-3615.
-
Resolution: Not A Bug
> Missing class file while upgrade to TIka 2.1.0
>
[
https://issues.apache.org/jira/browse/TIKA-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilman Hausherr reopened TIKA-3615:
---
> Missing class file while upgrade to TIka 2.1.0
> --
[
https://issues.apache.org/jira/browse/TIKA-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilman Hausherr closed TIKA-3614.
-
Resolution: Not A Bug
I'm closing these as "not a bug" because we don't want these to appear in a
[
https://issues.apache.org/jira/browse/TIKA-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilman Hausherr reopened TIKA-3614:
---
> Trying to upgrade from 1.27 to 2.1.0
>
>
>
47 matches
Mail list logo
