Re: [NOTICE] Apache Tamaya is retiring - what next

Hi Tamaya is already marked retired. I am waiting for one of you to submit the request to infra to migrate the repos as mentioned previously John On Sun, May 10, 2020 at 16:34 P. Ottlinger wrote: > Hi Werner, > > as John already pointed out there should not be a big problem to keep > the name

[NOTICE] Apache Tamaya is retiring - what next

Hi all, Apache Tamaya has successfully completed incubation leading to their retirement from Apache. In the coming days, this mailing list and other mailing lists for the project will be marked read only. All repositories will be locked as well. I know there was an ask to move the repos back to

[VOTE] Retire Apache Tamaya

Hi all, The Apache Tamaya podling has voted to retire, with the plan to have a transfer of the source repos back to a privately managed Github project. This is now a call to vote to retire from the IPMC's perspective. Per [1] this is a lazy consensus vote, so I'll summarize it in 72 hours and do

Re: [VOTE] Retire Tamaya and migrate repositories to Github as they are

atole Tresch > * +1: William Lieurance > * +1: me > > Thanks, > Phil > > > Am 23.04.20 um 04:36 schrieb John D. Ament: > > Hi all > > > > Please note the mixed public/private lists. > > > > Looks like the vote passed, does that mean it's tim

Re: [VOTE] Retire Tamaya and migrate repositories to Github as they are

Hi all Please note the mixed public/private lists. Looks like the vote passed, does that mean it's time to move it to the IPMC to vote? Thanks, John On Thu, Apr 16, 2020 at 5:28 AM P. Ottlinger wrote: > Hi *, > > following our discussions in January and February 2020 I propose to > terminat

Tamaya's Future (was Re: Podling Tamaya Report Reminder - February 2020)

Hey guys I signed off on the report. I'd really like to ensure that you figure out what your path forward is going to be. Activity is low, there was a release started end of last year that it's not clear was ever finished up. If interest is low enough, moving to github is a fine approach.

Re: Incubator Clutch Analysis Job failed

Since the build was broken I'm not sure what I'm looking at right now unfortunately. On Tue, Sep 10, 2019, 21:20 Dave Fisher wrote: > Look at incubator.apache.org/clutch/tamaya.html > > Sent from my iPhone > > > On Sep 10, 2019, at 6:17 PM, John D. Ament > wro

Re: Incubator Clutch Analysis Job failed

I just made a small change to Tamaya's status page since some of the sections causing issues are out of date. One question - how were we planning to handle projects like Tamaya with multiple git repos? I put a link to the query on github that shows you all of their repos. John On Tue, Sep 10, 2

Re: Podling report due today

I'd strongly recommend that the podling seek more mentors, and perhaps figure out if they are actually going to be a viable Apache project. Tamaya has been incubating 2014-November, and hasn't had a release in 2 years, the most recent committer change came a very long time after the last change. T

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

I've signed off on the report. However, there were a lot of merge conflicts so if you could please double check. I'm concerned about the strength of the project. It's basically a 2 person team. What can we do to try to grow the community? John On Tue, Nov 6, 2018 at 5:36 PM P. Ottlinger wrot

Re: Tamaya CDI question

On Mon, Aug 27, 2018, 10:32 ajs6f wrote: > I'm afraid not-- I changed javax.enterprise.inject.spi.Extension to: > > # Register Tamaya to perform injection > org.apache.tamaya.cdi.TamayaCDIInjectionExtension > org.apache.tamaya.cdi.TamayaSEInjectionExtension > > and now no extension from Tamaya is

Re: Apache Trafodion becomes Top-Level Project - SD Times

The project very clearly understands the release model, and communicating developer discussions via email. However, unless we get more contributors I don't believe it's possible to graduate. John On Fri, Jan 12, 2018 at 1:57 PM Werner Keil wrote: > Wonder, when we might see this about Tamaya?

Re: MicroProfile 1.3 - any changes in Tamaya?

I suspect Tamaya already supports all of the features in MP Config 1.2. This release fixes the issue reported last release, where you were failing because of common sense converters. I would say try upgrading the pom and see if any tests fail. Would be happy to help you if you run into any issues

Re: [DISCUSS] Offering Tamaya as ConfigJSR reference Impl

On Mon, Nov 6, 2017 at 2:09 PM P. Ottlinger wrote: > Am 06.11.2017 um 13:27 schrieb Anatole Tresch: > >- Depending on we would agree to support also the ultimate step, I can > >discuss with the JSR EG that Tamaya might get THE official RI. > >- All our extensions and integrations woul

Re: Podling Report Reminder - November 2017

the report is now nearly past due. Anyone going to put one together? On 2017-10-31 17:05, Anatole Tresch wrote: > - ​0.4-SNAPSHOT features: Microprofile API Support > ​- Members are have joined the actual config JSR (me and John), depending > on the speed we might also implement this JSR in

Re: Podling Report Reminder - November 2017

BTW, ask and you shall receive... :-) On Sat, Oct 21, 2017 at 6:43 PM wrote: > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initial reminder to give you plenty of time to > prepare your quarterly board report. > > The board meetin

Re: report reminder working?

November is your next report. Dont worry i wont let you forget. https://whimsy.apache.org/roster/ppmc/tamaya On Oct 21, 2017 3:16 PM, "P. Ottlinger" wrote: > Am 21.10.2017 um 21:09 schrieb John D. Ament: > > When do you believe your report is due? > > mmmh - well

Re: report reminder working?

When do you believe your report is due? On Oct 21, 2017 2:41 PM, "P. Ottlinger" wrote: > Hi John, > > I seem to be missing your automatically generated reminder for the board > report? Is the script still working? > > Shouldn't we have got a reminder about reporting to the board? > > Thanks > Ph

Re: Microprofile TCK starts to look giid

Yes, those are the same tests failing from when I pushed my last commit [1]. We can safely ignore testAutoDiscoveredConverterNotAddedAutomatically, we'll be changing that test in MP Config Spec to avoid possible common sense conversion logic. [1]: https://github.com/apache/incubator-tamaya-sandbo

Re: MASTER BUILD BROKEN BECAUSE OF COVERAGE

ored. > I know in an ideal world we would do it but to do it it requires a log > of discipline. > > Oliver > > > > Am 01.10.17 um 19:52 schrieb P. Ottlinger: > > Am 01.10.2017 um 19:04 schrieb John D. Ament: > >> So it can be run but its not default. Do we h

Re: Anyone looking at this PR?

pinions on that? > I'm of the opinion that it helps gives projects more visibility. Although, the cut over is a bit of a hard one - we'd have to change all remotes. It also helps better communicate when changes are coming through. > > Thanks, > Phil > > Am 06.10.20

Re: Anyone looking at this PR?

7;s much more convenient. > > > > Any other opinions on that? > > > > Thanks, > > Phil > > > > Am 06.10.2017 um 02:47 schrieb John D. Ament: > > > Take a look at [1]. When I created the PR, the email sent included > > > instructions how

Re: Anyone looking at this PR?

On Thu, Oct 5, 2017 at 4:46 PM P. Ottlinger wrote: > Am 05.10.2017 um 01:56 schrieb John D. Ament: > > For Tamaya, the github repositories are read only mirrors. > > rofl - ok, let me rephrase my questions: > how can I deal with a github PR if I'm unable to accept it via

Re: Anyone looking at this PR?

For Tamaya, the github repositories are read only mirrors. John On Wed, Oct 4, 2017 at 5:37 PM P. Ottlinger wrote: > Am 04.10.2017 um 03:38 schrieb John D. Ament: > > Anyone in the incubator group has write access, the repo is listed on > your > > sources page. > >

Re: Anyone looking at this PR?

Anyone in the incubator group has write access, the repo is listed on your sources page. On Tue, Oct 3, 2017 at 4:23 PM P. Ottlinger wrote: > Am 03.10.2017 um 19:59 schrieb John D. Ament: > > It looks like some tests that were passing are now failing in the branch. > > Empty valu

Re: Anyone looking at this PR?

PM John D. Ament wrote: > At this point the PR doesn't compile. So not sure what to do. It seems > like Anatole's moved forward on it anyways. > > > On Sun, Oct 1, 2017 at 5:02 PM P. Ottlinger wrote: > >> Am 30.09.2017 um 23:13 schrieb Anatole Tresch: >

Re: Anyone looking at this PR?

At this point the PR doesn't compile. So not sure what to do. It seems like Anatole's moved forward on it anyways. On Sun, Oct 1, 2017 at 5:02 PM P. Ottlinger wrote: > Am 30.09.2017 um 23:13 schrieb Anatole Tresch: > > I shortly looked at it. It makes sense, so +1 to merge from my side...

Re: MASTER BUILD BROKEN BECAUSE OF COVERAGE

t; > Am 01.10.17 um 17:50 schrieb John D. Ament: > >> Does the profile that check for code coverage run locally? or can it only >> run in jenkins? >> >> On Sun, Oct 1, 2017 at 9:21 AM Oliver B. Fischer < >> o.b.fisc...@swe-blog.net> >> wrote: >>

Re: MASTER BUILD BROKEN BECAUSE OF COVERAGE

Does the profile that check for code coverage run locally? or can it only run in jenkins? On Sun, Oct 1, 2017 at 9:21 AM Oliver B. Fischer wrote: > Dear all, > > the test coverage of Tamya went down from 52 to 51 after merging the > Java 8 branch to master. I woulk like to ask the authors who co

Anyone looking at this PR?

https://github.com/apache/incubator-tamaya-sandbox/pull/1 Let me know if I should just merge it. John

Re: Handling Optional in Tamaya core?

;K1").get(); > >> String value2 = c.key("K2").getOrThrow(() -> new RuntimeException()); > >> String value3 = c.key("K3").getOrElse(() -> "DEFAULT") > >> String value4 = c.key("K4").map(v -> v).get() > >> > >

Planning to remove rosters from active podlings

All, This coming weekend (9/29) I plan to remove the roster sections from all podling status pages. Podling rosters are meant to be managed in Whimsy. The roster in the status page is redundant and end up out of sync. In place of the roster, I will be adding a link automatically to all podling

Handling Optional in Tamaya core?

Hi I was wondering, would it make sense for Tamaya to handle within its core usage of Optional? Its required by MP, however the code looks a bit disjointed in how it works. The method MicroprofileConfig.getOptionalValue looks elegant, but it seems there's no handling of the optional values prope

[jira] [Commented] (TAMAYA-260) Implement Microprofile.io Config API

[ https://issues.apache.org/jira/browse/TAMAYA-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174197#comment-16174197 ] John D. Ament commented on TAMAYA-260: -- https://github.com/eclipse/micropro

[jira] [Commented] (TAMAYA-260) Implement Microprofile.io Config API

[ https://issues.apache.org/jira/browse/TAMAYA-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174178#comment-16174178 ] John D. Ament commented on TAMAYA-260: -- I pushed up a PR that changes the strate

[jira] [Created] (TAMAYA-304) Service Loading should consider class's class loader

John D. Ament created TAMAYA-304: Summary: Service Loading should consider class's class loader Key: TAMAYA-304 URL: https://issues.apache.org/jira/browse/TAMAYA-304 Project: Tamaya

Upgrading Sandbox MicroProfile to 1.1?

Hi, I just tried to upgrade the Sandbox MP build to point to the released 1.1 spec. I see this compilation error, and was wondering if something changed in core? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile (default-compile) on project tamaya-microp

Re: 2017-09-18 hangout minutes

On Mon, Sep 18, 2017 at 4:04 PM P. Ottlinger wrote: > Hi * :-) > > PARTICIPANTS > Anatole, Oliver, Werner, Phil > > > AGENDA > > * Oliver: build problems, will try to integrate with Travis and file a > INFRA-ticket > > * Oliver: initiate a chat with John concerning graduation > > FYI - I'm waitin

Re: Scope of Tamaya 0.4

Oh, nevermind. Looks like you already had that on the java8 branch. On Wed, Aug 9, 2017 at 6:34 AM John D. Ament wrote: > I just pushed up a branch with MP support. TCK runs against Weld right > now (failing). Give it a shot, let me know if that helps can easily be > merged to ma

Re: Scope of Tamaya 0.4

I just pushed up a branch with MP support. TCK runs against Weld right now (failing). Give it a shot, let me know if that helps can easily be merged to master (but looks like its pointing to Tamaya 0.3 instead of 0.4?) John On Wed, Aug 9, 2017 at 6:19 AM Anatole Tresch wrote: > Basically a go

Re: changes in Jenkins - DONE

All, Our build jobs should be at https://builds.apache.org/view/S-Z/view/Tamaya/ John On Tue, Aug 1, 2017 at 4:47 PM Oliver B. Fischer wrote: > That is very pitty. Such things help us to organize our work. Do be > blocked here is not helpful. > > > Am 26.07.17 um 22:59 schrieb P. Ottlinger: >

[REMINDER] Policies around Publicity & Press

h any concerns. Regards, John D. Ament VP, Apache Incubator

Re: Podling Report Reminder - August 2017

On Wed, Jul 26, 2017 at 4:51 PM P. Ottlinger wrote: > Hi, > > I'd love to take of that - main objectives are: > > * Release of Tamaya Core 0.3 > * Release of Tamaya Extensions 0.3 - work in progress > > Now that it has 3 +1's on the incubator list, would be good if Oliver can wrap up that release

Re: Thoughts on releasing Tamaya API&Core and Tamaya Extensions

Merging them into a single repo would make sense. On Mon, Jul 17, 2017 at 2:42 AM P. Ottlinger wrote: > Hi, > > Am 16.07.2017 um 23:43 schrieb Oliver B. Fischer: > > Any objections? > > When we separated the repositories we had the discussion about why to > separate API/Core from Extensions

Dist Area permissions problem

All, Please be advised that the infra team is aware of a permission problem that is affecting podlings ability to write to the incubator dist area. This may cause you to be unable to create staged releases and promote those to the public mirrors. You can track the status in https://issues.apache

Re: [VOTE] Release of Apache Tamaya Extensions 0.3-incubating, Vote I

+1 to release Checked rat, verified signatures. On Tue, Jul 11, 2017 at 6:08 PM Oliver B. Fischer wrote: > Hi, > > I was running the needed tasks to get the 0.3-incubating release of > Apache Tamaya Extensions out. > The artifacts are deployed to Nexus [1] and releases [3]. > > The tag is avail

Re: Status of the IMPC voting on release 0.3 of API and CORE

You should be all set you only need 3 bindong +1s On Jun 18, 2017 4:28 PM, "Oliver B. Fischer" wrote: > Dear all, > > We have three binding +1s on the IPMC mailinglist. So we need on +1 more > to release 0.3 officially. > > Best, > > Oliver > > > -- > N Oliver B. Fischer > A Schönhauser Allee 64

Re: Draft of announcement mail to the IPMC - Invitation to edit

IMHO this is nice, but over kill. All you have to do is take the same release vote from https://lists.apache.org/thread.html/dce5a698f1d9731a7592d8b7e6bbac4620e86c885cf119080236599d@%3Cdev.tamaya.apache.org%3E and send that to general@incubator, removing the parts about nexus since that already wa

Re: 2017-06-12 hangout minutes

schrieb Oliver B. Fischer: > > Hi John, > > > > we and I do all the things here in our spare time between work, > > private life and other responsibilities. > > > > Isse should be created. > > > > Oliver > > > > > > Am 13.06.17 um 0

[DRAFT] What the new Status Pages potentially look like

All, We're piloting a new format for the podling status pages. Specifically, the current status page leaves a lot to be desired - it's basically crafted html, there's no structure and its hard to find missing items. The end goal is to have a web form editable in Whimsy, but until we get more inp

Re: 2017-06-12 hangout minutes

All, While the video chats have been useful from what I can tell, how do we get more of that communication to happen on list? I'll be honest, I feel a bit awkward over the release vote on general@incu. I think it's been out there a week now and seemingly no response from Oliver on it. The IPMC

Re: [Result] (was: Re: VOTE] Release of Apache Tamaya 0.3-incubating, Vote II) (second try)

Oliver, The vote on the podling is for review purposes only. You have to send a full vote thread to the general@incubator list with all of the details, similar to what Anatole did in the links I sent you. My +1 will carry with the vote. John On Sat, Jun 10, 2017 at 9:06 AM Oliver B. Fischer w

Re: Version 0.3 of API and Core have been released

Oliver, All releases are release candidates. If they fail, they get re-rolled. Personally, I hate when podlings present -rcX to the incubator. It's like they feel strongly they will fail so need a safety net. I will say that since the maven repository was already released, that may be an issue

Re: [Result] (was: Re: VOTE] Release of Apache Tamaya 0.3-incubating, Vote II)

On Mon, Jun 5, 2017 at 3:40 AM Oliver B. Fischer wrote: > [Result] (was: Re: VOTE] Release of Apache Tamaya 0.3-incubating, Vote II) > > Thank you for voting! > > X binding +1 votes (pmc): > - John D. Adment > - Philipp Ottlinger > - Werner Keil > > Y non-binding +1 votes: > - n/a > > Z -1 votes

Re: Website Jenkins Job

Err, so I just noticed the job doesn't do a check in. Is it supposed to? On Sat, Jun 3, 2017 at 11:20 AM John D. Ament wrote: > All, > > I worked with Infra to get jbake installed on our build nodes. I want to > mess with our site job to see if I can use it. If it w

Re: Build failed in Jenkins: Tamaya-Site-Master #491

I've disabled this job, was it out of date? On Sat, Jun 3, 2017 at 11:05 AM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > > -- > Started by user pottlinger > [Env

Website Jenkins Job

All, I worked with Infra to get jbake installed on our build nodes. I want to mess with our site job to see if I can use it. If it works, I'll commit changes to remove the jbake JARs. Any concerns? John

[jira] [Created] (TAMAYA-272) Move Tamaya in 5 minutes intro to home page

John D. Ament created TAMAYA-272: Summary: Move Tamaya in 5 minutes intro to home page Key: TAMAYA-272 URL: https://issues.apache.org/jira/browse/TAMAYA-272 Project: Tamaya Issue Type

[NOTICE] Managing Podling Rosters

Podlings, I wanted to raise a point to all, hence the direct emails. The Whimsy PMC has put together a roster tool for managing the committers in a podling. Rather than managing the committer list in your status file, this will keep track and make sure we list out everyone's valid IDs. If you h

Re: [Vote] webpage change - move to jbaked version?

+1 to do the switch. I actually worked with Gav a few weeks ago to create a jbake package for the build slaves. Still need to raise a PR to install that package on buildbot and jenkins. Once thats in, we should be able to even remove the local JARs. But that shouldn't be a blocker for this work

Re: VOTE] Release of Apache Tamaya 0.3-incubating, Vote II

+1 to release If you could please drop the other repos. On Sat, May 27, 2017 at 6:04 PM P. Ottlinger wrote: > Am 27.05.2017 um 23:54 schrieb Anatole Tresch: > > *Looking at Nexus I see multiple staging repos [1]:* > > > >- ​ > > > https://repository.apache.org/content/repositories/orgapache

Re: VOTE] Release of Apache Tamaya 0.3-incubating, Vote II

Oliver, Do you have checksum files? See also [1] John [1]: http://www.apache.org/dev/release-publishing.html#distribution_dist On Thu, May 25, 2017 at 4:35 PM Oliver B. Fischer wrote: > Hi, > > I was running the needed tasks to get the 0.3-incubating release of > Apache Tamaya out. > The arti

Re: [VOTE] Release of Apache Tamaya 0.3-incubating

-1: There's no cryptographic signature files for the .zip and .tar.gz files, which is required for the release. (it could be they just need to be staged) I see no other issues, so if those files can get staged I'll switch to a +1. FWIW I don't see those files in the maven staging repo, not sure

[DRAFT] Incubator PMC Board Report - May 2017

e out that rosters should be maintained in Whimsy going forward. A formal announcement should happen by ApacheCon. * Credits - Report Manager: John D. Ament -- Table of Contents BatchEE Blur Distributed

Re: Podling Report Reminder - May 2017

It seems no one has done this yet. Can someone do it tomorrow? If not, we'll need to report in June. On Tue, May 2, 2017 at 5:13 PM Oliver B. Fischer wrote: > Who would like to write our podling report? > > > Am 02.05.17 um 05:12 schrieb johndam...@apache.org: > > Dear podling, > > > > This ema

Re: Do we need a binary distribution?

Most maven projects I've seen provide two things: - The source distribution of the actual source code required to build the projects. - A link to a maven staging repository with artifacts staged to verify the binary output as well. When I look at what Tamaya's done, its a library publishing a bin

[jira] [Comment Edited] (TAMAYA-144) Ensure correct licensing for binary distribution

[ https://issues.apache.org/jira/browse/TAMAYA-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993769#comment-15993769 ] John D. Ament edited comment on TAMAYA-144 at 5/2/17 9:1

[jira] [Commented] (TAMAYA-144) Ensure correct licensing for binary distribution

[ https://issues.apache.org/jira/browse/TAMAYA-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993769#comment-15993769 ] John D. Ament commented on TAMAYA-144: -- [~o.b.fischer] The contents of the bi

[jira] [Commented] (TAMAYA-144) Ensure correct licensing for binary distribution

[ https://issues.apache.org/jira/browse/TAMAYA-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992123#comment-15992123 ] John D. Ament commented on TAMAYA-144: -- Ideally the binary distribution is only

Re: Regarding TAMAYA-144

time, getting one release out the door entirely before trying the next. Since these are separate repos, it'll cut down on voting confusion. We can vote for the artifacts on the dev list before hand. John On Sat, Apr 29, 2017 at 6:23 PM John D. Ament wrote: > Oliver, > > Basically,

Re: Regarding TAMAYA-144

Oliver, Basically, don't repackage 3rd party libraries and most of the licensing issues go away. If we don't include the website in the distribution, those licensing issues go away as well. John On Sat, Apr 29, 2017 at 6:11 PM Oliver B. Fischer wrote: > Hi all, > > I need someone to discuss >

Re: ping? status?s some tests and implemented the microprofile api in the sandbpx. Oli should care on the release... not sure if he is at Javaland, so we could meet.

So I see the microprofile stuff in source under sandbox. Very cool. Just wondering, did we have to import all of their api source code? If so, please make sure you update the NOTICE file. Also, there's no root pom file on that module. John On Sat, Mar 25, 2017 at 5:47 PM Anatole Tresch wrote

Re: site-repo: Git problem? unable to push

I would reach out to infra. On Tue, Feb 21, 2017 at 7:03 PM P. Ottlinger wrote: > Hi, > > does anyone of you experience the same problem? > > ✔ ~/workspace2016/incubator-tamaya-site [master ↑·1|✔] > 00:32 $ git push > Zähle Objekte: 28, Fertig. > Delta compression using up to 4 threads. > Kompri

Re: 2017-02-13: Hangout Minutes

On Mon, Feb 13, 2017 at 2:38 PM P. Ottlinger wrote: > Hi, > > today's hangout took place with Anatole, Werner and me. > > Topics were: > > * Graduation: > we'd love to graduate after release 0.3 and will start a discussion on > the private list > > I'm curious, what's special about 0.3 that it bl

Re: Tamaya Site repo - change default branch?

Its fixed. On Mon, Feb 13, 2017 at 8:42 PM John D. Ament wrote: > Huh, thats weird. I don't remember requesting the default branch. But > putin a ticket to change it > https://issues.apache.org/jira/browse/INFRA-13510 > > John > > > On Mon, Feb 13, 2017 at

Re: Tamaya Site repo - change default branch?

Huh, thats weird. I don't remember requesting the default branch. But putin a ticket to change it https://issues.apache.org/jira/browse/INFRA-13510 John On Mon, Feb 13, 2017 at 5:00 PM P. Ottlinger wrote: > Hi John, > > could I file an infra bug ticket to change the tamaya repo to default to

[jira] [Commented] (TAMAYA-236) Reconsider PropertySource ordering and getOrdinal()

[ https://issues.apache.org/jira/browse/TAMAYA-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15852768#comment-15852768 ] John D. Ament commented on TAMAYA-236: -- I'll point out that the Chief Arc

Re: Podling Report Reminder - February 2017

LGTM On Tue, Jan 31, 2017 at 5:05 PM P. Ottlinger wrote: > Am 30.01.2017 um 22:07 schrieb P. Ottlinger: > > here's my proposal - WDYT? > > I'd like to add our report to the wiki on time. > > Any more feedback/wishes to change things? > > Otherwise I'd put it on the wiki by Wednesday 2017-02-01 9

Re: incubator-tamaya git commit: Added additional repositories for dependency resolution

Even if its available in bintray, its also available in maven central. Unless there's a strong reason to rely on jcenter, we should try to stick to maven central. On Sun, Jan 29, 2017 at 3:42 PM Werner Keil wrote: > Did anybody use AssertJ so far? > > Bintray/JCenter has it: http://jcenter.bintr

Re: Jira - Versions

Updated. On Tue, Jan 24, 2017 at 5:49 PM P. Ottlinger wrote: > Hi Anatole, > > can you add another version > 0.4 or "Future" > as a metaversion to put tasks into that need to be done after 0.3? > > > https://issues.apache.org/jira/browse/TAMAYA/?selectedTab=com.atlassian.jira.jira-projects-plugi

Re: [DISCUSS] Graduation

ld like to get 0.3 out and to release a new homepage. After this > we would like to start with the graduation. > > Oliver > > Am 19.01.17 um 03:56 schrieb John D. Ament: > > Hey guys > > > > Its a new year. I wanted to begin discussing formally the idea of >

[DISCUSS] Graduation

Hey guys Its a new year. I wanted to begin discussing formally the idea of graduating tamaya. So what concerns exist with moving to a TLP? John

Re: Build failed in Jenkins: Tamaya-Sandbox-Master » Apache Tamaya :: OSGI Integration :: Features #254

That looks suspiciously like the problem I had when I first started working on the OSGi support. the problem is that the tests are expecting the module to be in the repo. In the case of CI, it won't be there yet. So if I had to guess, it was built manually then tests run. May need to split out

Re: Build failed in Jenkins: Tamaya-Sandbox-Master » Apache Tamaya :: OSGI Integration :: Features #254

6 um 21:59 schrieb John D. Ament: > > It seems that this module keeps failing. Anyone know why? > > I assume we run into a timeout as the build fails/get stuck before the > OSGi container is properly booted, but just wild guess while scanning > the logs. > > Cheers, > Phil >

Re: Build failed in Jenkins: Tamaya-Sandbox-Master » Apache Tamaya :: OSGI Integration :: Features #254

It seems that this module keeps failing. Anyone know why? On Thu, Dec 29, 2016 at 3:58 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < > https://builds.apache.org/job/Tamaya-Sandbox-Master/org.apache.tamaya.ext$tamaya-features/254/ > > > > ---

[jira] [Commented] (TAMAYA-73) PropertyConverters for JSR 363

[ https://issues.apache.org/jira/browse/TAMAYA-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757710#comment-15757710 ] John D. Ament commented on TAMAYA-73: - Oh ok, thanks. > PropertyConverters

[jira] [Commented] (TAMAYA-73) PropertyConverters for JSR 363

[ https://issues.apache.org/jira/browse/TAMAYA-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757504#comment-15757504 ] John D. Ament commented on TAMAYA-73: - Werner, this is assigned to you. Are

[jira] [Commented] (TAMAYA-198) tamaya-formats blindly tries (and failes) to parse a config file with multiple formats

[ https://issues.apache.org/jira/browse/TAMAYA-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685315#comment-15685315 ] John D. Ament commented on TAMAYA-198: -- Actually, the patch is using short forms

[jira] [Commented] (TAMAYA-198) tamaya-formats blindly tries (and failes) to parse a config file with multiple formats

[ https://issues.apache.org/jira/browse/TAMAYA-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685306#comment-15685306 ] John D. Ament commented on TAMAYA-198: -- [~hugo.hirsch] it shouldn't be re

[jira] [Created] (TAMAYA-201) Add documentation on raising PRs

John D. Ament created TAMAYA-201: Summary: Add documentation on raising PRs Key: TAMAYA-201 URL: https://issues.apache.org/jira/browse/TAMAYA-201 Project: Tamaya Issue Type: Improvement

Re: Podling Report Reminder - November 2016

y commit didn't break anything. > > Phil > > Am 04.11.2016 um 01:04 schrieb John D. Ament: > > Phil, > > > > The incubator is a project just like any other. We encourage external > > contribution. The file that includes this template is &

Re: incubator-tamaya-extensions git commit: Turn off doclint, for JDK 8.

Commit: > http://git-wip-us.apache.org/repos/asf/incubator-tamaya-extensions/commit/57e349d3 > > Tree: > http://git-wip-us.apache.org/repos/asf/incubator-tamaya-extensions/tree/57e349d3 > > Diff: > http://git-wip-us.apache.org/repos/asf/incubator-tamaya-extensions/diff/5

Re: Maturity Model assessment

dards. > > However it seems in serious trouble or suffering at least a very low > level > > of activity by its initial/key committer and a few others left by now > > having created forks like "HuntBugs". > > > > Cheers, > > Werner > > > > &

Maturity Model assessment

All, I put together a file with the template of the Apache Maturity Model, visible here - https://github.com/apache/incubator-tamaya/blob/master/maturity-model.md I would ask everyone to take a look at it, and maybe start discussing on the list areas where you may feel Tamaya can't answer positiv

Re: Extensions also not building

Sun, Nov 6, 2016 at 2:21 PM Oliver B. Fischer wrote: > You can check the known/active repositorys by running mvn > dependency:list-repositories > > > Am 06.11.16 um 15:26 schrieb John D. Ament: > > I suspect the underlying issue is that we're pointing to a non-relative

Re: Extensions also not building

I suspect the underlying issue is that we're pointing to a non-relative snapshot release. Snapshots are not in maven central, so maven is using its internal logic to known repositories. This I suspect is activating the legacy codehaus repos. John On Sun, Nov 6, 2016 at 4:43 AM P. Ottlinger wro

Re: Please help with the extensions

e to keep an eye on > it... > > J Anatole > > > 2016-11-05 15:26 GMT+01:00 John D. Ament : > > > Changing to Apache parent causes this, which is further: > > https://paste.apache.org/p/bEBx > > > > > > On Sat, Nov 5, 2016 at 10:23 AM John D. Ament

Re: Please help with the extensions

Changing to Apache parent causes this, which is further: https://paste.apache.org/p/bEBx On Sat, Nov 5, 2016 at 10:23 AM John D. Ament wrote: > Oliver, > > I'll raise the same concern I raised in the past - if extensions require > tamaya's core repo, it shouldn't be

Re: Please help with the extensions

Oliver, I'll raise the same concern I raised in the past - if extensions require tamaya's core repo, it shouldn't be a separate repo. Right now the parent for extensions is tamaya-all. I would recommend that its standard apache parent. John On Sat, Nov 5, 2016 at 5:48 AM Oliver B. Fischer wro

Re: Podling Report Reminder - November 2016

Thanks. > > > Am 02.11.2016 um 22:12 schrieb John D. Ament: > > Phil, > > > > Could you add the items in the "Tamaya TLP" mail thread to the graduation > > items list of the report? > > > > John >

  1   2   3   4   5   >