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

Isn't Tamaya going to be ramped down? Werner On Fri, Jul 3, 2020 at 10:11 PM ASF subversion and git services (Jira) < j...@apache.org> wrote: > > [ >

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

unless e.g. similar to "Jakarta" Apache Foundation granted us to keep using the name "Tamaya" we probably have to abandon it and find a new one. Werner On Thu, Apr 30, 2020 at 11:20 PM Werner Keil wrote: > Hi, > > I also moved but it's already done, so I sh

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

Hi, I also moved but it's already done, so I should be able to help sooner. Cheers, Werner On Thu, Apr 30, 2020 at 11:18 PM P. Ottlinger wrote: > Hi all, > > as I'm in the middle of moving I won't be able to do that much until end > of June, but my github id is "ottlinger". > > Thanks and

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

John/all, Thanks for the update. I believe Philip already asked about that and Anatole who owns the JavaConfig organization should be able to give those who are willing to help admin or push access. I am also happy to help, so please unless I already have could you give me the necessary access?

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

It looks like William has sent it to both lists, everyone else must have voted on dev. Werner On Thu, Apr 23, 2020 at 4:36 AM John D. Ament wrote: > 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

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

William you probably joined a little late, but I would not consider it a chance to contribute to an official Jakarta EE configuration standard, either directly or indirectly via MP Config. Given most of that is also under the Apache license all it takes for those who would like to contribute to

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

+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 > > terminate/retire Apache Tamaya podling and move all repositories over to > > Github and

Re: Podling Tamaya Report Reminder - May 2020

Justin, Thanks for the update. I believe it is a good and sensible move. Those who were able to contribute and still wish to help the cause have the opportunity to help the likes of Helidon, Quarkus or Eclipse MicroProfile which in one or the other form is a likely candidate for inclusion into

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

Hi Anatole, Thanks for the update, also about your future career step. Congratulations on moving to IBM soon. As we discussed, an incubating project does not get archived, but simply deleted by Apache, correct me if I got that wrong? So 1) would delete and destroy all of it. There may not be too

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

I guess John knows best, what happens when you're no longer able to contribute to a project: https://github.com/eclipse/microprofile-rest-client/graphs/contributors If it wasn't for IBM then MP Rest Client would be dead after he stopped working on it around 2 years ago. Same for Config btw

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

I think this shows that best: https://github.com/apache/incubator-tamaya/graphs/contributors Werner On Mon, Feb 10, 2020 at 10:06 PM Oliver B. Fischer wrote: > And who is currently the most active contributer? > > Am 10.02.20 um 21:00 schrieb P. Ottlinger: > > Hi *, > > > > Am 10.02.20 um

Re: Podling Tamaya Report Reminder - February 2020

> a valid alternative. > > But ofc that’s just my opinion. > > Julian > > Am 19.01.20, 21:41 schrieb "Werner Keil" : > > Phil/all, > > Thanks for the discussion. > I'm not sure, to what extent the ASF can really boost the project's >

Re: Podling Tamaya Report Reminder - February 2020

Phil/all, Thanks for the discussion. I'm not sure, to what extent the ASF can really boost the project's popularity and adoption? There have been many uncertainties like the whole Config JSR issue, although that's now dead, but it still isn't completely sure, if MicroProfile Config would simply

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

The second one is a formally binding vote for an Apache Release. > A PPMC Vote alone is not (as its formally not an Apache PMC). > > Thus, two votes and the second one just finished : ) > > Julian > > Am 07.11.19, 13:31 schrieb "Werner Keil" : > > I r

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

I recall I voted on that already Anatole Tresch schrieb am Do., 7. Nov. 2019, 11:53: > Great, thanks to all. > > I assume I will push out everything tomorrow or the WE. I will close the > vote in the next minutes... > > J Anatole > > > Am Do., 7. Nov. 2019 um 08:05 Uhr schrieb Julian Feinauer <

Re: ApacheCon in Berlin - anyone?

I won't because I have a Jakarta EE talk at EclipseCon Europe and another session about JSR 385 at Codemotion in the same week. Werner On Fri, Oct 4, 2019 at 8:58 PM Julian Feinauer wrote: > Hi guys, > > I will be there, yes : ) > > Julian > > Am 04.10.19, 17:20 schrieb "P. Ottlinger" : > >

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

+1 Werner P. Ottlinger schrieb am Mi., 2. Okt. 2019, 07:48: > Am 25.09.19 um 14:41 schrieb Anatole Tresch: > > The tag for this release candidate is available at [3] and [4]. It will > be > > renamed > > once the vote passed. > > Please take a look at the artifacts and vote! > > +1 > > Works

Re: Podling Report Reminder - October 2019

Did RC4 pass and was it deployed already? On Mon, Sep 23, 2019 at 7:59 PM Anatole Tresch wrote: > Then lets go for rc5. It s not much work... > > Julian Feinauer schrieb am Mo., 23. Sep. > 2019, 19:54: > > > Hi Anatole, > > > > I think we should create a new vote for that, this is my gut

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

Cool, then also +1 from my side. Hope it all works this time? Werner On Fri, Sep 13, 2019 at 1:06 PM Aaron Coburn wrote: > +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: > > $

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

applies to the -sandbox items) > > > > > On Mon, 26 Aug 2019 at 11:43, Werner Keil wrote: > > > Wouldn't it be possible to change from snapshot only once 0.4 is > released, > > or should it work without Snapshot in staging? > > > > Aaron Coburn

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

Wouldn't it be possible to change from snapshot only once 0.4 is released, 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 will

Re: FW: [OFFER] Offer to Mentor one or two podlings

Julian, Thanks for your interest in mentioning. I also haven't had a chance to help with too many parts of Tamaya except for a bit of HOCOM aspects, as I have duties in other Open Source communities like the JCP or Eclipse (Jakarta EE) One major difference is, that Tamaya adds more support for

Re: Starting with the preparation of the next release of Tamaya

+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 keyboard > > > From: Anatole Tresch > Sent: Monday, August 19, 2019 5:44:37 AM > To:

Re: release it!

; 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 schrieb Werner Keil: > > > The JSR will never be out, it was withdrawn in favor of either > > MicroProfile > >

Re: release it!

Phil, The JSR will never be out, it was withdrawn in favor of either MicroProfile Config, a future Jakarta spec or both. the Jakarta spec is not there but keeping the old JSR in there would cause more confusion, in a sandbox module I guess it is at people's own risk. Werner On Wed, Jul 17,

Re: release it!

I'm not sure about the part that implemented JSR 182. Was that official or in the sandbox modules? I would deprecate those in a new release because the JSR stopped. At the moment Microprofile Config is an alternative. A Jakarta spec is planned but not sure when it will start. Werner Aaron

Re: Returning to Tamaya

-Fr > matches best... > > P. Ottlinger schrieb am Mo., 27. Mai 2019, 21:01: > > > Hi, > > > > I could provide a location for a not too big meetup > > just let me know, Oliver+Werner :-) > > > > Cheers, > > Phil > > > > Am 27.05.

Re: Returning to Tamaya

If you can at a shorter notice, it would be great. I am not sure when we have to be in Berlin, it might be between July and August once, but that is probably not a good time during the holidays.樂 Werner On Mon, May 27, 2019 at 7:29 PM Anatole Tresch wrote: > I can do so yes... also did that

Re: Returning to Tamaya

I was there a little while ago when the JCP EC met in Berlin. Which subject would you have in mind, Tamaya or something else? I could but not sure, if it works before the summer or afterward. The current client and project have partners to meet in Berlin, so it would be great if that could work

Re: Returning to Tamaya

For me neither, I have an Adopt-a-JSR session with JUG Utrecht. Werner On Sun, May 26, 2019 at 10:10 PM Anatole Tresch wrote: > sorry, we in general are more difficult as well foe me. 1st of June does > not work at all (children time)... > > How about meeting at some Hackergarden or

Re: Returning to Tamaya

I may be traveling to a Dutch Meetup then. Oliver B. Fischer schrieb am Fr., 17. Mai 2019, 14:43: > Would be the 1st of June fine for us? > > Am 15.05.19 um 11:20 schrieb Oliver B. Fischer: > > Hi, > > > > I can only offer an appointment for the 1th or 2nd of June... ? > > > > Best, > > > >

Re: Returning to Tamaya

Hi Oliver, That's great news. I may be in Berlin at some point for a meeting with clients in the current project. Any chance for a Tamaya proposal to Apachecon Berlin anyone or is it too short notice? Werner Anatole Tresch schrieb am Mo., 13. Mai 2019, 08:37: > Hi Oliver > > thats awesome

Re: Short Update

Anatole, Thanks for the update. Which modules deal with HOCON support? I'd be happy to look at those since I contributed to some of the extension/incubation modules around HOCON and supporting units in configuration like Typesafe Config does. Regards, Werner On Sun, May 12, 2019 at 6:38 PM

Re: another approach to configuration: project helidon/oracle podcast

Another reason why on behalf of the Jakarta EE Spec committee I try to help the JSR EG and Spec Leads out of the hole they dug themselves into and see how it could become a Jakarta EE Spec instead. IMO the MP API which already used by some of those products could be be largely used and maybe just

Re: Podling report due today

The underlying standardization effort is stalled and so far has not made up their minds whether to continue the inactive JSR 382 (it is artificially kept "active", in reality it has not released an EDR since October 2017: https://jcp.org/en/jsr/detail?id=382 Tamaya implements both that JSR and the

Yet another Microframework

Hi, I heard about Apache Juneau a few days ago by an article on Heise. https://juneau.apache.org It seems John is involved although the only serious committer is just one person with Millions of LOC over the past 2 years. Shows, even a relatively small project with just half a dozen committers

Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

+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 schrieb P. Ottlinger: > > Any objections or can I file an issue to move us over to the new system? > > Filed >

Archaius

Guys, It may not apply to Archaius at this point, but in a MicroProfile lab Emily is doing here at Java2Days she mentioned, Netflix will no longer contribute to Hystrix. A rather crucial piece for circuit breakers for the Spring stack. If Netflix also pulled the plug on Archaius, this shows, why

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

s that direction? > > --William > ____ > From: Werner Keil > Sent: Wednesday, November 7, 2018 12:12 PM > To: dev@tamaya.incubator.apache.org > Subject: Re: RFC: Draft for report - will submit at 2018-11-06 > > William, > > Thanks for

Re: Work pushed

Hi, Was this why most builds broke for a while? Thanks and Regards, Werner On Sun, Nov 18, 2018 at 10:51 PM Anatole Tresch wrote: > Hi Guys > > I pushed everything now from my machine. All builds worked fine, keeping > fingers crossed they will do also on the build servers. From a

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

We discussed this a while ago that the mentors have not been available in most cases. Werner Am Do., 8. Nov. 2018, 07:15 hat Justin Mclean geschrieben: > Hi, > > Would be good if you also answered this question in the report: > > Have your mentors been helpful and responsive or are things

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

ted in helping out with getting jsr382 across the finish > line to unblock that effort and then start churning out examples for all > the different kinds of uses that tamaya has. I think that's also the way to > start getting more people using and then ultimately involved with tamaya. > > --W

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

not realize how much William has done, so why haven't we voted on his committer role already? Werner On Wed, Nov 7, 2018 at 4:32 PM Werner Keil wrote: > Phil mentioned two possible committers. > Not sure if they meet requirements by ASF based on their existing > contributions like

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

Phil mentioned two possible committers. Not sure if they meet requirements by ASF based on their existing contributions like JIRA, etc. to be nominated right now? Anatole mentioned support for both JSR 382 and MicroProfile config. However the Config standardization efforts are totally fragmented

Re: [ANNOUNCE] Commons Configuration 2.4 Released

Phil, Not at all. At least when I last looked at it, Commons Config 2 shows a great improvement over V1, somewhat similar to e.g. the step up from Log4J 1 to Log4J2. However, its API does not seem to implement either MicroProfile Config, JSR 382 or (a not yet existing) Jakarta EE Config. And

Re: Important changes

So I guess we try go get Tamaya graduated here eventually? If a clarification of a more distinct config spec than the "Trinity" that's cultivated right now happens before that, it certainly won't hurt ;-) @Anatole All the best. Werner On Sun, Oct 7, 2018 at 3:36 PM Anatole Tresch wrote: >

Re: Improving our Community

Unfortunately the fragmentation and internal competition between JSR 382, MicroProfile Config, Geronimo Config, DeltaSpike Config and at Apache alone at least Commons Config 2 and Tamaya, make it harder for all involved projects to reach a broader audience. Cheers, Werner On Sun, Sep 30, 2018

RE: Nest steps

Yes, also did that for the JSR 385 API similar to JavaMoney. Werner Sent from Mail for Windows 10 From: Anatole Tresch Sent: Thursday, May 10, 2018 18:29 To: dev@tamaya.incubator.apache.org Cc: P. Ottlinger Subject: Re: Nest steps Its basically simple: - Add module-info.java files. -

RE: Java 9 & 10

Actually a Multi-Release JAR if we found that useful (with a new JDK every 6 months it seems tempting or even inevitable) is not built with Java 9 or 10, the plugin states it should be with Java 8, but thanks to the Multi-release feature and META-INF it’ll work with different versions. I am

Re: Java 9 & 10

Hi, I raised this for the RI of JSR 385, the upcoming new Units of Measurement standard 2.0: https://github.com/unitsofmeasurement/indriya/issues/25 If this Maven plugin was acceptable by Apache projects it could be used not only by Tamaya. And utilizing the Multi-Release JAR feature of Java 9

Fwd: Apache EU Roadshow CFP Closing Soon (23 February)

Hi, Did someone already propose a Tamaya talk? I'm afraid, beside DWX in Nuremberg in the last week of June there is an exact overlap (Apache and Eclipse don't seem to coordinate everywhere as with the possible "Jakarta EE" name ;-) with EclipseCon France: https://www.eclipsecon.org/france2018/

Re: ApacheCon NA in September

Phil, Let's have a look, I would not mind to propose something if others are not in town or able to present. Cheers, Werner On Wed, Jan 31, 2018 at 11:10 PM, P. Ottlinger wrote: > Hi, > > Am 31.01.2018 um 22:17 schrieb Anatole Tresch: > > just wanted to inform you that

Re: ApacheCon NA in September

Hi Anatole, Thanks for the heads-up. Seems in Europe Apache does something like Voxxed Days as opposed to a full conference? I'd be happy to propose something with other Tamaya committers for Berlin. As I seem to be in Germany for most of this year and unless there was really e.g. a JavaOne talk

Re: Recent test failures with Extensions

Great stuff. Glad to see the Tamaya team grow. And with a company that seems to deal with configuration a lot it might also broaden the user base. If that continues it may also increase chances of graduation. Cheers, Werner On Tue, Jan 23, 2018 at 11:23 PM, P. Ottlinger

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

uate. > > John > > On Fri, Jan 12, 2018 at 1:57 PM Werner Keil <werner.k...@gmail.com> wrote: > > > Wonder, when we might see this about Tamaya? > > > > https://sdtimes.com/data/apache-trafodion-becomes-top- > level-project/#.WlkEgCxWl10.gmail > >

Apache Trafodion becomes Top-Level Project - SD Times

Wonder, when we might see this about Tamaya? https://sdtimes.com/data/apache-trafodion-becomes-top-level-project/#.WlkEgCxWl10.gmail Of course the team sounds quite massife at Trafodion, especially from China. Werner

Re: Tamaya implements the JSR's API

I don't think there are any real implementations yet. Maybe Geronimo Config, but the default also looks more like it's MP Config so far. Werner On Thu, Nov 23, 2017 at 11:16 PM, P. Ottlinger wrote: > Hiho, > > Am 23.11.2017 um 00:13 schrieb Anatole Tresch: > > the > >

Re: motivational conference today

Hi, Sounds great. Will this new conference also have a CFP or tracks interesting to Tamaya or other technologies? I was invited to chair the Java Track of DWX '18 once more after 2017 and probably with MicroProfile/JSR 382 EG reps a talk about configuration may fit in there quite nicely. I'll try

Re: Reverting Api and Extensions?

After JVMCon? Am 19.11.2017 23:29 schrieb "Anatole Tresch" : > BTW, not yet fixed 100%, but it looks that I will be in Berlin on We/Th > next week... > I will keep you updated once I go book the flights! > > 2017-11-19 23:27 GMT+01:00 Anatole Tresch : > >

Re: Travis integration working from individual project forks

So Travis works while Jenkins builds for the same artifacts keep failing? Am 15.11.2017 00:11 schrieb "P. Ottlinger" : > Hi, > > Travis integration seems to be working fine :-) > At least the first build went through successfully in contrast to the > current situation on

Re: [DISCUSS] Offering Tamaya as ConfigJSR reference Impl

+1 Speak tomorrow in the EG call Am 08.11.2017 05:04 schrieb "Anatole Tresch" : OK, then I will follow up this thing on Thursday with the guys on the EG. Even is we dont get to be the official implementation, our extensions also will allow us to outstand IMO ;-) 2017-11-07

Re: [DISCUSS] Offering Tamaya as ConfigJSR reference Impl

It sounds worth considering. Of course there has been effort by Mark, Co-Spec Lead of the JSR and mostly John into Geronimo Config https://github.com/apache/geronimo-config/graphs/contributors Compared to the codebase and various extension modules (I would not see many as part of the RI, but

Re: Microprofile TCK now running

Cool, that will be great news for upcoming conference talks about it. Werner On Fri, Oct 13, 2017 at 1:24 AM, Anatole Tresch wrote: > Hi all, > > it was a bit harder than originally thaught, but with the fix of some > issues on MP and the OptionalConverter we now have the

Re: Anyone looking at this PR?

Probably another reason why Java EE went to Eclipse. There fully Github based repos become the norm for most new projects. Am 07.10.2017 11:42 schrieb "P. Ottlinger" : > Hi, > > maybe we are still not really understanding each other. > I was of the impression that ASF

[jira] [Updated] (TAMAYA-313) Evaluate Java 9 Multi-release JAR feature

[ https://issues.apache.org/jira/browse/TAMAYA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Keil updated TAMAYA-313: --- Summary: Evaluate Java 9 Multi-release JAR feature (was: Evaluate Java 9 Multi-version JAR feature

[jira] [Created] (TAMAYA-313) Evaluate Java 9 Multi-version JAR feature

Werner Keil created TAMAYA-313: -- Summary: Evaluate Java 9 Multi-version JAR feature Key: TAMAYA-313 URL: https://issues.apache.org/jira/browse/TAMAYA-313 Project: Tamaya Issue Type: Task

Re: JSR 382

09-13 11:14 GMT+02:00 Werner Keil <werner.k...@gmail.com>: > > > Guys, > > > > Looks like a couple of JSRs beside Java SE (.next) were filed this week: > > https://jcp.org/en/jsr/detail?id=382 > > > > It is up to the PMO who Emily and Mark repre

JSR 382

Guys, Looks like a couple of JSRs beside Java SE (.next) were filed this week: https://jcp.org/en/jsr/detail?id=382 It is up to the PMO who Emily and Mark represent (I know, for a long time he represented Apache Foundation;-) but someone from Tamaya, ideally Anatole (representing Trivadis, not

Re: Hangout next week (2017-09-11)

Me too, next week should work. Werner On Mon, Sep 4, 2017 at 8:07 PM, P. Ottlinger wrote: > Am 04.09.2017 um 16:29 schrieb Oliver B. Fischer: > > WDYT? 8 pm? > > sounds good to me since I'm quite busy this week. > > Cheers, > Phil >

Re: Scope of Tamaya 0.4

Hi, Does the MicroProfile extension module implement the current API and pass TCKs? If so, it could be worth mentioning it under https://github.com/eclipse/microprofile-config (Tamaya is already an influence, but if parts implement the API why not also add this fact in the Readme) Werner On

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

ding +1 votes (pmc): > - Anatole > - Philipp > - Oliver > - John > - Werner > > 0 non-binding +1 votes: > > 0 -1 votes: > > I will prepare now the vote for the IPMC. > > Oliver > > > Am 12.07.17 um 11:06 schrieb Werner Keil: > >> +1 >> >> >&

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

+1 On Wed, Jul 12, 2017 at 2:34 AM, John D. Ament wrote: > +1 to release > > Checked rat, verified signatures. > > On Tue, Jul 11, 2017 at 6:08 PM Oliver B. Fischer < > o.b.fisc...@swe-blog.net> > wrote: > > > Hi, > > > > I was running the needed tasks to get the

Re: 2017-07-10 hangout minutes

Sorry did not hear it:-/ On Mon, Jul 10, 2017 at 10:08 PM, P. Ottlinger wrote: > Hi, > > today's meeting took place with: > * Anatole, Oliver and Phil > > AGENDA: > * Release status > ** Release of TamayaCORE is approved by the IPMC - ok > ** Vote01 will take place in

Re: Hangout next Monday, 12. June

+1 Werner On Mon, Jun 12, 2017 at 8:11 AM, Oliver B. Fischer wrote: > Great, > > so we will talk at eight. > > > cu > > > Am 07.06.17 um 09:59 schrieb Oliver B. Fischer: > > WDYT? >> >> Von meinem iPhone gesendet >> > > -- > N Oliver B. Fischer > A Schönhauser Allee

Re: Podling Report Reminder - June 2017

I assume the 0.3 release and probably what's happening with JBake could be enough news? Werner On Thu, Jun 8, 2017 at 2:46 AM, wrote: > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initial reminder to

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

+1 I looked at the JBake page from my Android mobile this morning and it does not render that well compared to the current one, but for the sake of being up to date, I think the JBake one is an improvement (and some CSS/Bootstrap "magic" could probably also address issues on mobile browsers or

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

Yes for Maven they should be, but ZIP sounds like a "binary" or "download" distribution was also created, where I don't think Maven supports you unless there is a separate Maven resource-plugin or similar to create ZIP or TAR archives with Maven, too. Cheers, Werner On Wed, May 24, 2017 at 3:01

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

Thanks for pointing that out John. I know I had to go through that when releasing some artifacts of DeviceMap while it was active. No rocket science though, so I would not change the vote and assume everyone can change theirs if the necessary conditions (like those signatures) are met. All Maven

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

+1 Werner On Tue, May 23, 2017 at 10:45 PM, Oliver B. Fischer < o.b.fisc...@swe-blog.net> wrote: > Hi, > > I was running the needed tasks to get the 0.3-incubating release of Apache > Tamaya out. > The artifacts are deployed to Nexus [1] and releases [3]. > > The tag is available at [3] and

Re: Hangout tonight?

Sounds OK, too. I am pretty flexible between now and the second half of June. Anatole said, he proposed one or the other topic to Expert Days. I'd be happy to also do with 2 or 3 key topics I work with or spoke about already.

Re: Hangout tonight?

I'd be available. Werner On Mon, May 15, 2017 at 2:17 PM, Anatole Tresch wrote: > How about a short hangout tonight at 20h the latest? > > J Anatole > > -- > *Anatole Tresch* > PPMC Member Apache Tamaya > JCP Star Spec Lead > *Switzerland, Europe Zurich, GMT+1* >

Re: Do we need a binary distribution?

Good point. I don't know if any Apache projects do that by themselves, but in some cases maybe a Docker image could be a binary distribution to consider. MavenCentral/Sonatype seems to have lost the lead on that, but Bintray (their mirror and equivalent to MavenCentral is JCenter) did a lot for

Re: Regarding TAMAYA-144

Was there a hangout today? Did not see a missed reminder. On Mon, May 1, 2017 at 4:43 PM, Oliver B. Fischer wrote: > So give a hangout call at 6:45. I will be only. I just returned from the > doctor... > > > Am 01.05.17 um 15:24 schrieb Anatole Tresch: > >> I am

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

Asciidoctor license because of the plugins? Hate to ask but what about JBake?;-) On Mon, May 1, 2017 at 5:11 PM, Oliver B. Fischer (JIRA) wrote: > > [ https://issues.apache.org/jira/browse/TAMAYA-144?page= > com.atlassian.jira.plugin.system.issuetabpanels:comment- >

Re: Regarding TAMAYA-144

So should we do the hangout at 5pm or is it something in greater detail you wish to discuss 1on1 that may not be helpful to all participants? Werner On Mon, May 1, 2017 at 1:43 PM, Oliver B. Fischer wrote: > Hi Anatole, > > can I call you via Hangout at 5 pm? I am

Re: Regarding TAMAYA-144

license by some Oil, Gas and Energy standards body) and that also works fine for SIS ;-) It long left the incubator and seems to have quite an impressive number of contributors: http://sis.apache.org/team-list.html Werner On Sun, Apr 30, 2017 at 10:38 AM, Werner Keil <werner.k...@gmail.c

Re: Regarding TAMAYA-144

Same here. Werner On Sun, Apr 30, 2017 at 6:19 AM, Anatole Tresch wrote: > hi oliver > > mo is ok. when? it is a free day here in zh... > best Anatole > > Am 30.04.2017 00:11 schrieb "Oliver B. Fischer" >: > > > Hi all, > > > > I need someone to

Re: Hangout this week?

d about some > sandbox modules such as tamaya-metamodel and that we will have to add much > more tests in the future as well. > Afterwards release we will switch to Java 8. > > J Anatole > > 2017-04-26 23:12 GMT+02:00 P. Ottlinger <pottlin...@apache.org>: > > > Am

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

Apache Commons, seriously?;-O Why is that even on the list, at least other ASF projects should be pretty obvious. On Wed, Apr 26, 2017 at 11:12 PM, P. Ottlinger wrote: > Hi guys, > > what needs to be done here?! > > Do we just need to list the licenses or are there

Re: Hangout this week?

Guess we're skipping this Week?

Re: Hangout this week?

> > Oliver > > > Am 18.04.17 um 22:56 schrieb P. Ottlinger: > >> Am 18.04.2017 um 20:33 schrieb Werner Keil: >> >>> Do we plan a hangout this week or will it be better next week? >>> >> +1 for next week to give Oliver some time to forge the relea

Re: Hangout this week?

Have to check, if there is a JCP.next call but otherwise next Tue is fine for me, too. On Wed, Apr 19, 2017 at 8:30 AM, Oliver B. Fischer wrote: > Tuesday next week is fine for me. > > > Am 18.04.17 um 23:43 schrieb P. Ottlinger: > > Am 18.04.2017 um 23:28 schrieb

Hangout this week?

Hi, Do we plan a hangout this week or will it be better next week? Werner

Re: Hangout?

So there was not enough for a hangout, or are we doing it another day? Werner On Mon, Apr 10, 2017 at 8:01 PM, Oliver B. Fischer wrote: > My topic for today would be only: Close the issues assigned to you for > 0.3. This is an blocker for the release. > > Oliver > >

Re: Hangout?

Me, too. On Mon, Apr 10, 2017 at 12:22 AM, Anatole Tresch wrote: > For me all works Mo, Tu, We... > > Am 09.04.2017 22:56 schrieb "P. Ottlinger" : > > > Am 09.04.2017 um 22:31 schrieb Anatole Tresch: > > > How about a hangout on Monday 20h MET

Re: [jira] [Commented] (TAMAYA-231) Fix developers and contributors in POMs

No idea if that happens while a project is incubating? John should know. However, we heard on the mailing list by 2 or 3 of them they wanna leave. Werner On Thu, Apr 6, 2017 at 10:51 PM, P. Ottlinger <pottlin...@apache.org> wrote: > Am 06.04.2017 um 22:48 schrieb Werner Keil (JIRA): &

Re: Cleaning up JIRA for 0.3

Hi, I simply removed the version tag from at least the Unit/HOCOM support issues. Especially things in the sandbox don't have to be dragged from release number to release number. If we don't know which version it'll be ready or it has not started, that's "backlog". Are there any showstoppers

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

[ https://issues.apache.org/jira/browse/TAMAYA-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Keil updated TAMAYA-73: -- Affects Version/s: (was: 0.1-incubating) 0.2-incubating > PropertyConvert

[jira] [Updated] (TAMAYA-234) Which JSR 363 implementations to use?

[ https://issues.apache.org/jira/browse/TAMAYA-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Keil updated TAMAYA-234: --- Fix Version/s: (was: 0.3-incubating) > Which JSR 363 implementations to

[jira] [Updated] (TAMAYA-84) Finish asciidoc for jodatime module

[ https://issues.apache.org/jira/browse/TAMAYA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Keil updated TAMAYA-84: -- Fix Version/s: (was: 0.3-incubating) > Finish asciidoc for jodatime mod

  1   2   3   4   5   6   >