-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this project still maintained? #100
Comments
Looking for the same answer: is this project still maintained? @sandeepk-veritas did you find out anything in the last few months? |
@luicir, unfortunately no response here. I can see that owner of this project is Richard Johnson (rjohnsondev). Let's see if he responds to this query. @rjohnsondev, can you please make available new version if things are found to be stable? |
hey guys - unfortunately I don't have much time to work on this these days. With regards to publishing a new version and tika integration - this project kind of pre-dates the self-published approach that in now in place, and sadly uses a protected name space. This means it needs approval by exception to be updated in maven by people more important than I. I'm happy to kick the process off if people find the current HEAD stable however, and we can see what happens. I'll even update the name space if that helps, but I assume this will probably require someone to do the needful on the Tika end as well. So: let me know if you reckon current git version is working enough to publish |
Hi, we are also wondering if there will be a new public release, it seems there are quite a few changes since 0.9.4 (the last published version I can find). |
Hi Owner of repo any update about the new version? |
I can see that there were many PRs that have been merged in last few years. But there is no new publicly released version of this since 2016, so I would like to know if this project is still maintained and any plans for new release?
We make use of Tika which internally uses this module. Scanners are detecting this module as EOL as it has been 6+ years since last release.
The text was updated successfully, but these errors were encountered: