Hi,

In TIKA-204 I'm about to start using the new commons-compress
component for better support for more compression and packaging
formats.

However, commons-compress is not yet released, so I can't yet add the
dependency in trunk without requiring everyone to build
commons-compress locally before building Tika.

So, to avoid breaking the trunk while still being able to proceed in
adding commons-compress features based on the current 1.0-SNAPSHOT,
I'd like to create a TIKA-204 development branch in svn. This branch
would be used only for TIKA-204 changes, and would be merged back to
trunk as soon as commons-compress 1.0 is out. The branch would use the
merge tracking feature in Subversion 1.5.

Any objections to this plan?

BR,

Jukka Zitting

Reply via email to