The vote is open to anyone Alex. The more the merrier.
It has a requirement of at least three PMC members giving a +1 vote for the
vote to pass.
Whenever a PMC -or anybody else in this mailing list- raises an issue or votes
-1 and explains what went wrong building or testing the proposed
repository.
kinow pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-imaging.git
commit 5ab6b2059f9201fdec1d73991f6ffce65ae18e79
Merge: 4ba419d 7fb71bd
Author: Bruno P. Kinoshita
AuthorDate: Thu Sep 10 17:27:24 2020 +1200
Merge pull request #96 from
apache
[x] +1 Release these artifacts
Built from tag with Maven 3.5.4 and Java 8. Build passing OK, reports look good.
Checked signatures, found no issues. Inspected some files in binary/source
folders of the dist area, all looking good.
Thanks for managing this release Gary.
Bruno
On
Bruno P. Kinoshita
wrote:
> Thanks for heads up Gary! Looking forward to reading/reviewing the new
> code!
> Bruno
>
Hi Bruno,
It's in there now, feel free to take a look and review, change, or fiddle
;-)
Gary
>
> On Sunday, 11 October 2020, 3:16:20 am NZDT, Gary Gre
Checked signatures, and inspected files in the dist area. No issues.
Tried building following instructions in `BUILDING.txt` but it failed due to
files without license when RAT report was executed.
Tried again with the commands in the body of your e-mail Gary, but it failed
again on: mvn -V
Thanks for heads up Gary! Looking forward to reading/reviewing the new code!
Bruno
On Sunday, 11 October 2020, 3:16:20 am NZDT, Gary Gregory
wrote:
Hi All:
FYI,
I am working and nearly done adapting our file filters to work with
java.nio.file.Files.walk APIs.
My goal overall in
That looks really useful Gary! I always wondered if I would have to open a
JIRA ticket in order to add some labels like #imageprocessing to imaging, or
#java to lang.
Looks like that's possible with this .asf.yaml.
I think the notifications part will be useful for that discussion around where
SM -DAES_ASM -DVPAES_ASM
-DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM
3: built on: Tue Dec 4 20:09:18 UTC 2018
4: platform: debian-amd64
5: OPENSSLDIR: "/usr/lib/ssl"
Gary
On Sun, Aug 23, 2020 at 2:23 AM Bruno P. Kinoshita wrote:
> Hi Gary,
>
> I might be able to test on Win64
[x] +1 Release these artifacts
Build OK from the tag with Maven 3.5.4, Ubuntu 18.04 LTS, JDK 1.8.
Site reports look good. The docs about upgrading from 2.x to 3.x should be
useful for users, great idea.
Had a look inside the dist archives for binaries and sources, everything looks
OK. Found
Might be easier to have a simpler page with the link as Gilles suggested.
But +1 to the the idea of showing users in GitHub too how to report security
issues.
Bruno
On Sunday, 23 August 2020, 4:13:10 am NZST, Gilles Sadowski
wrote:
2020-08-22 16:02 UTC+02:00, Gary Gregory :
>
Hi Gary,
I might be able to test on Win64 and Linux64 this week. You mentioned
snapshots… what is the easiest way to test them? Run some code using the code
of the snapshots, or perhaps run the build+tests from a tag/commit?
Cheers
Bruno
On Sunday, 23 August 2020, 11:49:21 am NZST, Gary
[x] +1 Release these artifacts
Building OK from tag with JDK 8 on Ubuntu LTS. Site reports look OK. Checked
signatures of dist/maven archives, no issues.
Manually inspected files in the dist area, no issues with the binary/source
archives.
Had a look at the change log, quite small release.
Tested building on Java 8 from new tag, and checked the version of the dist
area archives
[x] +1 Release these artifacts
Bruno
On Wednesday, 30 September 2020, 5:46:15 pm NZDT, Gary Gregory
wrote:
*[The difference between RC1 and RC2 is that pom.xml fil**le's* *version
has been
[x] +1 Release these artifacts
Build passing from tag with `mvn clean test install site` with
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_265, vendor: Private Build, runtime:
[x] +1 Release these artifacts
Building from tag OK, with
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_265, vendor: Private Build, runtime:
/usr/lib/jvm/java-8-openjdk-amd64/jre
Default
[x] +1 Release these artifacts
Build passing from tag with:
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_252, vendor: Private Build, runtime:
/usr/lib/jvm/java-8-openjdk-amd64/jre
Default
Hi Carl,
Was going to vote but I think I did it already :)
Cheers
Bruno
On Sunday, 24 May 2020, 4:28:32 pm NZST, Carl Hall
wrote:
Nudging this thread in case anyone has some cycles to help us get that last
vote to release. Thanks to all for helping get this done.
If you get a
Hi,
I think the code is in the dormant section now:
http://svn.apache.org/viewvc/commons/dormant/el/trunk/http://svn.apache.org/viewvc/commons/dormant/el/
Bruno
On Saturday, 30 May 2020, 7:12:40 pm NZST, Xeno Amess
wrote:
https://github.com/apache/commons-el is an empty repo.
And
Hi Amey!
>> 3. Any pending work or jiras available which I can help to graduate commons
>> graph? this is not available https://issues.apache.org/jira/projects/GRAPH ?
>
>Strange; again maybe the reason is in the ML archive.
I believe projects in the Sandbox use the common JIRA project
I **think** projects using Apache gitbox can be/are hosted/mirrored on GitHub.
As for moving to git, I'm +1 in principle. But I don't know if we create git
repositories under github.com/apache for projects in the sandbox. Maybe one
option here would be moving the sandbox over to git instead?
Hi Gary!
I've read the proposal in the JIRA issue, thanks a lot for explaining it so
well. I've added some comments in JIRA, mainly around this new writer and
whether it would replace the existing one or be an alternative writer; and on
streams vs File.
But sounds like a good improvement,
[x] +1 Release these artifacts
Build passing from tag, with the commands in the body of the vote e-mail, with
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_265, vendor: Private Build, runtime:
[x] +1 Release these artifacts
Building OK from tag on my environment.
Thanks
Bruno
On Wednesday, 28 October 2020, 5:27:32 am NZDT, Gary Gregory
wrote:
We have fixed a few bugs and added some enhancements since Apache Commons
VFS Project 2.6.0 was released, so I would like to
uce.
Cheers
Bruno
On Monday, 26 October 2020, 7:51:08 am NZDT, Gary Gregory
wrote:
On Mon, Oct 19, 2020 at 3:03 AM Bruno P. Kinoshita wrote:
> Checked signatures, and inspected files in the dist area. No issues.
>
> Tried building following instructions in `BUILDING.txt` but i
Thanks for helping with so many releases (and issues, PR's, mails, etc :) Gary!
I'll prepare an alpha2 for [imaging] soon too.
Thanks
Bruno
On Sunday, 19 July 2020, 1:00:42 am NZST, Gary Gregory
wrote:
Hi All,
We've just released Commons Lang 3.11. My goal is to release Text very
se review the release candidate and vote.
This vote will close no sooner that 72 hours from now.
[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
Thank you,
Bruno P. Kinoshita,
Release Manager (using key
Not a problem Sebb. Just the name should be fine. I was preparing the
1.0-alpha2 release for [imaging], and just realized I forgot to close the
artefact. I'm re-uploading, and will close with the tag as description (good
idea).
Cheers
Bruno
On Sunday, 2 August 2020, 7:17:37 am NZST,
[x] +1 Release these artifacts
Build successfully with JDK 8, Ubuntu LTS, Maven 3.5, from tag with `mvn clean
test install`.
Site reports look good. Had a look around files in dist area checking license,
structure, release-notes, etc. Everything looks OK.
Checked signatures of the dist area
[x] +1 Release these artifacts
Building OK from tag, with Java 8, Ubuntu LTS, Maven 3.5, and using target mvn
clean test install site.
Site reports look OK. Checked signature, and contents of samples from
dist/maven repo.
Everything looking OK.
Thanks!
Bruno
On Sunday, 2 August 2020,
My own vote
[x] +1 Release these artifacts
Bruno
On Sunday, 2 August 2020, 11:54:01 am NZST, Bruno P. Kinoshita
wrote:
We have fixed quite a few bugs and added some significant enhancements since
Apache Commons Imaging 1.0-alpha1 was released, so I would like to release
Apache
The release was approved with the following votes
- +1 sebb (binding)
- +1 Gary Gregory (binding)
- +1 Bruno P. Kinoshita (binding)
- +1 Gary Lucas (non-binding)
Thanks to all votes. I will prepare the release in the next hours.
Cheers
Bruno
On Sunday, 2 August 2020, 11:54:01 am NZST
The Apache Commons Imaging team is pleased to announce the
commons-imaging-1.0-alpha2 release!
Apache Commons Imaging (previously Sanselan) is a pure-Java image library.
There are breaking changes between 1.0-alpha1 and 1.0-alpha2, until we
stabilize the API for our 1.0 release.
Users are
Roger that. Will try to remember for the next release, or maybe we should
include a note in the release instructions.
Bruno
On Saturday, 8 August 2020, 11:22:06 pm NZST, sebb wrote:
I've just noticed that several recent announcement emails have used the tags
[ANNOUNCEMENT]
or even
ng: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Gary
On Sat, Aug 1, 2020 at 7:54 PM Bruno P. Kinoshita wrote:
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons Ima
in the release-prepare
documentation. Will commit it later this week.
Cheers
Bruno
On Sunday, 2 August 2020, 10:45:13 pm NZST, sebb wrote:
On Sun, 2 Aug 2020 at 00:54, Bruno P. Kinoshita wrote:
>
> We have fixed quite a few bugs and added some significant enhancements since
> Apach
Good stuff Gary! Couple questions.
Q1/ Will there be a follow-up post on behavioral compatibility too? :)
Q2/ Only component I'm working (meaning pushing for a release soon-ish) on at
the moment is [imaging] for some IIIF related stuff. Should we rename the
package from o.a.c.imaging to
I will take a look at that issue for Circuit Breakers using old swing/desktop
classes, and see if it can be deprecated so that we can use Java 9 modules
without requiring the java.desktop module too.
But not a blocker for 3.11, just nice to deprecate as soon as possible, to give
more time for
[x] +1 Release these artifacts
Build passing fine on Java 8, Ubuntu LTS. Site generated successfully too,
reports look OK.
Thanks
Bruno
On Sunday, 7 June 2020, 12:34:19 am NZST, Gary Gregory
wrote:
We have fixed a few bugs and added some enhancements since Apache Commons
BCEL
[x] +1 Release these artifacts
Build passed on JDK 8 Ubuntu LTS, site reports generated and look OK. Checked
dist area signatures and found no issues.
Cheers
Bruno
On Wednesday, 22 July 2020, 8:57:06 am NZST, Gary Gregory
wrote:
Hi All,
We have fixed a few bugs and added some
[x] +1 Release these artifacts
Building passing from tag, with `mvn clean test install` on:
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_252, vendor: Private Build, runtime:
[x] +1 Release these artifacts
Build passing from tag, with `mvn clean install site`, on:
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_252, vendor: Private Build, runtime:
Not following the thread, but from your explanation it sounds OK to me. There
are other parts of Lang that could do with some trimming for a future 4.x
release I think, either moving some code to other components or suggesting the
use of JVM code (e.g. some of the date/time methods).
Bruno
Hi,
I've been using GitHub actions for a while now, and it works fine. It's really
handy to have CI and code in GitHub. I believe even users not using GitHub
(i.e. no GitHub account) are able to access the CI logs, just like Travis.
I never gave much thought to the Coveralls and JaCoCo issue.
[x] +1 Release these artifacts
Build passing on JDK 8, Ubuntu LTS.
Site reports look good.
The changes report is showing the date as 2020-MM-DD. But I think that can be
fixed later in the site.
Checked signatures from Maven repo and from the dist area src and bin files.
Found no issues.
Hi,
Unfortunately I don't think that's possible. The code is hosted at ASF, and
synced with GitHub.
The issues are also hosted at ASF infra, but I don't believe we have any sort
of issues-mirroring service available at ASF.
I agree it would be convenient to have everything in a single place,
I left a comment when merging in Git (thought it would appear in here, but it
didn't, sorry). [functor] has not been released yet. So I thought it wouldn't
be necessary to have an entry in changes.xml as we are not updating from
version X to Y.
On Tuesday, 24 November 2020, 1:53:36 pm
Hi,
+1 to javacc if that works for you use case. Apache Jena ARQ module uses it, in
case you want to look at an existing project for ideas [1].
Cheers,
Bruno
[1] https://github.com/apache/jena/tree/master/jena-arq/Grammar
On Saturday, 19 December 2020, 7:48:31 am NZDT, Matt Juntunen
Hi Lee,
I don't know much about Compress' API, only as a user of the API in some
projects.
I had a cursory look, read comments and JIRA and left comments on GitHub PR. No
blockers for me. Hope it helps.
Thanks for bringing it to the mailing list, and for the review.
CheersBruno
On Monday,
ng from the tag or the zip or tar?
Gary
On Tue, Oct 20, 2020, 18:52 Bruno P. Kinoshita wrote:
> >Overall, I would not say this is a blocker. WDYT?
>
> If others are able to build it I'd say it's not a blocker.
>
> I tried the commands you sent below. I think they are the same o
mpared to a single module build.
Overall, I would not say this is a blocker. WDYT?
Gary
On Mon, Oct 19, 2020 at 3:03 AM Bruno P. Kinoshita wrote:
> Checked signatures, and inspected files in the dist area. No issues.
>
> Tried building following instructions in `BUILDING.txt` but it failed
Hi Xeno,
Good to hear about your enthusiasm, and thanks for your contributions.
The ASF page about contributors [1] describes the process that is used in
Apache Commons, as well as in other of the ASF projects.
I think it is hard to tell how close someone is from being a committer, I am
[x] +1 Release these artifacts
NB: the NOTICE file needs the yearly update, from 2020 to 2021. Not a blocker I
think?
Building OK from tag with `mvn clean test install site` on
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home:
[x] +1 Release these artifacts
Building OK from the tag, with Ubuntu LTS + Java 8, Maven 3.5.4.
Minor notes:
- "Maven artifacts are here", the URL is 404 for me, I logged in to
repository.apache.org, and copied the link:
OK =
Thanks for the explanation. Looks like it would be helpful for IDE/static
analyzers/etc, without any impact for the users runtime.
I think a) makes sense, but b) would be OK too for me.
Cheers
Bruno
On Monday, 1 February 2021, 11:58:23 pm NZDT, Jochen Wiedmann
wrote:
Hi,
as a
Hi Matt,
It sounds like a good addition to [text]. What do you think about creating a
JIRA issue and preparing a pull request? It would be easier to review the
implementation that way IMO.
There are some users that reply to github pull requests too, but normally don't
read the mailing list
[x] +1 Release these artifacts
At the top of the RELEASE-NOTES.txt, it's showing "Version 3.2". Shouldn't it
be "Version 3.2.1"? Or do we skip the bug fix part? Not a blocker I think...
In the generated site (locally, and dist area) there are links to Javadocs for
v1.1, v2.2.1, and v3.2.
can do to help with the new
Commons Imaging.
I've looked at the latest changes in your personal fork of Imaging. I
could do some stuff on the TIFF branch if you wanted.
Gary
On Fri, Apr 9, 2021 at 6:33 PM Bruno P. Kinoshita wrote:
> Hi all,
>
> Family will be away in May/June for
[x] +1 Release these artifacts
Building OK with
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /opt/apache-maven-3.6.3
Java version: 11.0.11, vendor: Ubuntu, runtime:
/usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name:
+1 for 2)
In [Imaging] we do something similar, but it was easier because there were many
methods that were already doing it (throwing ImageReadException or
ImageWriteException).
Bruno
On Sunday, 27 June 2021, 11:03:31 pm NZST, Stefan Bodewig
wrote:
Hi
I'd like to get closure
[x] +1 Release these artifacts
Building OK from tag with JDK 11 and Maven 3.6.3 on Linux Ubuntu.
Inspected archives & signatures in the dist area, found no issues.
Site reports look good.
> (note some *relative* links are broken and the 1.0 directories are not
>yet created - these will
[x] +1 Release these artifacts
`mvn clean test install site` is failing on JDK 11 Maven 3.6.3 when running
FindBugs, but working fine with JDK 8.
The RELEASE-NOTES.txt for 1.21 starts with "Compress 1.20 now at least requires
Java 8 to build and run." which is a bit confusing, but not a
[x] +1 Release these artifacts
Building OK with JDK 11 and Maven 3.6.3. Reports look good. Inspected dist area
archives and found no issues.
Thanks Gary!
Bruno
On Saturday, 10 July 2021, 1:52:51 pm NZST, Gary Gregory
wrote:
We have fixed a few bugs and added some enhancements
Hi all,
I've created a PR to add .asf.yaml to Commons Imaging. The PR includes only
basic GitHub project information such as description (from pom.xml), URL to
Commons Imagnig component page, and these labels: [java, image, imaging,
image-processing]
The .asf.yaml docs [2] state
>When using
Haven't used nor had the need to contribute to any of these. I thought I'd be
able to work on functor, but I think I'll be working on Imaging for the rest of
the year.
Out of these, I think the last ones I used were digester and jelly. I think
Jenkins uses Jelly, and I **think** they stopped
+1
Site reports look good, signatures look good too. Inspected maven archives &
dist binaries and sources. Found nothing out of the ordinary.
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_282,
[X] +1 Release these artifacts
Building OK from tag, with `clean test install` targets.
Used the site from dist area. Reports look OK (no idea
why we have 2 checkstyle reports, but new one is consistent
with existing report), even fixing some checkstyle/spotbugs
bugs in the core module.
+1 for oss fuzz. Fabian also got in contact a few days earlier, and asked me
about using it with Commons Imaging. I told him it had to be discussed here
first, but that I thought it could be useful (we are parsing several image file
formats, probably a few things could be improved).
As for
Hi all,
Family will be away in May/June for ~15 days, and I'm planning to use the spare
time these weeks to release Apache Commons Imaging 1.0-alpha3, and Apache
Commons Text 1.10.
I'm working with Gary Lucas on fixing the Hashmap parameters and replacing them
by a new object [1]. Gary has
Thank you Stefan!
Bruno
On Monday, 19 April 2021, 4:22:18 am NZST, Stefan Bodewig
wrote:
On 2021-04-18, Fabian Meumertzheim wrote:
> Anyone who is (or wants to be) a moderator on that list and has a Google
> account, please let me know the primary email address so that I can add it
Hi Fabian,
Yes, please: brunodepaulak at gmail
Thanks!
Bruno
On Monday, 19 April 2021, 7:36:42 am NZST, Fabian Meumertzheim
wrote:
I have prepared the integrations at
https://github.com/CodeIntelligenceTesting/oss-fuzz/tree/commons-compress
and
Done in imaging! Thanks
https://github.com/apache/commons-imaging/pull/130
Bruno
On Wednesday, 21 April 2021, 2:27:38 am NZST, Fabian Meumertzheim
wrote:
The first OSS-Fuzz build passed and some bugs have already been created.
Everything looks good from my side, but let me know if
[x] +1 Release these artifacts
Tested with (time to upgrade my maven & default JVM I reckon, might bump these
up next month)
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_282, vendor: Private
I think it probably should go to dormant. I had a look at found a few users in
mvnrepository [1] and from random internet search [2][3][4]
But no activity as you pointed, and I think we can move it back to proper later
if there's interest from users/devs later. So +1
Bruno
[1]
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 exposes several
, Bruno P. Kinoshita
wrote:
Funny, I checked the [imaging] version and it's correct. But I don't recall
updating that file myself. I wonder if the commons-release-plugin has some
feature to update this info somehow?
Bruno
On Tuesday, 13 July 2021, 6:04:01 pm NZST, Stefan Bodewig
Funny, I checked the [imaging] version and it's correct. But I don't recall
updating that file myself. I wonder if the commons-release-plugin has some
feature to update this info somehow?
Bruno
On Tuesday, 13 July 2021, 6:04:01 pm NZST, Stefan Bodewig
wrote:
On 2021-07-13, Henri
[X] +1 Release these artifacts
Build from tag on:
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /opt/apache-maven-3.6.3
Java version: 11.0.11, vendor: Ubuntu, runtime:
/usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name:
Agreed. Just document in the release notes.
On Friday, 30 July 2021, 4:21:01 pm NZST, Gary Gregory
wrote:
It seems to me we just need to update our release notes.
Gary
On Fri, Jul 30, 2021, 00:00 PeterLee wrote:
> Hi all,
>
> There is a new issue Compress-583 reporting Compress
[x] +1 Release these artifacts
Build OK from tag with
Maven home: /opt/apache-maven-3.6.3
Java version: 11.0.11, vendor: Ubuntu, runtime:
/usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-80-generic", arch: "amd64", family:
[x] +1 Release these artifacts
Building OK on Maven 3.6.3 JDK 11 on Ubuntu.
Checked signatures, found no issues. Site reports look good too. Inspected a
couple of files in the dist area, LICENSE/NOTICE/other files all good, no
issues.
Thanks and sorry for the delay reviewing the release.
Building OK from the tag on my environment, reports look good too. Thanks!
[x] +1 Release these artifacts
Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
Maven home: /opt/apache-maven-3.8.2
Java version: 11.0.11, vendor: Ubuntu, runtime:
/usr/lib/jvm/java-11-openjdk-amd64
Hi,
Thomas has had a lot of patience troubleshooting this issue with me off-list
(thanks heaps!). Not only remotely, but I think we are on opposite timezones
too.
Yesterday Thomas suggested to look at EncryptingSerializer, and also to look at
the time that my machine was taking to get data
Hi,
I would prefer a solution that fixes the email issue, but if it bothers others,
I guess I could enable dependabot on my fork of commons-imaging, commons-lang,
commons-text, or any other repository that I may RM one day.
I use dependabot in other personal and $work projects and it's very
Mail on Android
On Fri, 31 Dec 2021 at 10:05, Bruno P.
Kinoshita wrote: Hi,
Thomas has had a lot of patience troubleshooting this issue with me off-list
(thanks heaps!). Not only remotely, but I think we are on opposite timezones
too.
Yesterday Thomas suggested to look
-
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on
project commons-jcs3-core: There are test failures.
-Bruno
On Tuesday, 28 December 2021, 11:08:47 pm NZDT, Thomas Vandahl
wrote:
Hi Bruno.
Hi,
I couldn't find the tag "commons-jcs-3.1-rc1", I think the tag is
"commons-jcs3-3.1-rc1" (missing 3 after jcs)?
Building from that tag on:
Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
Maven home: /opt/apache-maven-3.8.2
Java version: 11.0.13, vendor: Ubuntu, runtime:
[x] +1 Release these artifacts
Build passed with no issues on my environment with `mvn clean test install site`
Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
Maven home: /opt/apache-maven-3.8.2
Java version: 11.0.13, vendor: Ubuntu, runtime:
/usr/lib/jvm/java-11-openjdk-amd64
:31 am NZDT, Thomas Vandahl
wrote:
> Am 28.12.2021 um 13:01 schrieb Bruno P. Kinoshita
> :
>
> `mvn clean test install site` took a few minutes, but it just finished
> running. Below the error that just happened again on my environment (appears
> to be consistent f
[x] +1 Release these artifacts
Built successfully from tag, with JDK 11 on Ubuntu. Found no issues with dist
area archives.
Site reports look good. The core module has RAT errors but in both generated
and live site, but I think they are test files, probably created during the
site
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
Vandahl
wrote:
Hi Bruno,
> Am 05.01.2022 um 06:41 schrieb Bruno P. Kinoshita
> :
>
> I didn't have much time, so inspected only one file, randomly selected, from
> the dist area. The src zip. @Thomas, I think the NOTICE has the date 2020? I
> think that can be fixed
t file got there... still not clear to me.
-Bruno
On Thursday, 6 January 2022, 10:30:44 pm NZDT, Thomas Vandahl
wrote:
Hi Bruno,
> Am 05.01.2022 um 21:59 schrieb Bruno P. Kinoshita
> :
>
> Did you have an old NOTICE file in the directory where you built the jcs
> release? I read
won't be of much help with the other thread.
-Bruno
On Thursday, 6 January 2022, 10:30:44 pm NZDT, Thomas Vandahl
wrote:
Hi Bruno,
> Am 05.01.2022 um 21:59 schrieb Bruno P. Kinoshita
> :
>
> Did you have an old NOTICE file in the directory where you built the jcs
>
Reviewed about 1/4 of the PR, but it was mainly about serialization (started
from the bottom, comparing using GitHub UI [1]). But that code and tests were
looking OK.
Will try to go over a few more files, but I also found a PDF in the issue that
I think I will try to read first, to have a
[X] +1 Release these artifacts
Builds OK from tag on
Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
Maven home: /opt/apache-maven-3.8.5
Java version: 17.0.7, vendor: Private Build, runtime:
/usr/lib/jvm/java-17-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS
+1
Tested on
Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
Maven home: /opt/apache-maven-3.8.5
Java version: 17.0.9, vendor: Private Build, runtime:
/usr/lib/jvm/java-17-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version:
+1
Tested on
Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
Maven home: /opt/apache-maven-3.8.5
Java version: 17.0.9, vendor: Private Build, runtime:
/usr/lib/jvm/java-17-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version:
501 - 597 of 597 matches
Mail list logo
