Hi All: After the last round of discussion WRT generics, a 2.0, version, and the new BM encoder, it seems the consensus is:
- Release a version based on trunk. Trunk requires Java 5 and includes the new BM encoder. - Revert the trunk changes that break binary compatibility, specifically, based on Clirr: Severity Message Class Method / Field Error Method 'public StringEncoderComparator()' has been removed org.apache.commons.codec.StringEncoderComparator public StringEncoderComparator() Error Method 'public boolean isArrayByteBase64(byte[])' has been removed org.apache.commons.codec.binary.Base64 public boolean isArrayByteBase64(byte[]) Error Class org.apache.commons.codec.language.Caverphone removed org.apache.commons.codec.language.Caverphone Error Method 'public int getMaxLength()' has been removed org.apache.commons.codec.language.Soundex public int getMaxLength() Error Method 'public void setMaxLength(int)' has been removed org.apache.commons.codec.language.Soundex public void setMaxLength(int) Error Field charset is now final org.apache.commons.codec.net.URLCodec charset Error Method 'public java.lang.String getEncoding()' has been removed org.apache.commons.codec.net.URLCodec public java.lang.String getEncoding() - Continue the generics discussion toward a major release which would likely require a package name change. Question: Because the code now requires Java 5, should the new version be 1.6 or 2.0? 1.6 feels right because we are adding an encoder. The only reason now for a 2.0 label is because we are using Java 5. Thoughts? Thank you, Gary -- http://garygregory.wordpress.com/ http://garygregory.com/ http://people.apache.org/~ggregory/ http://twitter.com/GaryGregory
