+1
Aaron
On Thu, 16 Apr 2020 at 05:32, Werner Keil wrote:
> +1
>
> Werner
>
>
>
>
> On Thu, Apr 16, 2020 at 11:29 AM P. Ottlinger
> wrote:
>
> > Am 16.04.20 um 11:28 schrieb P. Ottlinger:
> > > Hi *,
> > >
> > > following our discussions in January and February 2020 I propose to
> > >
Since the last board report, 0.4-incubating was released. (That is a
noteworthy accomplishment!)
Aaron
On Thu, 16 Jan 2020 at 17:36, P. Ottlinger wrote:
> Hi guys,
>
> anything noteworthy to report?
>
> The discussion I tried to start about the future of Tamaya did not yield
> any results yet
I believe the extension modules are all set -- they were part of the 0.4
release and they have been incremented to 0.5-incubating-SNAPSHOT. But the
sandbox code should definitely be adjusted:
https://github.com/apache/incubator-tamaya-sandbox/pull/32
Aaron
On Tue, 31 Dec 2019 at 08:22, P.
This is great news. Thanks for all your work on this.
Aaron
On Mon, 11 Nov 2019 at 14:19, Anatole Tresch wrote:
> Hi Guys
>
> our release is basically done. The only thing *left over is updating the
> homepage* and *preparing the master for the next snapshot*
> 0.5-incubating-SNAPSHOT
>
> But
+1
I verified the signatures and hashes for API/Core and Extensions artifacts
(Note: in the future, you don't need to include *all of* md5, sha1, sha256
and sha512; just including one of sha512 or sha256 will suffice)
The core and ext code builds and all the tests pass.
I have some downstream
+1
I verified the signatures and hashes for the api/core release as well as
for the extensions.
The code built correctly for me using Java 11 on a Mac:
$ java -version
java version "11.0.3" 2019-04-16 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.3+12-LTS)
Java HotSpot(TM) 64-Bit Server
Thanks so much for cutting the second release candidate. The source looks
great (no SNAPSHOT dependencies); I was able to successfully compile and
test the code. And I was able to successfully use the CDI and Microprofile
extensions in an external project.
I'd give a +1, but there are two issues
sed,
> or should it work without Snapshot in staging?
>
> Aaron Coburn schrieb am Mo., 26. Aug. 2019,
> 17:37:
>
> > -1 (non-binding)
> >
> > The microprofile extension depends on the tamaya-api
> > 0.4-incubating-SNAPSHOT artifact, which wi
-1 (non-binding)
The microprofile extension depends on the tamaya-api
0.4-incubating-SNAPSHOT artifact, which will cause problems when trying to
use that (and that is the artifact I am most interested in using)
+1
I will be happy to test any release candidates.
On Mon, Aug 19, 2019, 17:06 Werner Keil wrote:
> +1
>
> Werner
>
>
>
> On Mon, Aug 19, 2019 at 10:13 PM William Lieurance <
> william.lieura...@namikoda.com> wrote:
>
> > Please do. Let me know if I can be of any help.
> >
> > Sent from a tiny
Yes, let's definitely cut a release. +1
Cheers,
Aaron
On Tue, 16 Jul 2019 at 05:16, Anatole Tresch wrote:
> Hi Guys
>
> is there anything that speaks against building a new release? If no, we
> should build one.
>
> J Anatole
>
Hi All,
it seems that the sonar integration for the core tamaya repository has been
removed. Were those commits reverted? Or maybe a force-push? A number of
the recent changes seem no longer to be present.
Aaron
I would be interested in joining. 5/27 at the time you suggested works for
me.
Cheers, Aaron
On Mon, 13 May 2019 at 15:59, P. Ottlinger wrote:
> Am 13.05.19 um 21:51 schrieb Oliver B. Fischer:
> > Monday and Tuesday I will be in St. Petersburg on vacation. ;-)
>
> what about:
>
> 2019-05-27
I find Sonar to be useful, but I also take those analyses with a
significant grain of salt.
First of all, whether a given commit will pass or fail the sonar analysis
is a bit of a moving target, and it's also not easy to reproducible
locally. This means there is a bit of guesswork involved if
[
https://issues.apache.org/jira/browse/TAMAYA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn resolved TAMAYA-387.
-
Resolution: Fixed
The checkstyle updates have been applied to the various repositories
[
https://issues.apache.org/jira/browse/TAMAYA-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16824522#comment-16824522
]
Aaron Coburn commented on TAMAYA-386:
-
I saw this issue with vertx, too. Currently, that example
[
https://issues.apache.org/jira/browse/TAMAYA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn reassigned TAMAYA-387:
---
Assignee: Aaron Coburn
> Upgrade checkstyle vers
Aaron Coburn created TAMAYA-387:
---
Summary: Upgrade checkstyle version
Key: TAMAYA-387
URL: https://issues.apache.org/jira/browse/TAMAYA-387
Project: Tamaya
Issue Type: Improvement
There are two ways (that I know of) to add these credentials to the Travis
configuration without including them as plain text. I take it that you've
already generated a token from the sonar cloud interface. For both
approaches, you'll need to add this to the .travis.yml file:
addons:
integration is set up, that should be able to generate reports
identifying all the unused variables.
Aaron
On Mon, Mar 25, 2019 at 4:39 PM P. Ottlinger wrote:
> Hi,
>
> Am 22.03.19 um 05:08 schrieb Aaron Coburn:
> > Which modules don't have checkstyle enabled?
>
> Not su
[
https://issues.apache.org/jira/browse/TAMAYA-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn resolved TAMAYA-385.
-
Resolution: Fixed
Fix Version/s: 0.4-incubating
> Update to latest RAT 0
[
https://issues.apache.org/jira/browse/TAMAYA-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn updated TAMAYA-216:
Fix Version/s: 0.4-incubating
> Migrate all tests in module extensi
[
https://issues.apache.org/jira/browse/TAMAYA-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn closed TAMAYA-349.
---
Assignee: Aaron Coburn
> Ensure that Tamaya builds properly on JDK
[
https://issues.apache.org/jira/browse/TAMAYA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn closed TAMAYA-379.
---
> Enable checkstyle validation
>
>
> Key
[
https://issues.apache.org/jira/browse/TAMAYA-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn resolved TAMAYA-215.
-
Resolution: Fixed
Fix Version/s: 0.4-incubating
Test assertions have been completely
[
https://issues.apache.org/jira/browse/TAMAYA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn resolved TAMAYA-219.
-
Resolution: Fixed
Assignee: Aaron Coburn
Fix Version/s: 0.4-incubating
[
https://issues.apache.org/jira/browse/TAMAYA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776094#comment-16776094
]
Aaron Coburn commented on TAMAYA-378:
-
In one of the recent commits to tamaya-sandbox (especially
+1
Thanks
On Sun, Feb 3, 2019 at 2:40 AM Anatole Tresch wrote:
> +1 Thanks, Phil
>
> Am So., 27. Jan. 2019, 22:12 hat P. Ottlinger
> geschrieben:
>
> > Hi everybody,
> >
> > I'd love to do the report :-)
> >
> > * 2 new contributors added, which rocks.
> > * homepage overhaul
> > * working on
[
https://issues.apache.org/jira/browse/TAMAYA-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756435#comment-16756435
]
Aaron Coburn commented on TAMAYA-217:
-
All of the tests in the core module have been migrated
[
https://issues.apache.org/jira/browse/TAMAYA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn resolved TAMAYA-380.
-
Resolution: Fixed
> Misspelled class name in jsr382 mod
Aaron Coburn created TAMAYA-380:
---
Summary: Misspelled class name in jsr382 module
Key: TAMAYA-380
URL: https://issues.apache.org/jira/browse/TAMAYA-380
Project: Tamaya
Issue Type: Improvement
:10 Uhr schrieb P. Ottlinger <
> pottlin...@apache.org>:
>
>> Am 17.01.19 um 21:09 schrieb Aaron Coburn:
>>> I've noticed that for any Github activity on tamaya-extensions and
>> tamaya-sandbox (pull requests, comments, etc), messages are sent to the dev@
>
Aaron Coburn created TAMAYA-379:
---
Summary: Enable checkstyle validation
Key: TAMAYA-379
URL: https://issues.apache.org/jira/browse/TAMAYA-379
Project: Tamaya
Issue Type: Improvement
um 17:02 schrieb Aaron Coburn:
>> What would you all think about adjusting the maven configuration to have
>> checkstyle run on each build? Initially, it might make sense to just report
>> the errors rather than failing an entire build because of them. I can supply
>&g
Hi All,
I've noticed that for any Github activity on tamaya-extensions and
tamaya-sandbox (pull requests, comments, etc), messages are sent to the dev@
list, but that doesn't seem to apply to activity on the main tamaya repository.
Is there a missing part of the integration? Maybe something
build because of them. I can supply a PR
for this.
Best,
Aaron
> On Jan 16, 2019, at 2:57 PM, P. Ottlinger wrote:
>
> Dear Aaron,
>
> Am 16.01.19 um 15:40 schrieb Aaron Coburn:
>> https://github.com/apache/incubator-tamaya/pull/32
>> https://github.com/apache/incubato
Hi All,
There is a quartet of Jira issues related to consolidating the test assertion
code so that AssertJ is used (TAMAYA-216, TAMAYA-217, TAMAYA-218 and
TAMAYA-219). At present, there is a combination of AssertJ, JUnit and Hamcrest
in use throughout the tests. I have three open pull requests
[
https://issues.apache.org/jira/browse/TAMAYA-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn resolved TAMAYA-364.
-
Resolution: Fixed
> Travis-CI build environme
I agree with ajs6f. Given that we're still pre-1.0, this is definitely the time
to make any API changes. I also think that reducing the API footprint is a good
direction to be going in.
That is, I would be in favor of keeping these API changes.
Aaron
> On Jan 13, 2019, at 4:35 PM, ajs6f
[
https://issues.apache.org/jira/browse/TAMAYA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739505#comment-16739505
]
Aaron Coburn commented on TAMAYA-219:
-
Once all of the assertj-related Pull Requests are merged
[
https://issues.apache.org/jira/browse/TAMAYA-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736263#comment-16736263
]
Aaron Coburn commented on TAMAYA-154:
-
I believe this issue can be marked as resolved.
> Fix java
> as I upgraded jbake I'm keen to publish the latest changes /including
> the new start page & teasers/
> any objections?
No objections here.
> To my mind we should publish the page independent of the project/release
> status.
+1
Cheers, Aaron
[
https://issues.apache.org/jira/browse/TAMAYA-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn resolved TAMAYA-331.
-
Resolution: Fixed
All of the core/extension/sandbox modules have correct Automatic-Module-Name
Hi All,
I agree that the next steps here should result in a release. I am eager to make
use of the new features and bug fixes that are currently in the various master
branches. I also have some time in the next few weeks to help move this forward.
Are there particular tasks or JIRA issues that
Hi,
I think someone with admin rights will need to cancel the current Jenkins build
for the extensions repository. It's been stuck since 12/15:
https://builds.apache.org/job/Tamaya-Extensions-Master/
> On Dec 16, 2018, at 12:46 PM, Anatole Tresch wrote:
>
> Hi Guys
>
> I will fix the
+1 for migrating. Thanks for moving this forward.
Aaron
> On Dec 10, 2018, at 3:00 PM, Werner Keil wrote:
>
> +1 for moving, seems the standard way for all repositories, so better
> migrate.
>
> Werner
>
>
>
> On Mon, Dec 10, 2018 at 8:59 PM P. Ottlinger wrote:
>
>> Am 08.12.18 um 20:36
Aaron Coburn created TAMAYA-364:
---
Summary: Travis-CI build environments
Key: TAMAYA-364
URL: https://issues.apache.org/jira/browse/TAMAYA-364
Project: Tamaya
Issue Type: Improvement
Aaron Coburn created TAMAYA-363:
---
Summary: extraneous CORBA import
Key: TAMAYA-363
URL: https://issues.apache.org/jira/browse/TAMAYA-363
Project: Tamaya
Issue Type: Improvement
Aaron Coburn created TAMAYA-362:
---
Summary: Configuration::getSnapshot not implemented in some
extension modules
Key: TAMAYA-362
URL: https://issues.apache.org/jira/browse/TAMAYA-362
Project: Tamaya
Aaron Coburn created TAMAYA-361:
---
Summary: Findbugs version
Key: TAMAYA-361
URL: https://issues.apache.org/jira/browse/TAMAYA-361
Project: Tamaya
Issue Type: Improvement
Components
Hi,
I have an application that uses the 0.3-incubating version of Tamaya (just the
tamaya-api and tamaya-core artifacts), and simply incrementing to
0.4-incubating-SNAPSHOT (based on a local build from the current master branch)
works great. Changing ConfigurationProvider.getConfiguration() to
[
https://issues.apache.org/jira/browse/TAMAYA-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn resolved TAMAYA-349.
-
Resolution: Fixed
> Ensure that Tamaya builds properly on JDK
[
https://issues.apache.org/jira/browse/TAMAYA-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn resolved TAMAYA-334.
-
Resolution: Fixed
> Update geronimo-annotation dependency to
Aaron Coburn created TAMAYA-349:
---
Summary: Ensure that Tamaya builds properly on JDK 11
Key: TAMAYA-349
URL: https://issues.apache.org/jira/browse/TAMAYA-349
Project: Tamaya
Issue Type
[
https://issues.apache.org/jira/browse/TAMAYA-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn reopened TAMAYA-331:
-
That is a good idea to cross check this with the JSR branch. I'm re-opening
this issue to help
[
https://issues.apache.org/jira/browse/TAMAYA-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn resolved TAMAYA-331.
-
Resolution: Fixed
Automatic-Module-Name metadata has been added to each subproject in tamaya
[
https://issues.apache.org/jira/browse/TAMAYA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn resolved TAMAYA-330.
-
Resolution: Fixed
> Make it possible to build Tamaya on JD
[
https://issues.apache.org/jira/browse/TAMAYA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454683#comment-16454683
]
Aaron Coburn commented on TAMAYA-330:
-
[~hugo.hirsch] there is one last PR related to this issue
[
https://issues.apache.org/jira/browse/TAMAYA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426219#comment-16426219
]
Aaron Coburn commented on TAMAYA-330:
-
[~hugo.hirsch] the tamaya and tamaya-extensions repositories
[
https://issues.apache.org/jira/browse/TAMAYA-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn resolved TAMAYA-334.
-
Resolution: Fixed
> Update geronimo-annotation dependency to
Hi,
> On Mar 19, 2018, at 4:50 PM, P. Ottlinger <pottlin...@apache.org> wrote:
>
> Am 06.03.2018 um 21:01 schrieb Aaron Coburn:
>> Travis-CI currently supports Java 9 builds, which would be simple to add to
>> the current .travis.yml configuration. It is possible to
[
https://issues.apache.org/jira/browse/TAMAYA-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn resolved TAMAYA-333.
-
Resolution: Fixed
> ::equals(Object) implementation should correctly handle null argume
[
https://issues.apache.org/jira/browse/TAMAYA-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Coburn resolved TAMAYA-332.
-
Resolution: Fixed
> beans.xml file is not in META-INF directory for microprofile extens
Aaron Coburn created TAMAYA-334:
---
Summary: Update geronimo-annotation dependency to 1.0
Key: TAMAYA-334
URL: https://issues.apache.org/jira/browse/TAMAYA-334
Project: Tamaya
Issue Type
Aaron Coburn created TAMAYA-333:
---
Summary: ::equals(Object) implementation should correctly handle
null arguments
Key: TAMAYA-333
URL: https://issues.apache.org/jira/browse/TAMAYA-333
Project: Tamaya
Aaron Coburn created TAMAYA-331:
---
Summary: Add Automatic-Module-Name metadata for use with JDK 9+
module system
Key: TAMAYA-331
URL: https://issues.apache.org/jira/browse/TAMAYA-331
Project: Tamaya
Aaron Coburn created TAMAYA-330:
---
Summary: Make it possible to build Tamaya on JDK 9+
Key: TAMAYA-330
URL: https://issues.apache.org/jira/browse/TAMAYA-330
Project: Tamaya
Issue Type
either or both of these items, though
I wasn't sure if you'd like to discuss either of these first.
Thanks,
Aaron Coburn
68 matches
Mail list logo
