[jira] [Commented] (TIKA-1601) Integrate Jackcess to handle MSAccess files

2015-06-29 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/TIKA-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14606832#comment-14606832
 ] 

Hudson commented on TIKA-1601:
--

SUCCESS: Integrated in tika-trunk-jdk1.7 #774 (See 
[https://builds.apache.org/job/tika-trunk-jdk1.7/774/])
TIKA-1601: integrate Jackcess to parse MSAccess files (tallison: 
http://svn.apache.org/viewvc/tika/trunk/?view=revrev=1688337)
* /tika/trunk/CHANGES.txt
* /tika/trunk/tika-bundle/pom.xml
* /tika/trunk/tika-parsers/pom.xml
* 
/tika/trunk/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/JackcessExtractor.java
* 
/tika/trunk/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/JackcessParser.java
* 
/tika/trunk/tika-parsers/src/main/resources/META-INF/services/org.apache.tika.parser.Parser
* 
/tika/trunk/tika-parsers/src/test/java/org/apache/tika/parser/microsoft/JackcessParserTest.java
* /tika/trunk/tika-parsers/src/test/resources/test-documents/testAccess2.accdb
* 
/tika/trunk/tika-parsers/src/test/resources/test-documents/testAccess2_2000.mdb
* 
/tika/trunk/tika-parsers/src/test/resources/test-documents/testAccess2_2002-2003.mdb
* /tika/trunk/tika-server/pom.xml


 Integrate Jackcess to handle MSAccess files
 ---

 Key: TIKA-1601
 URL: https://issues.apache.org/jira/browse/TIKA-1601
 Project: Tika
  Issue Type: Improvement
Reporter: Tim Allison
 Attachments: jackcess_nocommit_v1.patch, testAccess2.zip


 Recently, James Ahlborn, the current maintainer of 
 [Jackcess|http://jackcess.sourceforge.net/], kindly agreed to relicense 
 Jackcess to Apache 2.0.  [~boneill], the CTO at [Health Market Science, a 
 LexisNexis® Company|https://www.healthmarketscience.com/], also agreed with 
 this relicensing and led the charge to obtain all necessary corporate 
 approval to deliver a 
 [CCLA|https://www.apache.org/licenses/cla-corporate.txt] for Jackcess to 
 Apache.  As anyone who has tried to get corporate approval for anything 
 knows, this can sometimes require not a small bit of effort.
 If I may speak on behalf of Tika and the larger Apache community, I offer a 
 sincere thanks to James, Brian and the other developers and contributors to 
 Jackcess!!!
 Once the licensing info has been changed in Jackcess and the new release is 
 available in maven, we can integrate Jackcess into Tika and add a capability 
 to process MSAccess.
 As a side note, I reached out to the developers and contributors to determine 
 if there were any objections.  I couldn't find addresses for everyone, and 
 not everyone replied, but those who did offered their support to this move. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (TIKA-1601) Integrate Jackcess to handle MSAccess files

2015-05-12 Thread Tim Allison (JIRA)

[ 
https://issues.apache.org/jira/browse/TIKA-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540181#comment-14540181
 ] 

Tim Allison commented on TIKA-1601:
---

Hi [~lfcnassif], have you had a chance to work on this at all?  Let me know if 
a test file or two would be of use.  Thank you!

 Integrate Jackcess to handle MSAccess files
 ---

 Key: TIKA-1601
 URL: https://issues.apache.org/jira/browse/TIKA-1601
 Project: Tika
  Issue Type: Improvement
Reporter: Tim Allison

 Recently, James Ahlborn, the current maintainer of 
 [Jackcess|http://jackcess.sourceforge.net/], kindly agreed to relicense 
 Jackcess to Apache 2.0.  [~boneill], the CTO at [Health Market Science, a 
 LexisNexis® Company|https://www.healthmarketscience.com/], also agreed with 
 this relicensing and led the charge to obtain all necessary corporate 
 approval to deliver a 
 [CCLA|https://www.apache.org/licenses/cla-corporate.txt] for Jackcess to 
 Apache.  As anyone who has tried to get corporate approval for anything 
 knows, this can sometimes require not a small bit of effort.
 If I may speak on behalf of Tika and the larger Apache community, I offer a 
 sincere thanks to James, Brian and the other developers and contributors to 
 Jackcess!!!
 Once the licensing info has been changed in Jackcess and the new release is 
 available in maven, we can integrate Jackcess into Tika and add a capability 
 to process MSAccess.
 As a side note, I reached out to the developers and contributors to determine 
 if there were any objections.  I couldn't find addresses for everyone, and 
 not everyone replied, but those who did offered their support to this move. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (TIKA-1601) Integrate Jackcess to handle MSAccess files

2015-04-21 Thread Luis Filipe Nassif (JIRA)

[ 
https://issues.apache.org/jira/browse/TIKA-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14505377#comment-14505377
 ] 

Luis Filipe Nassif commented on TIKA-1601:
--

Great! Give me more 3 days to submit the patch. Do you have some Apache 2 MDB 
file for unit tests?

 Integrate Jackcess to handle MSAccess files
 ---

 Key: TIKA-1601
 URL: https://issues.apache.org/jira/browse/TIKA-1601
 Project: Tika
  Issue Type: Improvement
Reporter: Tim Allison

 Recently, James Ahlborn, the current maintainer of 
 [Jackcess|http://jackcess.sourceforge.net/], kindly agreed to relicense 
 Jackcess to Apache 2.0.  [~boneill], the CTO at [Health Market Science, a 
 LexisNexis® Company|https://www.healthmarketscience.com/], also agreed with 
 this relicensing and led the charge to obtain all necessary corporate 
 approval to deliver a 
 [CCLA|https://www.apache.org/licenses/cla-corporate.txt] for Jackcess to 
 Apache.  As anyone who has tried to get corporate approval for anything 
 knows, this can sometimes require not a small bit of effort.
 If I may speak on behalf of Tika and the larger Apache community, I offer a 
 sincere thanks to James, Brian and the other developers and contributors to 
 Jackcess!!!
 Once the licensing info has been changed in Jackcess and the new release is 
 available in maven, we can integrate Jackcess into Tika and add a capability 
 to process MSAccess.
 As a side note, I reached out to the developers and contributors to determine 
 if there were any objections.  I couldn't find addresses for everyone, and 
 not everyone replied, but those who did offered their support to this move. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (TIKA-1601) Integrate Jackcess to handle MSAccess files

2015-04-21 Thread Tim Allison (JIRA)

[ 
https://issues.apache.org/jira/browse/TIKA-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14505633#comment-14505633
 ] 

Tim Allison commented on TIKA-1601:
---

I don't. That's half the fun of a patch, right. :) On the sqlite parser, I 
tried to have a least one column for each data type, nonascii language to 
confirm no encoding problems and an embedded doc.  

Happy to generate this if it would help. Thank you, again.

 Integrate Jackcess to handle MSAccess files
 ---

 Key: TIKA-1601
 URL: https://issues.apache.org/jira/browse/TIKA-1601
 Project: Tika
  Issue Type: Improvement
Reporter: Tim Allison

 Recently, James Ahlborn, the current maintainer of 
 [Jackcess|http://jackcess.sourceforge.net/], kindly agreed to relicense 
 Jackcess to Apache 2.0.  [~boneill], the CTO at [Health Market Science, a 
 LexisNexis® Company|https://www.healthmarketscience.com/], also agreed with 
 this relicensing and led the charge to obtain all necessary corporate 
 approval to deliver a 
 [CCLA|https://www.apache.org/licenses/cla-corporate.txt] for Jackcess to 
 Apache.  As anyone who has tried to get corporate approval for anything 
 knows, this can sometimes require not a small bit of effort.
 If I may speak on behalf of Tika and the larger Apache community, I offer a 
 sincere thanks to James, Brian and the other developers and contributors to 
 Jackcess!!!
 Once the licensing info has been changed in Jackcess and the new release is 
 available in maven, we can integrate Jackcess into Tika and add a capability 
 to process MSAccess.
 As a side note, I reached out to the developers and contributors to determine 
 if there were any objections.  I couldn't find addresses for everyone, and 
 not everyone replied, but those who did offered their support to this move. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (TIKA-1601) Integrate Jackcess to handle MSAccess files

2015-04-11 Thread Tim Allison (JIRA)

[ 
https://issues.apache.org/jira/browse/TIKA-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14491093#comment-14491093
 ] 

Tim Allison commented on TIKA-1601:
---

Great! We have to wait for the change in license headers and a new release. 
Please do submit your parser whenever you have a chance, but there's no rush.  
Thank you!

 Integrate Jackcess to handle MSAccess files
 ---

 Key: TIKA-1601
 URL: https://issues.apache.org/jira/browse/TIKA-1601
 Project: Tika
  Issue Type: Improvement
Reporter: Tim Allison

 Recently, James Ahlborn, the current maintainer of 
 [Jackcess|http://jackcess.sourceforge.net/], kindly agreed to relicense 
 Jackcess to Apache 2.0.  [~boneill], the CTO at [Health Market Science, a 
 LexisNexis® Company|https://www.healthmarketscience.com/], also agreed with 
 this relicensing and led the charge to obtain all necessary corporate 
 approval to deliver a 
 [CCLA|https://www.apache.org/licenses/cla-corporate.txt] for Jackcess to 
 Apache.  As anyone who has tried to get corporate approval for anything 
 knows, this can sometimes require not a small bit of effort.
 If I may speak on behalf of Tika and the larger Apache community, I offer a 
 sincere thanks to James, Brian and the other developers and contributors to 
 Jackcess!!!
 Once the licensing info has been changed in Jackcess and the new release is 
 available in maven, we can integrate Jackcess into Tika and add a capability 
 to process MSAccess.
 As a side note, I reached out to the developers and contributors to determine 
 if there were any objections.  I couldn't find addresses for everyone, and 
 not everyone replied, but those who did offered their support to this move. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (TIKA-1601) Integrate Jackcess to handle MSAccess files

2015-04-11 Thread Luis Filipe Nassif (JIRA)

[ 
https://issues.apache.org/jira/browse/TIKA-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14491058#comment-14491058
 ] 

Luis Filipe Nassif commented on TIKA-1601:
--

Hi Tim,

I already have a parser based on jackcess. If you can wait, I can submit a 
preliminary patch next week.

 Integrate Jackcess to handle MSAccess files
 ---

 Key: TIKA-1601
 URL: https://issues.apache.org/jira/browse/TIKA-1601
 Project: Tika
  Issue Type: Improvement
Reporter: Tim Allison

 Recently, James Ahlborn, the current maintainer of 
 [Jackcess|http://jackcess.sourceforge.net/], kindly agreed to relicense 
 Jackcess to Apache 2.0.  [~boneill], the CTO at [Health Market Science, a 
 LexisNexis® Company|https://www.healthmarketscience.com/], also agreed with 
 this relicensing and led the charge to obtain all necessary corporate 
 approval to deliver a 
 [CCLA|https://www.apache.org/licenses/cla-corporate.txt] for Jackcess to 
 Apache.  As anyone who has tried to get corporate approval for anything 
 knows, this can sometimes require not a small bit of effort.
 If I may speak on behalf of Tika and the larger Apache community, I offer a 
 sincere thanks to James, Brian and the other developers and contributors to 
 Jackcess!!!
 Once the licensing info has been changed in Jackcess and the new release is 
 available in maven, we can integrate Jackcess into Tika and add a capability 
 to process MSAccess.
 As a side note, I reached out to the developers and contributors to determine 
 if there were any objections.  I couldn't find addresses for everyone, and 
 not everyone replied, but those who did offered their support to this move. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)