I apologize for that. I merged this through the GitHub UI (and will likely
never do so again). We can amend the message to remove all of the noise but
that would involve using `git push --force`, which is not something I've
ever done with an Apache repo.
-Matt
On Sat, Apr 27, 2024 at 8:42 PM
clone. If someone could give me a code review and point out areas to
> > > improve the code or errors i would be very thankful.
> >
> > Thank you for tackling this issue.
> > It was part of a broader discussion about the API around the hull
> > functionality.
>
...@gmail.com)> wrote:
> > > Yeah, there is code that looks odd for 2022, like a custom Closeable
> > > interface instead of reusing the JRE's. I'll take a look.
> > >
> > > Gary
> > >
> > > On Sun, Jul 17, 2022 at 2:32 PM Matt Juntunen > &g
+1
It would be great to get this code out to developers.
Regards,
Matt J
On Mon, Jul 25, 2022 at 11:46 AM Gilles Sadowski wrote:
>
> Le lun. 25 juil. 2022 à 16:38, Alex Herbert a
> écrit :
> >
> > On Mon, 25 Jul 2022 at 14:37, Gilles Sadowski wrote:
> >
> > > Hello.
> > >
> > > How about
gt; On Sun, Jul 17, 2022 at 10:49 AM Matt Juntunen
> wrote:
> >
> > I am going to put the 2.0.0-beta1 release on my TODO list. I am
> > currently working toward a release of commons-text, so I can't be sure
> > on a timeline. If anyone has questions or time to pick thi
wrote:
> >
> > On Sun, 17 Jul 2022 at 15:45, Matt Juntunen
> > wrote:
> > >
> > > Hello all,
> > >
> > > Steve Springett recently created a PR [1] for commons-parent that
> > > introduces the generation of software bill of materials (
I am going to put the 2.0.0-beta1 release on my TODO list. I am
currently working toward a release of commons-text, so I can't be sure
on a timeline. If anyone has questions or time to pick this up, please
let me know.
Regards,
Matt J
On Fri, Jul 15, 2022 at 12:35 PM Matt Juntunen
wrote
Hello all,
Steve Springett recently created a PR [1] for commons-parent that
introduces the generation of software bill of materials (SBOM)
artifacts into the build process. First of all, thank you, Steve.
Secondly, I believe this is an important topic that should be
addressed by our community.
org/releases/versioning.html
>
> Sorry, I must have been thinking of a different project.
>
> Sebb
>
> On Wed, 13 Jul 2022 at 01:36, Gary Gregory wrote:
> >
> > A beta is a good idea IMO.
> >
> > Gary
> >
> > On Tue, Jul 12, 2022, 17:19 Matt Juntune
Based on what I'm hearing, I'm thinking a beta release might be
appropriate. That would give consumers a chance to move away from the
previous version while giving us a chance to test and fine-tune the
API. Thoughts?
Regards,
Matt J
On Tue, Jul 12, 2022 at 4:15 PM Christoph Grüninger wrote:
>
>
t regards,
> rodde
>
> ti 12.7.2022 klo 22.49 Matt Juntunen kirjoitti:
>
> > Thanks! We should be ready for you to put together a PR for this. Have
> > we cleared any licensing or copyright issues on this algorithm? I
> > can't recall.
> >
> > Regards,
>
Thanks! We should be ready for you to put together a PR for this. Have
we cleared any licensing or copyright issues on this algorithm? I
can't recall.
Regards,
Matt J
On Tue, Jul 12, 2022 at 2:06 AM Rodion Efremov wrote:
>
> Hello,
>
> I have added the benchmark data (both my and Matt's) to the
Hello,
Does anyone know what the state of 2.0 development is here? It looks
like the last feature-related changes were from Sept 2021. Is there
anything preventing a release?
Regards,
Matt J
On Mon, Jul 11, 2022 at 9:51 AM Christoph Grüninger wrote:
>
> Dear Apaches!
>
> Apache FileUpload saw
patient :)
>
> Cheers
> -Bruno
>
> On Sun, 10 Jul 2022 at 17:03, Rodion Efremov wrote:
>
> > Hi Matt,
> >
> > It has been almost a week since your last response. Did you take a look at
> > my work?
> >
> > Best regards,
> > rodde
> >
Severity: Moderate
Description:
Apache Commons Configuration performs variable interpolation, allowing
properties to be dynamically evaluated and expanded. The standard format for
interpolation is "${prefix:name}", where "prefix" is used to locate an instance
of
regards,
> rodde
>
> [1] https://github.com/coderodde/indexedLinkedList/#benchmark-with-jmh
> [2]
> https://github.com/coderodde/IndexedLinkedListBenchmark/blob/main/src/main/java/com/coderodde/IndexedLinkedListPerformance.java
>
> On Fri, Jul 1, 2022 at 6:11 AM Matt Junt
st working only for
List>String< #137. Thanks to cigaly.
o Use final #141. Thanks to Arturo Bernal.
o Replace test asserts by simpler but equivalent calls. #139 Thanks to
Arturo Bernal.
o CONFIGURATION-764: Single Variable Interpolation #182. Thanks to Ning Zhang,
Matt Juntunen, Br
://commons.apache.org/proper/commons-configuration/apidocs/index.html
On Mon, Jul 4, 2022 at 3:14 AM Alex Herbert wrote:
>
> On Mon, 4 Jul 2022 at 03:41, Matt Juntunen
> wrote:
>
> > I'm not sure what to do
> > about the javadoc warnings on the generated classes. From the comments
> >
This vote passes with the following votes:
- Bruno Kinoshita +1 (binding)
- Gary Gregory +1 (binding)
- Matt Juntunen +1 (binding)
I will begin finalizing the release shortly.
Regards,
Matt J
On Sun, Jul 3, 2022 at 10:40 PM Matt Juntunen wrote:
>
> Thanks, Bruno and Gary!
>
> Gar
mac os x", version: "12.4", arch: "x86_64", family: "mac"
>
> Darwin *** 21.5.0 Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:22
> PDT 2022; root:xnu-8020.121.3~4/RELEASE_X86_64 x86_64
>
> Gary
>
> On Thu, Jun 30, 2022 at 12:23 AM Matt J
ers/garydgregory/Downloads/cc/commons-configuration2-2.8.0-src/target/generated-sources/javacc/org/apache/commons/configuration2/plist/Token.java:117:
> > warning: no @return
> > [WARNING] public static Token newToken(int ofKind, String image)
> > [WARNING] ^
> > [WARNING]
&g
feedback:
> https://markmail.org/message/y3tozjdke2ivz3dr
>
> >
> > Best regards,
> > rodde
> >
> > to 23.6.2022 klo 19.06 Matt Juntunen kirjoitti:
> >
> > > Hello,
> > >
> > > Thanks for providing the data here. I will hopefully
ons/configuration/2.8.0-RC3/site/rat-report.html
KEYS:
https://www.apache.org/dist/commons/KEYS
Please review the release candidate and vote.
This vote will close no sooner than 72 hours from now.
[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ]
https://dist.apache.org/repos/dist/dev/commons/configuration/2.8-RC2/site/userguide/upgradeto2_0.html
> ?
>
> Gary
>
> On Tue, Jun 21, 2022 at 11:47 PM Matt Juntunen
> wrote:
> >
> > We have fixed quite a few bugs and added some significant enhancements
> >
Hello,
Thanks for providing the data here. I will hopefully have time to take
a look at this over the weekend. Send me a ping here on the dev list
if you don't hear back from me (or someone else) within a week.
Regards,
Matt J
On Tue, Jun 21, 2022 at 7:22 AM Rodion Efremov wrote:
>
> Hi,
>
>
45 AM Gary Gregory wrote:
>
> Please use 2.8.0, I've been using the 3 part version format for all recent
> releases. I think it would be nice to follow this naming here.
>
> Gary
>
> On Tue, Jun 21, 2022, 22:30 Matt Juntunen wrote:
>
> > Thanks, Bruno! I'm going to go
rat-report.html
KEYS:
https://www.apache.org/dist/commons/KEYS
Please review the release candidate and vote.
This vote will close no sooner than 72 hours from now.
[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppos
; happens in other projects (I think CSV had a non-utf readme or release note
> too).
>
> Site reports look great.
>
> Tested signatures from Maven and from dist area, found no issues.
>
> [x] +1 Release these artifacts (if the README issue is not a blocker)
>
> Thanks!
>
han 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,
Matt Juntunen,
Release Manager (using key 7DD53AEFEDF1C3D392B51EBE346F4FCECFB70B1A)
For following is intended as a helper and refresher for re
gt;
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > mattjuntunen pushed a commit to branch 2.8.0-release
> > in repository
> > https://gitbox.apache.org/repos/asf/commons-configuration.git
> >
> > commit 6434507226c639a41d45af3b
t; some effort.
> As such, they need to mentioned in release notes, and the level of
> change needed should be reflected in the version numbering.
> e.g. if only a recompile is needed, then a patch version bump would be
> sufficient.
> Otherwise at least a minor version bump
Is someone able to confirm that the
METHOD_NO_LONGER_THROWS_CHECKED_EXCEPTION japicmp compatibility change
is something we're ok with between releases? Note that this is a
binary compatible change but not a source compatible one.
Regards,
Matt J
On Sun, Jun 19, 2022 at 10:50 AM Matt Juntunen
nch master
> > in repository
> > https://gitbox.apache.org/repos/asf/commons-configuration.git
> >
> >
> > The following commit(s) were added to refs/heads/master by this push:
> > new 2e39ef6b fixing binary incompatibilities with v2.7
> > 2e39ef6b is des
Hello,
All planned changes for commons-configuration 2.8.0 are now in master
so I am going to start preparing RC1. I haven't released this project
before so I'm hoping that I won't run into any issues and will be able
to have an RC out to vote on within the next few days.
Let me know if you have
I'm glad I asked this question :-) Bruno actually submitted a PR with
support for both the old and new namespaces [1] but we decided not to
go with it since it felt like too much to support both versions of the
API. However, this discussion is making me rethink that choice. For
one, dropping
Hello,
Good discussion here! This is great!
I lost track of what the overall goal here is while reading through
the conversation. The goal of NUMBERS-186 is to "allow operations to
be performed on lists of complex numbers". My first thought when
looking at this is "how are we going to represent
Hello,
I agree that this looks interesting. I personally would like to see
the following before weighing in on whether or not to include it in
commons:
1. A list of use cases where this data structure would be potentially
more performant or useful than existing data structures.
2. A set of
Hello,
We are slowly getting closer to a 2.8.0 release for
commons-configuration. One remaining item on the list is a PR [1] for
bumping the com.sun.mail:mailapi optional dependency from 1.6.7 to
2.0.1. I'd like to get community input on this change since it
involves a package name change in the
+1 as well.
Thanks, Alex! I have spent quite a bit of time refreshing the Travis
build page over and over waiting for my builds to start, so this will
be a welcome change :-)
-Matt J
On Thu, May 26, 2022 at 3:55 PM Bruno Kinoshita wrote:
>
> +1
>
> Thanks Alex!
>
> On Fri, 27 May 2022, 3:13 am
Please hold off on an RC. I should be able to address a specific issue over
> the weekend. Contact me on the private PMC list if you have any questions.
>
> Gary
>
> On Mon, May 9, 2022, 22:50 Matt Juntunen wrote:
>
> > Hello,
> >
> > I'm getting ready t
Congrats, guys! Well earned.
-Matt J
On Thu, May 19, 2022 at 7:38 AM Gary Lucas wrote:
>
> My next step will be to update the demonstration code from the
> Gridfour software package to use the new API. I'm also going to update the
> article on Elevation GeoTIFFs and Shaded Relief Rendering
>
Hello,
I've made a new PR [1] for CONFIGURATION-753 as part of my
preparations for the next release. I'd like to get another pair of
eyes on it if possible since it adds to the public API. The primary
cause of the issue is that DefaultConversionHandler and
ConfigurationInterpolator use different
Hello.
- Signatures and hashes look good on distribution and maven repo.
- Builds with "maven clean install site" from source distribution with
Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Maven home: /home/matt/tools/maven/apache-maven-3.8.4
Java version: 11.0.14.1, vendor:
Hello,
I'm getting ready to create the commons-configuration 2.8.0 release
and am currently trying to clear some of the outstanding GitHub PRs.
Are there any out of the current set of PRs that we definitely do or
do not want to include in 2.8.0?
Regards,
Matt J
Sounds reasonable to me. Are there any arguments against this change
other than the fact that it is not a japicmp default setting?
-Matt J
On Mon, May 9, 2022 at 8:59 AM Alex Herbert wrote:
>
> I would like to change some current interface methods in Commons RNG to
> have a default
Hello,
I've created a PR with a fix for that test. However, I'm not familiar
enough with the tar format to know if this is all that's needed or if
there is a deeper issue that needs to be addressed.
Regards,
Matt J
On Thu, May 5, 2022 at 8:41 PM Gary Gregory wrote:
>
> Hi All,
>
> I discovered
Hello,
I've created a PR[1] for GEOMETRY-147, adding line/ray intersection
methods to the BoundsXD classes, which are axis-aligned bounding
boxes. I'm picturing this being useful when raycasting against data
structures that use these bounding boxes, such as quadtrees, octrees,
and bounding volume
Hi Matt,
This is quite timely since I've spent the past week researching
frameworks to modularize a monolithic application at my day job into
separate components/plugins. Everything I've looked at so far is
larger and more complicated than I need (e.g. OSGi, Spring, etc) so I
was seriously
Hi Sebb,
Yep, geometry is still using Travis. I've never used GitHub Actions so
I'm not sure what it's capable of. Are there any specific features it
provides that are driving the migration to it? Or is it more a matter
of community preference? Either way is fine, I'm just curious.
Regards,
Matt
there are no objections to the current
PointMap/Set PR, I'm going to go ahead and merge it in and then
continue on with the closest point/farthest point API (GEOMETRY-146).
Regards,
Matt
On Wed, Mar 23, 2022 at 12:58 PM Gilles Sadowski wrote:
>
> Hi.
>
> Le mer. 23 mars 2022 à 03:27, M
al logic that could be built on top of
PointMap/Set, probably using the distance query methods in
GEOMETRY-146. Do you have a use case in mind here?
Regards,
Matt
On Tue, Mar 22, 2022 at 1:05 PM Gilles Sadowski wrote:
>
> Le mar. 22 mars 2022 à 14:46, Matt Juntunen
> a écrit :
Hello,
Unless there are any other comments on the PR, I'm going to plan on
merging it into master within the next couple of days.
Regards,
Matt
On Sun, Mar 20, 2022 at 11:39 AM Matt Juntunen
wrote:
>
> Hi Eric,
>
> > Would Java’s Map.entrySet provide the “getEntry” typ
data structure. The
PointMap.getEntry() method currently in the PR avoids this iteration
requirement.
Regards,
Matt
On Sun, Mar 20, 2022 at 9:13 AM Eric Bresie wrote:
>
>
>
>
> On March 14, 2022 at 10:19:14 AM CDT, Matt Juntunen
> wrote:
>
> I'm a little bit confused: Isn't
() is the
only method available to modify a TreeMap entry (outside of using the
entrySet).
Let me know what you think.
Regards,
Matt
[1] https://github.com/apache/commons-geometry/pull/194
On Wed, Mar 16, 2022 at 12:30 PM Gilles Sadowski wrote:
>
> Hi.
>
> Le mer. 16 mars 2022 à 15:42, M
"put" method on the underlying map when "setValue" is called.
Option #2 seems less than ideal so unless there is another approach
that I'm missing, I vote for #1.
Regards,
Matt
On Wed, Mar 16, 2022 at 9:48 AM Gilles Sadowski wrote:
>
> Hi.
>
> Le mer. 16 mars 2022 à 03
if this will have an impact on performance.
> > I'll try reducing the API as you suggest and include it in the PR if
> > it doesn't make a difference in performance.
> >
> > Do you prefer the "get" verb over "resolve",
>
> Yes (I'm missing
g over the whole set, why would
one want to start from some particular point?).
Could you post this comment on the JIRA issue and we can continue the
discussion there?
Regards,
Matt
On Sun, Mar 13, 2022 at 11:25 AM Gilles Sadowski wrote:
>
> Hello Matt.
>
>
ng implemented in a follow-up issue. [1]
Regards,
Matt
[1] https://issues.apache.org/jira/browse/GEOMETRY-146
On Sat, Mar 12, 2022 at 10:36 AM Gilles Sadowski wrote:
>
> Hello.
>
> Le ven. 11 mars 2022 à 16:18, Matt Juntunen
> a écrit :
> >
> > Hello,
> &g
else that we should plan on for 1.1?
Regards,
Matt Juntunen
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
t, or null if not found
Map.Entry resolveEntry(P pt);
}
PointSet {
// return the key corresponding to pt, or null if not found
P resolve(P pt);
}
Reviews and comments are welcome.
Regards,
Matt Juntunen
[1] https://github.com/apache/commons-geometry/pull/194
[2] https://issues.apache.org/jir
I just added a similar placeholder issue for geometry:
https://issues.apache.org/jira/browse/GEOMETRY-145. I hope those are
the kinds of ideas we're going for here.
Regards,
Matt J
On Wed, Feb 23, 2022 at 12:05 PM Gilles Sadowski wrote:
>
> Ping.
>
> Nothing for "Geometry", "Statistics", ...
wrote:
>
> Hello.
>
> Le lun. 17 janv. 2022 à 14:16, Matt Juntunen
> a écrit :
> >
> > Hi Gilles,
> >
> > The main things I want to do on the hull module are
> > - Review the public API to see if any changes need to be made. (ex:
> > make AklToussa
Hi Gilles,
The main things I want to do on the hull module are
- Review the public API to see if any changes need to be made. (ex:
make AklToussaintHeuristic internal)
- Add QuickHull implementations for 2D/3D (GEOMETRY-110). This is
currently blocked due to the need for a PointMap
If the functionality is mature, I would vote for a 1.0 release. YOLO :-)
-Matt J
On Tue, Sep 14, 2021 at 11:13 AM Alex Herbert wrote:
>
> The statistics component is a candidate for a release.
>
> The statistics distributions module contains mature functionality
> ported from CM. The dependency
Builds with JDK 8 and 11 from source distribution and tag.
Checksums and signatures are good.
Tag is good.
[X] +1 Release these artifacts
Regards,
Matt J
On Thu, Sep 9, 2021 at 6:45 AM Gilles Sadowski wrote:
>
> Le mer. 8 sept. 2021 à 12:01, Alex Herbert a écrit
> :
> >
> > We have fixed
: /home/matt/tools/maven/apache-maven-3.5.3
Java version: 11.0.2, vendor: Oracle Corporation
Java home: /home/matt/lang/java/jdk-11.0.2
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-81-generic", arch: "amd64", family: "unix&qu
The windows build is fixed. Before I cast my vote, can someone remind
me what to do to verify the nexus artifacts?
Regards,
Matt J
On Mon, Sep 6, 2021 at 6:09 AM Alex Herbert wrote:
>
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons RNG 1.3 was
rbert wrote:
>
> Hi,
>
> On Sun, 5 Sept 2021 at 13:51, Matt Juntunen
> wrote:
>
>
> > [ERROR] Failed to execute goal
> > org.apache.rat:apache-rat-plugin:0.13:check (rat-check) on project
> > commons-rng-parent: Too many files with unapproved license: 1 See RA
I ran into an error building from the source distribution on Windows.
C:\Users\matt\projects\commons-rng-1.4-src\commons-rng-1.4-src> mvn -v
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\Users\matt\tools\apache-maven-3.6.3-bin\apache-maven-3.6.3\bin\..
Java version:
I second this congratulations. Thank you for all of your hard work!
-Matt J
On Fri, Sep 3, 2021 at 8:46 AM Gary Gregory wrote:
>
> If only quantity was equivalent to quality ;-)
>
> Thanks Bernd :-)
>
> Gary
>
>
> On Tue, Aug 31, 2021, 11:44 Bernd Eckenfels wrote:
>
> > Congrats Gary to be
https://commons.apache.org/proper/commons-geometry/
Distribution packages can be downloaded from
http://commons.apache.org/proper/commons-geometry/download_geometry.cgi
Matt Juntunen,
Apache Commons Team
-
To unsubscribe, e-mail:
This vote passes with the following +1s.
- Alex Herbert (binding)
- Gilles Sadowski (binding)
- Matt Juntunen (binding)
I will work on getting the release out later tonight.
Regards,
Matt J
On Tue, Aug 17, 2021 at 3:22 AM Matt Juntunen wrote:
>
> We have completed initial developmen
For the record, here is my +1 vote.
-Matt
On Fri, Aug 20, 2021 at 4:18 PM Matt Juntunen wrote:
>
> This is good to know. Thanks for looking into this, Alex!
> -Matt
>
> On Thu, Aug 19, 2021 at 1:45 PM Alex Herbert wrote:
> >
> > It is definitely platform dependent.
de a method. So this is a bug in the javadoc tool on the
> linux platform. This explains why I did not see it on another build env.
> Because it is not a javadoc issue but an issue with the javadoc tool.
>
> If I run this with JDK 8 (1.8.0_241) on the same linux machine then I do
> no
The warnings about the unknown references seem to be caused by using
the @value tag to reference the value of a private constant. In my
experience, they only appear on JDK 8 and not 11+. I consider this
usage worth the warning since it ensures that the value given in the
docs actually matches
channels.
Regards,
Matt J
[1] https://dist.apache.org/repos/dist/release/commons/rng
[2] https://archive.apache.org/dist/commons/rng/binaries/
On Wed, Aug 18, 2021 at 8:10 AM Gilles Sadowski wrote:
>
> Le mer. 18 août 2021 à 01:47, Matt Juntunen
> a écrit :
> >
> > I agree. So,
I agree. So, where does this leave us for this RC?
-Matt
On Tue, Aug 17, 2021 at 5:48 PM Gilles Sadowski wrote:
>
> Hello.
>
> IIUC the binaries are for "convenience" (although it is certainly *more*
> convenient to rely on ivy/maven/whatever), and there is no mandatory
> contents.
> Hence I
I agree that this issue should be addressed. However, is this
something that needs to be done for this release, especially
considering that this is a long-standing issue and the documentation
in question is accessible in other locations?
Regards,
Matt J
On Tue, Aug 17, 2021 at 10:47 AM Alex
vote will close no sooner than 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,
Matt Juntunen,
Release Manager (using key 7DD53AEFEDF1C3D392B51EBE346F4FCECFB70B1A)
For following is in
I'm cancelling this vote again to address some of the issues that Alex
found, particularly the method naming convention issue.
Alex,
The behavior you described for the AbstractNode.depth() method is as
designed. It is not sufficient for a node to not have a parent in
order to be considered a root
N/A
RAT Report:
https://home.apache.org/~mattjuntunen/commons-geometry-1.0-RC3-site/rat-report.html
KEYS:
https://www.apache.org/dist/commons/KEYS
Please review the release candidate and vote.
This vote will close no sooner than 72 hours from now.
[ ] +1 Release these artifacts
[ ] +0 OK, bu
In addition to the issues that Alex found, I also noticed that the
commons-geometry-io-euclidean module was completely missing NOTICE and
LICENSE files. So, I'm going to cancel this vote and try again with
RC2.
Unless someone thinks it is a blocker, I'm going to defer any changes
related to the
and let you know if there are any
> further issues.
>
> Alex
>
>
>
> On Thu, 12 Aug 2021 at 16:41, Matt Juntunen
> wrote:
>
> > We have completed initial development work on Apache Commons Geometry,
> > so I would like to release Apache Commons Geometr
mmons-geometry-1.0-RC1-site/rat-report.html
KEYS:
https://www.apache.org/dist/commons/KEYS
Please review the release candidate and vote.
This vote will close no sooner than 72 hours from now.
[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppos
and (2) I have time now to do the
release but will most likely not later on. Please let me know if you
have any objections.
Regards,
Matt J
On Mon, Aug 2, 2021 at 7:25 AM Alex Herbert wrote:
>
> On Mon, 2 Aug 2021 at 02:32, Matt Juntunen
> wrote:
>
> >
> > > Then, as
6 Aug 2021 at 04:01, Gilles Sadowski wrote:
>
> > Le ven. 6 août 2021 à 04:01, Matt Juntunen a
> > écrit :
> > >
> > > Gilles,
> > >
> > > > I do _not_ ask any work to be done in order to complicate the release
> > > > process
Gilles,
> I do _not_ ask any work to be done in order to complicate the release
> process and/or review.
> My question was (cf. above and the other thread) whether singling out
> the "examples" module has any benefit (apart from saving a few bytes
> on Maven Central).
Yes, I believe it is
dowski wrote:
>
> > Le jeu. 5 août 2021 à 01:46, sebb a écrit :
> > >
> > > On Wed, 4 Aug 2021 at 13:38, Gilles Sadowski
> > wrote:
> > > >
> > > > Hi.
> > > >
> > > > Le mer. 4 août 2021 à 04:27, Matt Juntunen
>
Hello,
I apologize if this was resolved already and I missed it, but did we
land anywhere on the issue of whether or not to release binaries of
example code modules? I've included the example module binaries in
previous releases of numbers and geometry but I don't think that they
are actually
PM Alex Herbert wrote:
>
> On Sun, 1 Aug 2021 at 16:25, Gilles Sadowski wrote:
>
> > Hi.
> >
> > Le dim. 1 août 2021 à 02:57, Matt Juntunen a
> > écrit :
> > >
> > > Hello,
> > >
> > > I've addressed a few issues since I la
Hello,
I've addressed a few issues since I last proposed the commons-geometry
1.0 release, namely
- reducing the code smells in SonarCloud from 100+ to 8 (mostly by
clearing false positives) and
- removing use of checked exceptions in the IO modules (GEOMETRY-138).
I've also run fuzz testing
I've created GEOMETRY-138 [1] to track this and discuss the technical details.
-Matt
[1] https://issues.apache.org/jira/projects/GEOMETRY/issues/GEOMETRY-138
On Sat, Jul 24, 2021 at 12:41 PM Gilles Sadowski wrote:
>
> Le sam. 24 juil. 2021 à 18:25, Matt Juntunen
> a écrit :
> &
as runtime exceptions?
-Matt
On Sat, Jul 24, 2021 at 12:11 PM Gilles Sadowski wrote:
>
> Hi.
>
> Le sam. 24 juil. 2021 à 17:01, Matt Juntunen
> a écrit :
> >
> > Hello,
> >
> > > AFAICT, a precondition (max string length) is violated by the input: t
Hello,
> AFAICT, a precondition (max string length) is violated by the input: the
error is the caller's fault (either passing a too long string, or not having
set an appropriate upper bound).
This is not correct. This exception is thrown when a string token from
the input stream exceeds the
Alex, you are correct that a large number of the SonarQube issues can
be closed as "won't fix". I've opened INFRA-22130 [1] so I can get
admin access to make those changes.
Gilles, what do you picture as required in order for commons-geometry
to be released? Do you see fuzz-testing as a blocker?
-math examples, though.
-Matt J
On Tue, Jul 20, 2021 at 7:17 PM Gilles Sadowski wrote:
>
> Le mer. 21 juil. 2021 à 00:32, Matt Juntunen
> a écrit :
> >
> > > I completely agree. But how can we release (some official version of)
> > > the project as source withou
Geometry only uses rng for tests and performance benchmarks. Why do we
need to wait for the next release?
-Matt J
On Tue, Jul 20, 2021 at 12:56 PM Gilles Sadowski wrote:
>
> Hi.
>
> Le mar. 20 juil. 2021 à 04:01, Matt Juntunen
> a écrit :
> >
> > Hello,
> >
>
> I completely agree. But how can we release (some official version of)
> the project as source without also releasing the (convenience) binaries
> for everything?
I don't understand the question here. Wouldn't we just include all
example code in the source distribution but only create binaries
Hello,
commons-numbers 1.0 has now been released so I'd like to release
commons-geometry 1.0 soon. I was going to include the following
modules:
- commons-geometry-core
- commons-geometry-euclidean
- commons-geometry-spherical
- commons-geometry-io-core
- commons-geometry-io-euclidean
If there
ixed Fraction/BigFraction from(double, int) to support
Integer.MIN_VALUE as max denominator. Thanks to Alex Herbert.
Changes:
o NUMBERS-163: Combined "LinearCombination" and "Summation" into single
"Sum"
class. Thanks to Matt Juntunen.
o NUMBERS-164: A
1 - 100 of 263 matches
Mail list logo
