You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by Ken Krugler <kk...@transpac.com> on 2016/02/07 01:50:04 UTC
Tracking 2.x migration changes
Is there a document where we're tracking what (breaking) API changes are occurring in the 2.x branch, and the migration path from 1.x for Tika users?
If not, should this be a wiki page that we all edit iteratively?
Thanks,
-- Ken
--------------------------
Ken Krugler
+1 530-210-6378
http://www.scaleunlimited.com
custom big data solutions & training
Hadoop, Cascading, Cassandra & Solr
RE: Tracking 2.x migration changes
Posted by "Allison, Timothy B." <ta...@mitre.org>.
https://wiki.apache.org/tika/Tika2_0MigrationGuide
-----Original Message-----
From: Bob Paulin [mailto:bob@bobpaulin.com]
Sent: Monday, February 08, 2016 8:58 AM
To: dev@tika.apache.org
Subject: Re: Tracking 2.x migration changes
That's a good idea. I'm not aware of any breaking API changes yet but the maven/project re-org is definitely requires some coverage.
- Bob
On 2/8/2016 6:28 AM, Allison, Timothy B. wrote:
> Y, I was thinking the same thing. Let's start a wiki page, and then right before the release of 2.0, we can effectively copy and paste from that for the "Migration Guide to 2.0" to be included at the top level of the release with the CHANGES.txt file?
>
> -----Original Message-----
> From: Ken Krugler [mailto:kkrugler_lists@transpac.com]
> Sent: Saturday, February 06, 2016 7:50 PM
> To: tika-dev@lucene.apache.org
> Subject: Tracking 2.x migration changes
>
> Is there a document where we're tracking what (breaking) API changes are occurring in the 2.x branch, and the migration path from 1.x for Tika users?
>
> If not, should this be a wiki page that we all edit iteratively?
>
> Thanks,
>
> -- Ken
>
> --------------------------
> Ken Krugler
> +1 530-210-6378
> http://www.scaleunlimited.com
> custom big data solutions & training
> Hadoop, Cascading, Cassandra & Solr
>
>
Re: Tracking 2.x migration changes
Posted by Bob Paulin <bo...@bobpaulin.com>.
That's a good idea. I'm not aware of any breaking API changes yet but
the maven/project re-org is definitely requires some coverage.
- Bob
On 2/8/2016 6:28 AM, Allison, Timothy B. wrote:
> Y, I was thinking the same thing. Let's start a wiki page, and then right before the release of 2.0, we can effectively copy and paste from that for the "Migration Guide to 2.0" to be included at the top level of the release with the CHANGES.txt file?
>
> -----Original Message-----
> From: Ken Krugler [mailto:kkrugler_lists@transpac.com]
> Sent: Saturday, February 06, 2016 7:50 PM
> To: tika-dev@lucene.apache.org
> Subject: Tracking 2.x migration changes
>
> Is there a document where we're tracking what (breaking) API changes are occurring in the 2.x branch, and the migration path from 1.x for Tika users?
>
> If not, should this be a wiki page that we all edit iteratively?
>
> Thanks,
>
> -- Ken
>
> --------------------------
> Ken Krugler
> +1 530-210-6378
> http://www.scaleunlimited.com
> custom big data solutions & training
> Hadoop, Cascading, Cassandra & Solr
>
>
RE: Tracking 2.x migration changes
Posted by "Allison, Timothy B." <ta...@mitre.org>.
Y, I was thinking the same thing. Let's start a wiki page, and then right before the release of 2.0, we can effectively copy and paste from that for the "Migration Guide to 2.0" to be included at the top level of the release with the CHANGES.txt file?
-----Original Message-----
From: Ken Krugler [mailto:kkrugler_lists@transpac.com]
Sent: Saturday, February 06, 2016 7:50 PM
To: tika-dev@lucene.apache.org
Subject: Tracking 2.x migration changes
Is there a document where we're tracking what (breaking) API changes are occurring in the 2.x branch, and the migration path from 1.x for Tika users?
If not, should this be a wiki page that we all edit iteratively?
Thanks,
-- Ken
--------------------------
Ken Krugler
+1 530-210-6378
http://www.scaleunlimited.com
custom big data solutions & training
Hadoop, Cascading, Cassandra & Solr