Hi Matt,
Inspected NOTICE, LICENSE, RELEASE-NOTES, and found no issues. Checked out
the tag, and `mvn clean test install site` passed with no errors.
The README is still showing 2.7 in the download instructions. I **think**
one of the preparation steps uses a release-plugin goal that
We have fixed quite a few bugs and added some significant enhancements
since Apache Commons Configuration 2.7 was released, so I would like
to release Apache Commons Configuration 2.8.
Apache Commons Configuration 2.8 RC1 is available for review here:
Sounds good. I've switched branches.
-Matt J
On Mon, Jun 20, 2022 at 10:23 AM Gary Gregory wrote:
>
> There is already a branch called "release". I think that using one branch
> per release is just clutter IMO.
>
> Gary
>
> On Sun, Jun 19, 2022, 23:13 wrote:
>
> > This is an automated email
Hello,
Thank you all for your feedback. What I'm hearing here is that binary
compatibility is vital between releases but source compatibility can
be changed with proper documentation and notifications. This is good
to know. For this release, I do not see a compelling reason to break
source
On Mon, 20 Jun 2022 at 15:26, Gary Gregory wrote:
>
> It is OK with me because _binary_ compatibility is what matters most and
> that is maintained.
>
> If you are compiling your code against a new version of a library, then
> changing source files is fair game IMO.
I agree that binary
It is OK with me because _binary_ compatibility is what matters most and
that is maintained.
If you are compiling your code against a new version of a library, then
changing source files is fair game IMO.
Gary
On Sun, Jun 19, 2022, 10:50 Matt Juntunen wrote:
> Hello,
>
> The throw clauses in
On Mon, 20 Jun 2022 at 14:35, Alex Remily wrote:
>
> Sebb,
>
> I cloned your repo and ran the dockerfile. Feedback:
>
> The Maven download link is broken. It appears Apache updated to 3.8.6 on
> the 17th. I think the 3.6.3 build is less likely (although still not
> certain--as you pointed out)
There is already a branch called "release". I think that using one branch
per release is just clutter IMO.
Gary
On Sun, Jun 19, 2022, 23:13 wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> mattjuntunen pushed a commit to branch 2.8.0-release
> in repository
>
Hello Gilles,
Thanks! I will start a new thread for float support.
Thanks
Sumanth
On Mon, Jun 20, 2022, 18:41 Gilles Sadowski wrote
>
> > Also, should we add support for float data type for complex numbers?
>
> In the "dev" ML, we customarily aim at focussing each discussion,
> Thus could
Sebb,
I cloned your repo and ran the dockerfile. Feedback:
The Maven download link is broken. It appears Apache updated to 3.8.6 on
the 17th. I think the 3.6.3 build is less likely (although still not
certain--as you pointed out) to get overwritten.
RUN wget
Hello Sumanth.
Le lun. 20 juin 2022 à 07:05, Sumanth Rajkumar
a écrit :
>
> [...]
>
> Also, should we add support for float data type for complex numbers?
In the "dev" ML, we customarily aim at focussing each discussion, so
that people can easily decide (ideally, from the "Subject:" line) if
Hello.
Le lun. 20 juin 2022 à 04:25, Matt Juntunen
a écrit :
>
> 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
I think there used to be a page listing what changes were allowed when
changing major, minor and patch version numbers.
This may have been in the Wiki rather than the main website.
I could not find it just now, but have not spent much time looking for it.
If/when it is found, it probably needs to
BTW, speaking of wrapping more OpenSSL crypto functions, just came about this
research project from Tomcat for using Panama FFI as a OpenSSL wrapper
technology: that should work faster, safer and especially without native
compiles!
https://github.com/rmaucher/openssl-panama-foreign
Gruss
14 matches
Mail list logo
