If the API is not binary compatible between 1.0 and the next release, then
you must change the package name (imaging -> imaging2) and Maven artifact
ID. So choose wisely when to do your API rework ;-)

Gary

On Wed, Nov 19, 2014 at 3:11 AM, Damjan Jovanovic <[email protected]> wrote:

> The completeness and correctness ranges from feature to feature and
> file format to file format, eg. I wouldn't recommend it for JPEG
> images (as opposed to their metadata):
> http://commons.apache.org/proper/commons-imaging/formatsupport.html
>
> You can look through the issues to see what is outstanding/wrong.
>
> I wanted to make major API changes before the 1.0 release, to improve
> reading multiple images, better generic metadata handling, etc. But I
> wonder if that's better done in version 2.0?
>
> Damjan
>
>
> On Tue, Nov 18, 2014 at 9:36 PM, Mickley, Joshua R (Genworth)
> <[email protected]> wrote:
> > Greetings All,
> >
> > I am evaluating the use of Commons Imaging for a project involving image
> conversion and manipulation.
> >
> > My question is around a timeline for an official release of Commons
> Imaging and suitability for use in a Production environment.
> >
> > I am currently using the SNAPSHOT version and am curious what bits of
> functionality are needed prior to releasing the code.  The unit testing I
> have achieved to date gives me a good impression but I wanted to inquire
> and gain some additional insight.
> >
> > Let me know if there are any specific areas where I can help contribute.
> >
> > Thanks!
> >   -Josh
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>


-- 
E-Mail: [email protected] | [email protected]
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Reply via email to