The Apache Commons Imaging team is pleased to announce the release of
Apache Commons Imaging 1.0.0-alpha6.
Apache Commons Imaging (previously Sanselan) is a pure Java image library.
The 1.0.0-alpha6 release requires Java 8.
Historical list of changes:
https://commons.apache.org/proper/commons
This vote passes with the following binding +1 votes:
- Phil Steitz (psteitz)
- Henri Biestro (henrib)
- Gary Gregory (ggregory)
TY all,
Gary
On Sun, Apr 27, 2025 at 11:41 AM Gary Gregory wrote:
>
> We have fixed a few bugs and added enhancements since Apache Commons
> Imaging 1.0.0-a
My +1
Gary
On Sun, Apr 27, 2025 at 11:41 AM Gary Gregory wrote:
>
> We have fixed a few bugs and added enhancements since Apache Commons
> Imaging 1.0.0-alpha5 was released, so I would like to release Apache
> Commons Imaging 1.0.0-alpha6.
>
> There are many Javadoc warnings
[+1]
Build & tests ok; site & javadoc look good; reports check.
Nits: JIRA report has a few issues without a fix version; Jacoco/coverage is on
the low side;
Built using: mvn clean install site -s "$HOME/.m2/commons-settings.xml"
-Ddoclint=none
On: Apache Maven 3.8.6 (84538c9988a25aec085021c3
+1 to release
Checked build on openjdk 21.0.6, maven 3.9.3, ubuntu 24.10.
Verified sigs and hashes
Checked release notes, changelog, reports. Looks good.
Phil
On Sun, Apr 27, 2025 at 8:42 AM Gary Gregory wrote:
> We have fixed a few bugs and added enhancements since Apache Commons
> I
We have fixed a few bugs and added enhancements since Apache Commons
Imaging 1.0.0-alpha5 was released, so I would like to release Apache
Commons Imaging 1.0.0-alpha6.
There are many Javadoc warnings, the Javadocs are still a work in progress.
Apache Commons Imaging 1.0.0-alpha6 RC1 is available
Hi Mark,
On 26.03.2025 10:03, Mark Thomas wrote:
On 26/03/2025 08:55, libstech-auto (via GitHub) wrote:
This bot just earned themselves an ASF-wide ban from GitHub.
The ban is not restricted to the ASF: on Wednesday I reported the user
to GitHub and yesterday I received this response:
On 2
; >
> > libstech-auto opened a new pull request, #497:
> > URL: https://github.com/apache/commons-imaging/pull/497
> >
> > This PR adds a libs.tech recommendation badge to the README,
> > highlighting this project as a top choice in its category.
> >
> &g
> URL: https://github.com/apache/commons-imaging/pull/497
> >
> > This PR adds a libs.tech recommendation badge to the README,
> > highlighting this project as a top choice in its category.
> >
> > Since [**your project has been approved and
> > liste
On 26/03/2025 08:55, libstech-auto (via GitHub) wrote:
This bot just earned themselves an ASF-wide ban from GitHub.
Mark
libstech-auto opened a new pull request, #497:
URL: https://github.com/apache/commons-imaging/pull/497
This PR adds a libs.tech recommendation badge to the README
; Hi All -
>
> (First time on this mailing list)
>
> In my log files I see a lot of errors similar to what is in the
> imaging-177 issue when trying to get image metadata from a jpeg. I took a
> sample image that had the error to investigate, and found that the image
> appears to hav
Hi All -
(First time on this mailing list)
In my log files I see a lot of errors similar to what is in the imaging-177
issue when trying to get image metadata from a jpeg. I took a sample image
that had the error to investigate, and found that the image appears to have an
embedded thumbnail
I'll check it out, ty!
Gary
On Thu, Apr 18, 2024, 12:06 PM sebb wrote:
> On Thu, 18 Apr 2024 at 16:07, Gary Gregory wrote:
> >
> > The Apache Commons Imaging team is pleased to announce the release of
> > Apache Commons Imaging 1.0.0-alpha5.
> >
> > Apach
On Thu, 18 Apr 2024 at 16:07, Gary Gregory wrote:
>
> The Apache Commons Imaging team is pleased to announce the release of
> Apache Commons Imaging 1.0.0-alpha5.
>
> Apache Commons Imaging (previously Sanselan) is a pure-Java image library.
>
> The 1.0.0-alpha5 re
The Apache Commons Imaging team is pleased to announce the release of
Apache Commons Imaging 1.0.0-alpha5.
Apache Commons Imaging (previously Sanselan) is a pure-Java image library.
The 1.0.0-alpha5 release requires Java 8.
Historical list of changes:
https://commons.apache.org/proper/commons
;
> On Mon, Apr 15, 2024, 15:36 Gary Gregory wrote:
>
> > We have fixed a few bugs and added enhancements since Apache Commons
> > Imaging 1.0.0-alpha4 was released, so I would like to release Apache
> > Commons Imaging 1.0.0-alpha5.
> >
> > Apache Commons Im
My +1 [release]
Tomas Lanik
On Mon, Apr 15, 2024, 15:36 Gary Gregory wrote:
> We have fixed a few bugs and added enhancements since Apache Commons
> Imaging 1.0.0-alpha4 was released, so I would like to release Apache
> Commons Imaging 1.0.0-alpha5.
>
> Apache Commons Imaging 1
t; >> We have fixed a few bugs and added enhancements since Apache Commons
> >> Imaging 1.0.0-alpha4 was released, so I would like to release Apache
> >> Commons Imaging 1.0.0-alpha5.
> >>
> >> Apache Commons Imaging 1.0.0-alpha5 RC1 is available for revie
+1
> On Apr 15, 2024, at 1:01 PM, Bruno Kinoshita wrote:
>
> +1
>
> Thank you Gary!
>
>> On Mon, 15 Apr 2024 at 15:36, Gary Gregory wrote:
>>
>> We have fixed a few bugs and added enhancements since Apache Commons
>> Imaging 1.0.0-alpha4 was r
+1
Thank you Gary!
On Mon, 15 Apr 2024 at 15:36, Gary Gregory wrote:
> We have fixed a few bugs and added enhancements since Apache Commons
> Imaging 1.0.0-alpha4 was released, so I would like to release Apache
> Commons Imaging 1.0.0-alpha5.
>
> Apache Commons Imaging 1.0.
We have fixed a few bugs and added enhancements since Apache Commons
Imaging 1.0.0-alpha4 was released, so I would like to release Apache
Commons Imaging 1.0.0-alpha5.
Apache Commons Imaging 1.0.0-alpha5 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/imaging
The Apache Commons Imaging team is pleased to announce the release of
Apache Commons Imaging 1.0.0-alpha4.
Apache Commons Imaging (previously Sanselan) is a pure Java image library.
The 1.0.0-alpha4 release requires Java 8.
Historical list of changes:
https://commons.apache.org/proper/commons
at 6:01 PM, Tomas Lanik wrote:
> >
> > +1 for 1.0.0-alpha4
> >
> > On Sat, Mar 30, 2024 at 3:14 PM Gary Gregory wrote:
> >
> >> We have fixed a few bugs and added enhancements since Apache Commons
> >> Imaging 1.0-alpha3 was released, s
+1
> On Mar 30, 2024, at 6:01 PM, Tomas Lanik wrote:
>
> +1 for 1.0.0-alpha4
>
> On Sat, Mar 30, 2024 at 3:14 PM Gary Gregory wrote:
>
>> We have fixed a few bugs and added enhancements since Apache Commons
>> Imaging 1.0-alpha3 was released, so I would lik
+1 for 1.0.0-alpha4
On Sat, Mar 30, 2024 at 3:14 PM Gary Gregory wrote:
> We have fixed a few bugs and added enhancements since Apache Commons
> Imaging 1.0-alpha3 was released, so I would like to release Apache
> Commons Imaging 1.0.0-alpha4.
>
> Apache Commons Imaging 1.0.
My +1
Gary
On Sat, Mar 30, 2024, 10:13 AM Gary Gregory wrote:
> We have fixed a few bugs and added enhancements since Apache Commons
> Imaging 1.0-alpha3 was released, so I would like to release Apache
> Commons Imaging 1.0.0-alpha4.
>
> Apache Commons Imaging 1.0.0-alpha4 R
oks good, thanks a lot for preparing the release, Gary!
Bruno
On Sat, 30 Mar 2024 at 15:14, Gary Gregory wrote:
> We have fixed a few bugs and added enhancements since Apache Commons
> Imaging 1.0-alpha3 was released, so I would like to release Apache
> Commons Imaging 1.0.0-alpha
We have fixed a few bugs and added enhancements since Apache Commons
Imaging 1.0-alpha3 was released, so I would like to release Apache
Commons Imaging 1.0.0-alpha4.
Apache Commons Imaging 1.0.0-alpha4 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/imaging
were not fixed yet, and other bugs reported by
> users of the alpha1/2 releases that would be nice to fix before it's ready
> to be released.
>
> I think what we have in Imaging right now matches more the alpha release
> described in ASF's release policy page
> https://ww
to fix before it's ready
to be released.
I think what we have in Imaging right now matches more the alpha release
described in ASF's release policy page
https://www.apache.org/legal/release-policy.html#release-types,
> Releases that only represent a project milestone and are intend
ish from an alpha or 1.0 release?
>
> Tha ks for preparing the release!
>
> Bruno
>
> On Mon, 25 Mar 2024, 14:17 Gary Gregory, wrote:
>
> > We have fixed a few bugs and added some enhancements since Apache
> > Commons Imaging 1.0-alpha3 was released, so I would li
ase!
Bruno
On Mon, 25 Mar 2024, 14:17 Gary Gregory, wrote:
> We have fixed a few bugs and added some enhancements since Apache
> Commons Imaging 1.0-alpha3 was released, so I would like to release
> Apache Commons Imaging 1.0.0-M1.
>
> Apache Commons Imaging 1.0.0-M1 RC1 is availab
We have fixed a few bugs and added some enhancements since Apache
Commons Imaging 1.0-alpha3 was released, so I would like to release
Apache Commons Imaging 1.0.0-M1.
Apache Commons Imaging 1.0.0-M1 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0
be able to get back to this work anytime soon, so can anyone else
> fix it for me?
>
> Glavo
>
> [1]:
> https://github.com/apache/commons-imaging/pull/269#issuecomment-1381983655
>
> On Wed, Jan 3, 2024 at 5:44 AM Bruno Kinoshita
> wrote:
>
> > I don't mind
d
as soon as possible.
I won't be able to get back to this work anytime soon, so can anyone else
fix it for me?
Glavo
[1]:
https://github.com/apache/commons-imaging/pull/269#issuecomment-1381983655
On Wed, Jan 3, 2024 at 5:44 AM Bruno Kinoshita
wrote:
> I don't mind staying wit
s month, so not quite
> 1.0 but a signal that we are close.
>
> I think it's a bit premature. I think commons-imaging should not depend on
> java.desktop,
> otherwise it will be unavailable on some platforms (such as Android or
> other platforms that do not include java.des
> I plan on releasing a milestone 1.0-M1 version this month, so not quite
1.0 but a signal that we are close.
I think it's a bit premature. I think commons-imaging should not depend on
java.desktop,
otherwise it will be unavailable on some platforms (such as Android or
other platforms tha
ssing. I think the partial webp reading
> > > feature has not been released yet, but it was already merged in master.
> > >
> > > https://github.com/apache/commons-imaging/pull/254
> > >
> > > Feel free to test the latest version and prov
progress on reading webp, but it's not complete, and the
> > writing features are still missing. I think the partial webp reading
> > feature has not been released yet, but it was already merged in master.
> >
> > https://github.com/apache/commons-imaging/pull/254
>
; Hi, we made some progress on reading webp, but it's not complete, and the
> writing features are still missing. I think the partial webp reading
> feature has not been released yet, but it was already merged in master.
>
> https://github.com/apache/commons-imaging/pull/254
>
&g
"hard" to saying we'll provide allow and/or deny lists in the future.
For memory and CPU consumption issues, we want to avoid zip-bomb issues, and
that's where code inspections and fuzzing will help and has already helped.
Commons Imaging and Compress are two obvious targets
On Thu, Dec 14, 2023 at 9:31 AM Arnout Engelen wrote:
>
> Examples of what I referred to as arbitrary code execution would be
> unbounded deserialization of untrusted data (via techniques like those
> described in the motivation for
> https://docs.oracle.com/en/java/javase/17/core/serialization-f
d expect a
reasonable user to do. If we tell users that they need to check their
inputs to prevent something like this, then the natural next question is
“how?”
If I was using an imaging or compression library that told me I needed to
use an additional library to protect myself against malicious (j
On Thu, Dec 14, 2023 at 2:00 PM Elliotte Rusty Harold
wrote:
> On Thu, Dec 14, 2023 at 6:09 AM Arnout Engelen wrote:
> > * I'd say parsing/decompression/decoding should never allow malicious
> input
> > to trigger arbitrary code execution(?)
>
> Do any of these products include native libraries/
On Thu, Dec 14, 2023 at 6:09 AM Arnout Engelen wrote:
>
> Hello Commons developers,
>
> I'd like to discuss what our security ambitions are for components like
> Commons Imaging, Compress, Codec and IO:
>
> Generally for Commons, we say that unless otherwise specified
Hello.
Le jeu. 14 déc. 2023 à 12:10, Arnout Engelen a écrit :
>
> Hello Commons developers,
>
> I'd like to discuss what our security ambitions are for components like
> Commons Imaging, Compress, Codec and IO:
>
> Generally for Commons, we say that unless otherwise s
Hello Commons developers,
I'd like to discuss what our security ambitions are for components like
Commons Imaging, Compress, Codec and IO:
Generally for Commons, we say that unless otherwise specified it is up to
the user of the library to make sure any input is either trusted or
corr
Hi, we made some progress on reading webp, but it's not complete, and the
writing features are still missing. I think the partial webp reading
feature has not been released yet, but it was already merged in master.
https://github.com/apache/commons-imaging/pull/254
Feel free to test the l
Hi there,
I see on your roadmap that WEBP support is planned. Has this already been
developed in an unreleased version? When will there be another release of
the apache commons imaging project?
https://commons.apache.org/proper/commons-imaging/roadmap.html
Thanks in advance,
William
On Thu, Aug 31, 2023 at 3:26 PM Gary Gregory wrote:
>
> Why?
>
I assumed it was post 1.0. If that's not the case, then sure,
whatever. API compatibility is not promised yet.
--
Elliotte Rusty Harold
elh...@ibiblio.org
-
To
Why?
Gary
On Thu, Aug 31, 2023, 10:41 AM Elliotte Rusty Harold
wrote:
> This should be a major version bump.
>
> On Thu, Aug 31, 2023 at 1:26 PM Gary Gregory
> wrote:
> >
> > Hi All,
> >
> > I propose we drop implementating Serializable and avoid any and all
> > possible security issues in thi
I believe we haven't had a 1.0 yet, and we discussed previously about
breaking changes in the current pre 1.0 release. I think there are still
some issues that veto'ed 1.0 before that also need to be fixed, but it
shouldn't be too hard to prepare a 1.0 soon-ish.
On Thu, 31 Aug 2023 at 16:41, Ellio
This should be a major version bump.
On Thu, Aug 31, 2023 at 1:26 PM Gary Gregory wrote:
>
> Hi All,
>
> I propose we drop implementating Serializable and avoid any and all
> possible security issues in this area.
>
> Gary
--
Elliotte Rusty Harold
elh...@ibiblio.org
-
+1
On Thu, 31 Aug 2023 at 15:46, Gary Lucas wrote:
> +1 agree.
>
> On Thu, Aug 31, 2023, 9:29 AM Gary Gregory wrote:
>
> > Hi All,
> >
> > I propose we drop implementating Serializable and avoid any and all
> > possible security issues in this area.
> >
> > Gary
> >
>
Done in git master. Only 2 classes affected.
Gary
On Thu, Aug 31, 2023, 9:46 AM Gary Lucas wrote:
> +1 agree.
>
> On Thu, Aug 31, 2023, 9:29 AM Gary Gregory wrote:
>
> > Hi All,
> >
> > I propose we drop implementating Serializable and avoid any and all
> > possible security issues in this ar
+1 agree.
On Thu, Aug 31, 2023, 9:29 AM Gary Gregory wrote:
> Hi All,
>
> I propose we drop implementating Serializable and avoid any and all
> possible security issues in this area.
>
> Gary
>
On Thu, 31 Aug 2023 at 14:29, Gary Gregory wrote:
>
> Hi All,
>
> I propose we drop implementating Serializable and avoid any and all
> possible security issues in this area.
+1
It is extra work ensuring that the feature works properly let alone securely.
> Gary
---
Hello.
Le jeu. 31 août 2023 à 15:29, Gary Gregory a écrit :
>
> Hi All,
>
> I propose we drop implementating Serializable
+1
Gilles
> and avoid any and all
> possible security issues in this area.
>
> Gary
-
To unsubscribe, e
Hi All,
I propose we drop implementating Serializable and avoid any and all
possible security issues in this area.
Gary
Miguel,
Don't cut off the thread in the body of the email please.
Gary
On Wed, May 31, 2023, 01:49 Miguel Muñoz wrote:
>
> In addition to logging and swallowing the exception, this method also then
> returns null. This is also a bad practice.
>
>
>
> The caller has to check for null. One of
That whole class looks like it needs a bit of TLC (or Javadoc at least!)
On Wed, 31 May 2023 at 06:49, Miguel Muñoz wrote:
>
>
> In addition to logging and swallowing the exception, this method also then
> returns null. This is also a bad practice.
>
>
>
> The caller has to check for null. One o
In addition to logging and swallowing the exception, this method also then
returns null. This is also a bad practice.
The caller has to check for null. One of the reasons exceptions were invented
was to free the user from needing to check for null or error codes.
— Miguel
PR created: https://github.com/apache/commons-imaging/pull/294
Note that simply running 'mvn' after a clean checkout of 'master' fails on
JavaDoc generation for 'PhotometricInterpreterPalette',
as none of the parameters have JavaDoc.
Jeroen.
_
Jeroen,
That sounds interesting.
Feel free to create a PR on GitHub.
Gary
On Tue, May 23, 2023, 05:59 Vegt, Jeroen van der
wrote:
> Hi,
>
>
>
> I'm using Apache Commons Imaging to generate 8 bit (indexed) PNG files.
> Unfortunately, there doesn't seem to be
Hi,
I'm using Apache Commons Imaging to generate 8 bit (indexed) PNG files.
Unfortunately, there doesn't seem to be way to supply a custom color palette.
In particular, I'd like to use Wu's color quantization algorithm,
https://gist.github.com/bert/1192520.
Would a pat
Le mer. 10 mai 2023 à 12:29, Gilles Sadowski a écrit :
>
> Hello.
>
> Le mar. 9 mai 2023 à 23:43, Gary D. Gregory a écrit :
> >
> > Hi All,
> >
> > The method
> > org.apache.commons.imaging.icc.IccProfileParser.getICCProfileInfo(ByteSource)
> > looks like:
> >
> > public IccProfileInfo getI
Hello.
Le mar. 9 mai 2023 à 23:43, Gary D. Gregory a écrit :
>
> Hi All,
>
> The method
> org.apache.commons.imaging.icc.IccProfileParser.getICCProfileInfo(ByteSource)
> looks like:
>
> public IccProfileInfo getICCProfileInfo(final ByteSource byteSource) {
> // TODO Throw instead of
Hi All,
The method
org.apache.commons.imaging.icc.IccProfileParser.getICCProfileInfo(ByteSource)
looks like:
public IccProfileInfo getICCProfileInfo(final ByteSource byteSource) {
// TODO Throw instead of logging?
final IccProfileInfo result;
try (InputStream is = by
Then I encourage 1.0-beta1 ;-)
Gary
On Thu, Dec 8, 2022, 11:29 Bruno Kinoshita wrote:
> No objection from me :) 1.0b or 1.0, doing any progress on [Imaging] would
> be grand.
>
> -Bruno
>
> On Thu, 8 Dec 2022 at 17:11, Gilles Sadowski wrote:
>
> > [Moving to "d
No objection from me :) 1.0b or 1.0, doing any progress on [Imaging] would
be grand.
-Bruno
On Thu, 8 Dec 2022 at 17:11, Gilles Sadowski wrote:
> [Moving to "dev" ML...]
>
> Le jeu. 8 déc. 2022 à 16:56, Gary Gregory a
> écrit :
> >
> > Since we had alp
[Moving to "dev" ML...]
Le jeu. 8 déc. 2022 à 16:56, Gary Gregory a écrit :
>
> Since we had alpha releases, should we have a beta?
+1
It would allow modifying the API in order to e.g. provide a code that
self-documents the caller's responsibility wrt validation of external
input. [Something w
Relief Rendering
> <https://gwlucastrig.github.io/GridfourDocs/notes/ElevationGeoTiff1.html> to
> reflect the improvements to the imaging parameters specification. Finally,
> I'm working on a new article to discuss how to access metadata from
> GeoTIFFs. So I'll be using th
mprovements to the imaging parameters specification. Finally,
I'm working on a new article to discuss how to access metadata from
GeoTIFFs. So I'll be using the new Imaging library quite a bit.
Gary L.
On Thu, May 19, 2022 at 7:20 AM Bruno Kinoshita
wrote:
> You are very welcome
n the next coming weeks I will start some experiments with
Imaging 1.0-alpha3 using it in the Cantaloupe IIIF server and report the
results here in the dev mailing list.
Bruno
On Thu, 19 May 2022 at 23:03, Gary Lucas wrote:
> Obrigado, Bruno! I appreciate all of the careful work you
Obrigado, Bruno! I appreciate all of the careful work you put into this
release.
Gary
On Thu, May 19, 2022 at 3:56 AM Bruno Kinoshita wrote:
> The Apache Commons Team is pleased to announce the availability of
> Apache Commons Imaging 1.0-alpha3.
>
> Apache Commons Imaging, prev
The Apache Commons Team is pleased to announce the availability of
Apache Commons Imaging 1.0-alpha3.
Apache Commons Imaging, previously known as Apache Commons Sanselan,
is a library that reads and writes a variety of image formats, including
fast parsing of image info (size, color space, ICC
Forgot to include Gary Lucas' +1 (non-binding), sorry! Got confused with
the Gary's when counting the votes, sorry :)
-Bruno
-- Forwarded message -
From: Bruno Kinoshita
Date: Thu, 19 May 2022 at 14:16
Subject: [RESULT[[VOTE] Release Apache Commons Imaging 1.0-alpha
ommons Imaging 1.0-alpha2 was released, so I would like to
> release Apache Commons Imaging 1.0-alpha3.
>
> Apache Commons Imaging 1.0-alpha3 RC2 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC2
> (svn revision 54488)
>
> The
g a
post-it to look into it after the release.
Thanks Thomas
-Bruno
On Mon, 16 May 2022 at 21:18, Thomas Vandahl wrote:
> Hi Bruno,
>
> > Am 13.05.2022 um 14:02 schrieb Bruno Kinoshita :
> >
> > We have fixed quite a few bugs and added some significant enhancements
>
Hi Bruno,
> Am 13.05.2022 um 14:02 schrieb Bruno Kinoshita :
>
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons Imaging 1.0-alpha2 was released, so I would like to
> release Apache Commons Imaging 1.0-alpha3.
>
> Apache Commo
Kinoshita wrote:
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons Imaging 1.0-alpha2 was released, so I would like to
> release Apache Commons Imaging 1.0-alpha3.
>
> Apache Commons Imaging 1.0-alpha3 RC2 is available for review he
S name: "linux", version: "5.17.4-200.fc35.x86_64", arch: "amd64",
> family: "unix"
>
> - NOTE: Below are some updates that should be made to the site but I
> don't consider these to be blocking issues for the release.
> - There are some di
en_US, platform encoding: UTF-8
OS name: "linux", version: "5.17.4-200.fc35.x86_64", arch: "amd64",
family: "unix"
- NOTE: Below are some updates that should be made to the site but I
don't consider these to be blocking issues for the release.
- There
quot;linux", version: "5.17.5-200.fc35.x86_64", arch: "amd64", family:
> "unix"
>
> Thanks to all who made this possible!
>
> Cheers
> Andreas
>
>
>
> Am 13.05.22 um 14:02 schrieb Bruno Kinoshita:
>> We have fixed quite a few
a few bugs and added some significant enhancements
since Apache Commons Imaging 1.0-alpha2 was released, so I would like to
release Apache Commons Imaging 1.0-alpha3.
Apache Commons Imaging 1.0-alpha3 RC2 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/imagin
+1
Test source zip file: ASC and SHA OK.
Building default Maven goal OK
TODO: Update JaCoCo from 0.8.5 to 0.8.8.
Gary
On Fri, May 13, 2022 at 8:02 AM Bruno Kinoshita wrote:
>
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons Imaging 1.0-a
[x] +1 Release these artifacts
Bruno,
Thank you for all your hard work, your mad skills on github, and the
excellent insights on the PR's that you reviewed.
Gary (the other Gary)
We have fixed quite a few bugs and added some significant enhancements
since Apache Commons Imaging 1.0-alpha2 was released, so I would like to
release Apache Commons Imaging 1.0-alpha3.
Apache Commons Imaging 1.0-alpha3 RC2 is available for review here:
https://dist.apache.org/repos/dist/dev
RC1 vote is cancelled due to an issue in the build related to a Maven
Plug-in. I am preparing a new release at the moment.
Thanks
Bruno
On Fri, 13 May 2022 at 17:26, Bruno Kinoshita wrote:
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons I
asf/commons-imaging.git
> > --branch commons-imaging-1.0-alpha3-RC1 commons-imaging-1.0-alpha3-RC1
> >
>
> I get a build failure running „mvn clean install site“ using the
> environment
>
> Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
>
.git
> --branch commons-imaging-1.0-alpha3-RC1 commons-imaging-1.0-alpha3-RC1
>
I get a build failure running „mvn clean install site“ using the environment
Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Java version: 11.0.13, vendor: GraalVM Community, runtime:
/Library/Jav
;s/notes from pom.xml and upgrade to commons-parent-53
Thanks!
-Bruno
[1]
https://github.com/apache/commons-imaging/blob/b1cfcaad38de7c30f7814a5b3d80e45fe2bd9af1/pom.xml#L29-L32
[2]
https://github.com/apache/commons-imaging/blob/b1cfcaad38de7c30f7814a5b3d80e45fe2bd9af1/pom.xml#L29-L32
On Fri, 13
le in Maven Central in 5-10 days (I'll
leave it open for a bit longer since it's almost weekend - already here in
NZ).
-Bruno
On Thu, 12 May 2022 at 23:54, Gary Lucas wrote:
> My primary interest for Commons Imaging is using it to access
> geo-referenced TIFF file (GeoTIFF) . So
rs for 1.0 some
> > years ago (4? maybe 5 years ago?). I'm finishing the preparations for the
> > 1.0-alpha3 vote for Imaging. It's the last alpha release I have planned.
> >
> > I started working on Imaging when I became curious if we could use it as
> an
>
We have fixed quite a few bugs and added some significant enhancements
since Apache Commons Imaging 1.0-alpha2 was released, so I would like to
release Apache Commons Imaging 1.0-alpha3.
Apache Commons Imaging 1.0-alpha3 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev
My primary interest for Commons Imaging is using it to access
geo-referenced TIFF file (GeoTIFF) . So far, it's worked out pretty well.
The TIFF file format provides a flexible definition for attaching metadata
to images. Back in the 1990's, the Geographic Information System (GIS)
Nice job, Bruno! Thanks for pushing this.
Matt
On Wed, May 11, 2022, 11:32 PM Bruno Kinoshita
wrote:
> Hi,
>
> We have fixed all the issues that were raised as blockers for 1.0 some
> years ago (4? maybe 5 years ago?). I'm finishing the preparations for the
> 1.0-alpha3 vo
Hi,
We have fixed all the issues that were raised as blockers for 1.0 some
years ago (4? maybe 5 years ago?). I'm finishing the preparations for the
1.0-alpha3 vote for Imaging. It's the last alpha release I have planned.
I started working on Imaging when I became curious if we could
Hello,
The IMAGING-159 [1] issue was raised during one of the 1.0 vote threads for
Commons Imaging and it is a blocker for the final release.
We have a pull request [2] in which we couldn't reach consensus on an issue
with generics..
There is a class called "Imaging.java", which
Hi,
On IMAGING-159 [1], the current released code of Imaging uses Map params to pass parameters to different image parsers.
This was raised as a blocker for the 1.0 release, and we are trying to address
it in the next alpha release to get the final 1.0 release out of the door.
I had a go and
1 - 100 of 747 matches
Mail list logo
