Re: Tamaya 0.4-incubating almost released

This is super good news. Thanks, Anatole, for pushing this through, and thanks to everyone who helped get it out. :-D Sent from a tiny keyboard From: Anatole Tresch Sent: Monday, November 11, 2019 1:18:11 PM To: dev@tamaya.incubator.apache.org Subject: Tamaya

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC5

+1 from me as well. I verified that the code compiles cleanly and passes the same tests as it normally does. Signatures and checksums all match. Clearly we shouldn't publish md5s or sha1s, but I don't take a position on whether that should block this release. --William

Re: release it!

I'll certainly +1 a release now and also am in favor of more frequent releases in the future. Sent from a tiny keyboard From: P. Ottlinger Sent: Tuesday, July 16, 2019 5:17:48 PM To: dev@tamaya.incubator.apache.org Subject: Re: release it! Am 17.07.19 um 00:16

[jira] [Updated] (TAMAYA-394) Fix existing sonar warnings after integrating with SonarCloud

[ https://issues.apache.org/jira/browse/TAMAYA-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Lieurance updated TAMAYA-394: - Description: After integrating with SonarCloud fix all existing warnings/problems in all

[jira] [Closed] (TAMAYA-410) Update camel-core dependency past CVE-2019-0188

[ https://issues.apache.org/jira/browse/TAMAYA-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Lieurance closed TAMAYA-410. Resolution: Fixed > Update camel-core dependency past CVE-2019-0

[jira] [Created] (TAMAYA-410) Update camel-core dependency past CVE-2019-0188

William Lieurance created TAMAYA-410: Summary: Update camel-core dependency past CVE-2019-0188 Key: TAMAYA-410 URL: https://issues.apache.org/jira/browse/TAMAYA-410 Project: Tamaya Issue

[jira] [Closed] (TAMAYA-374) Asciidoc: Properties are not properly rendered to show Tamaya version

[ https://issues.apache.org/jira/browse/TAMAYA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Lieurance closed TAMAYA-374. Resolution: Fixed > Asciidoc: Properties are not properly rendered to show Tamaya vers

Re: Sonar integration and recent commits

It looks like 0ddb859d57c71515e417a33e77d69355c753bb9b ("Merged with master changes") didn't pick up the travis yaml changes. Git's CLI, and github's web as well, isn't great at showing all the three-way changes added in a merge commit. Do a `git diff 8bcf8106..d5d3b748` to see what got

Re: Returning to Tamaya

5/27 works. It's a holiday here in the states. :-) Sent from a tiny keyboard From: Aaron Coburn Sent: Monday, May 13, 2019 3:07:09 PM To: dev@tamaya.incubator.apache.org Subject: Re: Returning to Tamaya I would be interested in joining. 5/27 at the time you

Re: Returning to Tamaya

I would love to join a hangout about Tamaya. That time would work for me. Sent from a tiny keyboard From: P. Ottlinger Sent: Monday, May 13, 2019 2:35:48 PM To: dev@tamaya.incubator.apache.org Subject: Re: Returning to Tamaya Hi Oliver, Am 13.05.19 um 21:34

[jira] [Closed] (TAMAYA-391) Sandbox module not running with JDK12

[ https://issues.apache.org/jira/browse/TAMAYA-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Lieurance closed TAMAYA-391. Resolution: Fixed > Sandbox module not running with JD

[jira] [Commented] (TAMAYA-391) Sandbox module not running with JDK12

[ https://issues.apache.org/jira/browse/TAMAYA-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831472#comment-16831472 ] William Lieurance commented on TAMAYA-391: -- Master branch now has a green passing badge

Re: Question - should Sonar fail our builds?

Hi all, A thing I just discovered about the sonar integration we've got: if you open a pull request from a forked repo instead of a branch in the shared apache/incubator-tamaya* repo, sonarcube won't run and will, at this point, fail the build. That means that only folks who have access to

[jira] [Assigned] (TAMAYA-391) Sandbox module not running with JDK12

[ https://issues.apache.org/jira/browse/TAMAYA-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Lieurance reassigned TAMAYA-391: Assignee: William Lieurance > Sandbox module not running with JD

[jira] [Commented] (TAMAYA-391) Sandbox module not running with JDK12

[ https://issues.apache.org/jira/browse/TAMAYA-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831440#comment-16831440 ] William Lieurance commented on TAMAYA-391: -- Turns out openjdk 12 has changed the default value

[jira] [Assigned] (TAMAYA-382) Adapt download secton of webpage

[ https://issues.apache.org/jira/browse/TAMAYA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Lieurance reassigned TAMAYA-382: Assignee: William Lieurance > Adapt download secton of webp

[jira] [Assigned] (TAMAYA-374) Asciidoc: Properties are not properly rendered to show Tamaya version

[ https://issues.apache.org/jira/browse/TAMAYA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Lieurance reassigned TAMAYA-374: Assignee: William Lieurance > Asciidoc: Properties are not properly rende

[jira] [Closed] (TAMAYA-342) Webpage does not render version in Asciidoc page templates

[ https://issues.apache.org/jira/browse/TAMAYA-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Lieurance closed TAMAYA-342. Resolution: Duplicate TAMAYA-374 gets version references working everywhere I can find

[jira] [Commented] (TAMAYA-378) Clarify Property Key Resolution on Injection

[ https://issues.apache.org/jira/browse/TAMAYA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769818#comment-16769818 ] William Lieurance commented on TAMAYA-378: -- Oooh, I like that interface. :) > Clarify Prope

[jira] [Commented] (TAMAYA-378) Clarify Property Key Resolution on Injection

[ https://issues.apache.org/jira/browse/TAMAYA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749735#comment-16749735 ] William Lieurance commented on TAMAYA-378: -- I agree that a Class for KeyResolution makes it more

Re: API deprecation for ConfigOperator, ConfigQuery

I agree with this as well. It seems like a general improvement and I cannot imagine a later date being better than now to get this change in. Sent from a tiny keyboard From: Aaron Coburn Sent: Monday, January 14, 2019 9:36:04 AM To:

Re: Pitest failures in Extensions

It sure does. I've got 2 PRs that address that: https://github.com/apache/incubator-tamaya/pull/28 is the one you should merge first. It fixes an NPE thrown if EnumConverter hits a null value. https://github.com/apache/incubator-tamaya-extensions/pull/19 is the fix for the error you see in

Re: Sandbox build failure

Hi hi. I'm still seeing the same error the Phil posted, even after the ConfigurationData and daemon vs executor change got merged. The latest commit I see on incubator-tamaya-extensions master (3774a6c3f2c3a08379c49b2bd41fa0c434034b89) is still inconsistent in its use of

Re: RFC: Draft for report - will submit at 2018-11-06

a standstill) which nobody dares to make binding decisions before they delivered on those promises. Werner On Wed, Nov 7, 2018 at 6:51 PM William Lieurance < william.lieura...@namikoda.com> wrote: > *blush* I'm just happy to be able to help. > > In truth, I think once the s

Re: RFC: Draft for report - will submit at 2018-11-06

*blush* I'm just happy to be able to help. In truth, I think once the substantial api/spi changes that Anatole has mentioned for jsr382 (and I think I saw on a branch accidentally) go in, the biggest thing we are missing is breadth of documentation and even more examples. Our current answer of

Re: Important changes

Hi there, I took a stab at TAMAYA-355, the multi-value mapping ticket, and had a question. Anatole, you mention that there's somewhere in core that supports mapping that includes nested elements, but I can't find it. Where did you mean? I've got the json and yaml extensions found, but am

Re: Feedback needed

ursday, September 13, 2018 2:40 PM To: dev@tamaya.incubator.apache.org Subject: Re: Feedback needed OK, there was one number missing, it was https://issues.apache.org/jira/browse/TAMAYA-345 Am Do., 13. Sep. 2018 um 19:31 Uhr schrieb William Lieurance < william.lieura...@namikoda.com>: >

Re: Feedback needed

Which ticket are you pointing at? TAMAYA-34 looks pretty old. I'm guessing a typo there? Sent from a tiny keyboard From: Anatole Tresch Sent: Thursday, September 13, 2018 12:09:03 PM To: dev@tamaya.incubator.apache.org Subject: Feedback needed Hi Guys can

Re: Tamaya CDI question

Hi there, I've got some seemingly working code based on your branch at https://github.com/ajs6f/trellis-cassandra-webapp/compare/TamayaConfig...peculater:TamayaConfig . Take a look and tell me what you think. The problems I noticed are in two areas. The first one is the most frustrating to

Re: build failures / test failures and infra problems

Hey Phil. I actually submitted a PR to fix those sandbox test failures last week. https://github.com/apache/incubator-tamaya-sandbox/pull/7 should cover the metamodel sandbox changes that are needed after Anatole's logging commit. From: P. Ottlinger

Ignored test on EnvironmentPropertySourceTest

Phil pointed out very reasonably that I had ignored a test at https://github.com/apache/incubator-tamaya/blob/ab914033ac5066a0577169a6859911299689ea9a/code/spi-support/src/test/java/org/apache/tamaya/spisupport/propertysource/EnvironmentPropertySourceTest.java#L106 that tried to read an

Re: [jira] [Commented] (TAMAYA-288) Ensure that a successful build of Tamaya API requires a unit test coverage of at least 50%

Ok, cool. I'm probably going to try to expand some test coverage of tamaya-extensions next (TAMAYA-291); I'll be sure to use AssertJ for that. Thanks! From: P. Ottlinger Sent: Sunday, February 25, 2018 2:05 PM To:

supportedFormats text consistency

Hi all, I'm looking at the supportedFormats added by the converters in core. I note a lot of inconsistency in the text with most converters adding types with <> around them. For instance the LongConverter adds "" but the ShortConverter adds "short". The various date and duration converters

Re: Jenkins build became unstable: Tamaya-Extensions-Master #1365

I'm having a really hard time getting this to repeat on any of my test machines. It looks to happen after Weld has a problem undeploying and redeploying some archives. Anyone else able to get this to repeat? --William From: P. Ottlinger

[jira] [Created] (TAMAYA-329) PropertyConverterManager cannot box arrays of booleans

William Lieurance created TAMAYA-329: Summary: PropertyConverterManager cannot box arrays of booleans Key: TAMAYA-329 URL: https://issues.apache.org/jira/browse/TAMAYA-329 Project: Tamaya

[jira] [Created] (TAMAYA-328) Single apostrophe cannot be cast to Character with CharConverter

William Lieurance created TAMAYA-328: Summary: Single apostrophe cannot be cast to Character with CharConverter Key: TAMAYA-328 URL: https://issues.apache.org/jira/browse/TAMAYA-328 Project

BigInteger hex conversion

Hi devs, I noticed the other day that the BigInteger converter is doing its own parsing of hexadecimal strings at

[jira] [Created] (TAMAYA-327) Inconsistent signature for creating ConversionContext

William Lieurance created TAMAYA-327: Summary: Inconsistent signature for creating ConversionContext Key: TAMAYA-327 URL: https://issues.apache.org/jira/browse/TAMAYA-327 Project: Tamaya

[jira] [Updated] (TAMAYA-326) ServiceLoader picks second available service provider even if the ordinal is lower

[ https://issues.apache.org/jira/browse/TAMAYA-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Lieurance updated TAMAYA-326: - Description: While adding some test coverage on the api, I found

[jira] [Created] (TAMAYA-326) ServiceLoader picks second available service provider even if the ordinal is lower

William Lieurance created TAMAYA-326: Summary: ServiceLoader picks second available service provider even if the ordinal is lower Key: TAMAYA-326 URL: https://issues.apache.org/jira/browse/TAMAYA-326

[jira] [Commented] (TAMAYA-325) Integrate not yet finalized ConfigJSR-API via jitpack

[ https://issues.apache.org/jira/browse/TAMAYA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16338873#comment-16338873 ] William Lieurance commented on TAMAYA-325: -- Created pull request [https://github.com/apache

Re: configjsr branch not buildable in travis / other Travis builds are ok except CDI test failures in extensions

o: dev@tamaya.incubator.apache.org Subject: Re: configjsr branch not buildable in travis / other Travis builds are ok except CDI test failures in extensions Hi *, Am 21.01.2018 um 04:55 schrieb William Lieurance: > While I would definitely like to see javaconfig-api jars published correctly,

Re: configjsr branch not buildable in travis / other Travis builds are ok except CDI test failures in extensions

While I would definitely like to see javaconfig-api jars published correctly, as long as we're talking about bad workarounds I was able to get Anatole's branch built and tests passing using jitpack.io as a passthrough to their github repo. I'm not proud of it but I think it can get us moving

Re: Recent test failures with Extensions

the last couple months of archives is really informative. Thanks! William From: P. Ottlinger <pottlin...@apache.org> Sent: Saturday, January 20, 2018 2:38:28 PM To: William Lieurance Cc: dev@tamaya.incubator.apache.org Subject: Re: Recent test fa

[jira] [Commented] (TAMAYA-296) Update maven site plugins

[ https://issues.apache.org/jira/browse/TAMAYA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1652#comment-1652 ] William Lieurance commented on TAMAYA-296: -- Hey [~hugo.hirsch] I was able to get a clean site

Re: Recent test failures with Extensions

with some of the backlog. I've got a 2018 goal to contribute more to projects I like. Any places you'd recommend I start? --William From: P. Ottlinger <pottlin...@apache.org> Sent: Wednesday, January 17, 2018 3:55 PM To: William Lieurance C

Recent test failures with Extensions

to update my commit messages if I missed one. I also probably need to sign whatever contributor forms are relevant for this project. Thoughts? --William Lieurance 1. Example from yesterday: https://builds.apache.org/view/S-Z/view/Tamaya/job/Tamaya-Extensions-Master/1317/org.apache.tamaya.ext