[
https://issues.apache.org/jira/browse/IMAGING-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804600#comment-13804600
]
Matt Benson edited comment on IMAGING-120 at 10/24/13 7:43 PM:
---------------------------------------------------------------
Second patch with interface included. As you can see it's not terribly
involved. I'm not too concerned over the interface name; your suggestion would
be fine as well. Since I'm not a user of \[imaging] it won't affect me either
way. Not sure when the best time to break would be, but since we know there
are already breaking changes in 1.0 due to the package migration, it would seem
that we _know_ there is a compatibility break now, so why not do all the
breaking changes we know about together? Just my $0.02.
was (Author: mbenson):
Second patch with interface included. As you can see it's not terribly
involved. I'm not too concerned over the interface name; your suggestion would
be fine as well.
> Extract an interface from ImageFormat
> -------------------------------------
>
> Key: IMAGING-120
> URL: https://issues.apache.org/jira/browse/IMAGING-120
> Project: Commons Imaging
> Issue Type: Improvement
> Affects Versions: 0.97
> Reporter: Matt Benson
> Fix For: 1.0
>
> Attachments: IMAGING-120.patch2.txt, IMAGING-120.patch.txt
>
>
> As discussed on the dev@commons ML, this would allow users to create custom
> image formats while permitting the known image formats to be represented by
> the {{ImageFormat enum}}.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
