ctubbsii commented on issue #1065: map reduce failed because of commons config 
version in 1.9.3-rc2
URL: https://github.com/apache/accumulo/issues/1065#issuecomment-478666639
 
 
   > I still don't fully understand what the motivation for moving from ver 1.6 
to 1.10 was. It seems like it would be fine to leave it at 1.6, that is just 
the minimum version we support and build against. A user can always bump their 
runtime version to 1.10 if we build against 1.6.
   
   If we only produced source code, binding to the oldest supported API version 
would work fine... except that:
   
   1. commons-configuration doesn't necessarily have API guarantees, if we bind 
to the older version, there's no guarantee it will work with the newer versions 
or vice-versa,
   2. the newer versions [fix lots of 
bugs](https://commons.apache.org/proper/commons-configuration/changes-report.html#a1.10),
   3. we're not just releasing the source, we're also including the 
commons-configuration jar in our "convenience binary" tarball assembly.
   
   Because of 1, we have to do our due diligence to check that it will work 
with regardless of which we choose. Because of 2, we'd want to upgrade to 
ensure users aren't set up for failure, because of being forced to use an 
older, buggy version, because of possible incompatibilities with a newer 
versions. Because of 3, we have to be careful not to set users up for failure 
by shipping a known buggy version in our own binary assembly that they're 
likely to use.
   
   All that said, I do not care if we revert #659 or apply the cast workaround 
to bind to the correct method. Both solutions seem to work fine. I do have a 
very slight preference towards keeping the commons-configuration with fewer 
known bugs, but I'd settle for either solution.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to