You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Michael McCandless (Created) (JIRA)" <ji...@apache.org> on 2011/10/20 14:37:10 UTC
[jira] [Created] (TIKA-757) Address TODOs when we upgrade to next
POI release (3.8 beta 5)
Address TODOs when we upgrade to next POI release (3.8 beta 5)
--------------------------------------------------------------
Key: TIKA-757
URL: https://issues.apache.org/jira/browse/TIKA-757
Project: Tika
Issue Type: Improvement
Reporter: Michael McCandless
Fix For: 1.0
I'm opening a blanket issue to remind us all to address the TODOs in the sources for when we upgrade to the next POI.
I think this (a single blanket issue) is better than keeping separate issues open even though they are technically fixed?
For example, I've committed TIKA-753 (speedups for embedded office docs), yet it included some TODOs for further speedups possible once we upgrade POI. Rather than keeping TIKA-753 (and others like it) open, I think we should resolve them and let this issue cover all the TODOs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TIKA-757) Address TODOs when we upgrade to next
POI release (3.8 beta 5)
Posted by "Chris A. Mattmann (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated TIKA-757:
-----------------------------------
Fix Version/s: (was: 1.0)
1.1
- push out to 1.1: prep for 1.0.
> Address TODOs when we upgrade to next POI release (3.8 beta 5)
> --------------------------------------------------------------
>
> Key: TIKA-757
> URL: https://issues.apache.org/jira/browse/TIKA-757
> Project: Tika
> Issue Type: Improvement
> Reporter: Michael McCandless
> Fix For: 1.1
>
>
> I'm opening a blanket issue to remind us all to address the TODOs in the sources for when we upgrade to the next POI.
> I think this (a single blanket issue) is better than keeping separate issues open even though they are technically fixed?
> For example, I've committed TIKA-753 (speedups for embedded office docs), yet it included some TODOs for further speedups possible once we upgrade POI. Rather than keeping TIKA-753 (and others like it) open, I think we should resolve them and let this issue cover all the TODOs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TIKA-757) Address TODOs when we upgrade to next
POI release (3.8 beta 5)
Posted by "Nick Burch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Burch resolved TIKA-757.
-----------------------------
Resolution: Fixed
Fix Version/s: (was: 1.3)
1.2
I'm going to mark this as closed, as we have solved all but one TODO (around XSLF), and that probably warrants it's own jira issue.
> Address TODOs when we upgrade to next POI release (3.8 beta 5)
> --------------------------------------------------------------
>
> Key: TIKA-757
> URL: https://issues.apache.org/jira/browse/TIKA-757
> Project: Tika
> Issue Type: Improvement
> Reporter: Michael McCandless
> Fix For: 1.2
>
>
> I'm opening a blanket issue to remind us all to address the TODOs in the sources for when we upgrade to the next POI.
> I think this (a single blanket issue) is better than keeping separate issues open even though they are technically fixed?
> For example, I've committed TIKA-753 (speedups for embedded office docs), yet it included some TODOs for further speedups possible once we upgrade POI. Rather than keeping TIKA-753 (and others like it) open, I think we should resolve them and let this issue cover all the TODOs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TIKA-757) Address TODOs when we upgrade to next
POI release (3.8 beta 5)
Posted by "Chris A. Mattmann (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated TIKA-757:
-----------------------------------
Fix Version/s: (was: 1.1)
1.2
- push out to 1.2
> Address TODOs when we upgrade to next POI release (3.8 beta 5)
> --------------------------------------------------------------
>
> Key: TIKA-757
> URL: https://issues.apache.org/jira/browse/TIKA-757
> Project: Tika
> Issue Type: Improvement
> Reporter: Michael McCandless
> Fix For: 1.2
>
>
> I'm opening a blanket issue to remind us all to address the TODOs in the sources for when we upgrade to the next POI.
> I think this (a single blanket issue) is better than keeping separate issues open even though they are technically fixed?
> For example, I've committed TIKA-753 (speedups for embedded office docs), yet it included some TODOs for further speedups possible once we upgrade POI. Rather than keeping TIKA-753 (and others like it) open, I think we should resolve them and let this issue cover all the TODOs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TIKA-757) Address TODOs when we upgrade to next
POI release (3.8 beta 5)
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated TIKA-757:
-----------------------------------
- push to 1.3
> Address TODOs when we upgrade to next POI release (3.8 beta 5)
> --------------------------------------------------------------
>
> Key: TIKA-757
> URL: https://issues.apache.org/jira/browse/TIKA-757
> Project: Tika
> Issue Type: Improvement
> Reporter: Michael McCandless
> Fix For: 1.3
>
>
> I'm opening a blanket issue to remind us all to address the TODOs in the sources for when we upgrade to the next POI.
> I think this (a single blanket issue) is better than keeping separate issues open even though they are technically fixed?
> For example, I've committed TIKA-753 (speedups for embedded office docs), yet it included some TODOs for further speedups possible once we upgrade POI. Rather than keeping TIKA-753 (and others like it) open, I think we should resolve them and let this issue cover all the TODOs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TIKA-757) Address TODOs when we upgrade to next
POI release (3.8 beta 5)
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated TIKA-757:
-----------------------------------
Fix Version/s: (was: 1.2)
1.3
- push to 1.3
> Address TODOs when we upgrade to next POI release (3.8 beta 5)
> --------------------------------------------------------------
>
> Key: TIKA-757
> URL: https://issues.apache.org/jira/browse/TIKA-757
> Project: Tika
> Issue Type: Improvement
> Reporter: Michael McCandless
> Fix For: 1.3
>
>
> I'm opening a blanket issue to remind us all to address the TODOs in the sources for when we upgrade to the next POI.
> I think this (a single blanket issue) is better than keeping separate issues open even though they are technically fixed?
> For example, I've committed TIKA-753 (speedups for embedded office docs), yet it included some TODOs for further speedups possible once we upgrade POI. Rather than keeping TIKA-753 (and others like it) open, I think we should resolve them and let this issue cover all the TODOs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TIKA-757) Address TODOs when we upgrade to next
POI release (3.8 beta 5)
Posted by "Nick Burch (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172974#comment-13172974 ]
Nick Burch commented on TIKA-757:
---------------------------------
I believe that as of r1221115 most of these are now tackled, just a couple of TODOs remain
> Address TODOs when we upgrade to next POI release (3.8 beta 5)
> --------------------------------------------------------------
>
> Key: TIKA-757
> URL: https://issues.apache.org/jira/browse/TIKA-757
> Project: Tika
> Issue Type: Improvement
> Reporter: Michael McCandless
> Fix For: 1.1
>
>
> I'm opening a blanket issue to remind us all to address the TODOs in the sources for when we upgrade to the next POI.
> I think this (a single blanket issue) is better than keeping separate issues open even though they are technically fixed?
> For example, I've committed TIKA-753 (speedups for embedded office docs), yet it included some TODOs for further speedups possible once we upgrade POI. Rather than keeping TIKA-753 (and others like it) open, I think we should resolve them and let this issue cover all the TODOs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira