Hi,
On Fri, Mar 27, 2009 at 6:43 PM, Sami Siren wrote:
> In general sounds good to me. I am not familiar with the merge tracking
> feature, does it bring some new requirements for people using/testing the
> branch?
No, the merge tracking stuff only appears as an extra svn property
(svn:mergeinfo
Hi there,
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 so
Jukka Zitting wrote:
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
t
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
