From: Tresch, Anatole (KGVX 42)
Sent: Montag, 24. August 2015 15:53
To: 'MULCAHEY, DAVID F.'
Subject: RE: tamaya I have done something similar and would love to help
Hi David
thank very much for your mail. We will have a deeper look at it asap. Since you
definitively bring in
Hi Oliver
there was one change that broke the build: the original build used Java 8 for
all modules, since the Java requirements were that minimally 1.7 is required,
but 1.8 could fit as well. There was a change done that we explicitly required
1.7, so Java 1.8 did not match anymore for Java 7
Hi all
the only thing we need is some tooling that
- checks out during deploy the current site from SVN
- update the corresponding directories for docs, examples and javadocs with the
related content generated by the normal maven build
- check in the changes to SVN so they are staged.
So basical
Hi all
I have a few questions related to Apache dist policies:
1)My personal key, used so far, also for the release, is not yet signed by
another apache key as typically done at ApacheCons. If that is a problem, I
assume somebody must rerun/reupload our release from the 0.1-incubating
bra
Anatole +1 (binding)
Werner Keil +1 (binding)
Oliver B. Fischer +1 (binding)
John D. Ament +1 (binding)
Romain Manni-Bucau +1 (binding)
The vote PASSES with 5+ votes. Thanks for voting!
Next step will be the vote on Incubator PMC to proceed with tamaya
0.1-incubation
release. I will start the vo
Apache Committer | Advisory
Board Member, Java Track Chair, DWX '15
Twitter @wernerkeil | @UnitAPI | @JSR354 | @JSR377 | @AgoravaProj | #DeviceMap
| #DevOps | #EclipseUOMo
Skype werner.keil | Google+ gplus.to/wernerkeil
On Thu, Aug 6, 2015 at 2:44 PM, Tresch, Anatole <
anatole.tre...@credit-su
Dear all
so I hereby start the INTERNAL PPMC vote for the first release
"0.1-incubating" of Apache Tamaya (see [2] also for details on the voting
process).
Please note:
This vote is "majority approval" with a minimum of three +1 votes (see [4]).
---
Oh I see somehow the subject of confusion. My idea was just to ask if the
contents of the vote mailing is adequate or something more should be added. I
DID NOT WANT TO START RIGHT AWAY the PPMC vote (that would be the next step).
Since all committers here on dev are also PPMC member I suggest us
Hi all
The site is based on the sources from Deltaspike. Currently site deployment is
a manual process:
- checkout/update the svn repository.
- copy generated docs (html files), build from the docs module into the
corresponding section in docs
- copy generated javadocs into the corresponding jav
Hi John
inline again (removed a few things to keep it brief)...
Anatole
-Original Message-
From: John D. Ament [mailto:john.d.am...@gmail.com]
Sent: Montag, 3. August 2015 13:54
To: dev@tamaya.incubator.apache.org
Subject: Re: Initial release input
Hi Anatole
On Mon, Aug 3, 2015 at 2
the Incubation state may delay actual usage in production I had
a discusion with a Java Framework Architect in a current project and for
future he sounded interested in using Tamaya to replace or extend
home-grown configuration mechanisms here.
Cheers,
Werner
On Thu, Jul 9, 2015 at 10:20 AM, Tr
Hi Oliver
this is really great news! I will try to have a look at it around the weekend
(possibly also earlier, but I cannot promise it...).
Cheers,
Anatole
PS: I will present Tamaya at ApacheCon Europe in Budapest - do you want me to
join ?
-Original Message-
From: Oliver B. Fischer
create a release document with all need preparations?
WDYT?
Von meinem iPhone gesendet
> Am 22.05.2015 um 16:26 schrieb Tresch, Anatole
> :
>
> Hi all,
>
> does anyone have more hints (some kind of checklist ?), what must be in place
> to do a first release...
> In
Hi all,
does anyone have more hints (some kind of checklist ?), what must be in place
to do a first release...
In the mean time we have 80% plus test coverage on all modules I think, so I
would say
documentation, dist package are the most next steps. Beside we can still
discuss on further aspec
Thanks Daniel
I have integrated it in both the main events module as well as the example.
Best,
Anatole
-Original Message-
From: linead [mailto:lin...@gmail.com]
Sent: Dienstag, 19. Mai 2015 08:17
To: dev@tamaya.incubator.apache.org
Subject: Re: TAMAYA-79 : Updated ObservedConfigTest
S
No, can you perhaps help me with some links/infos what to do?
-Original Message-
From: John D. Ament [mailto:johndam...@apache.org]
Sent: Sonntag, 10. Mai 2015 23:12
To: dev@tamaya.incubator.apache.org
Subject: Re: Release
+1 from me. I think I already got nexus setup for you. Did anyo
I, saw, still an answer is required here ;)
-Original Message-
From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
Sent: Montag, 16. März 2015 19:32
To: dev@tamaya.incubator.apache.org
Subject: Re: ConfigurationBuilder
2015-03-16 14:10 GMT+01:00 Werner Keil :
> Hi,
>
> The idea of a
+1 IMO, for optimization. When you have a performance issue, it rarely happens
because you created small arrays by use of ellipse operators.
The GC will care about them ;)
On top if that the arrays are typically not empty and creating an array is
relatively cheap compared to create a collection t
[
https://issues.apache.org/jira/browse/TAMAYA-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313700#comment-14313700
]
Tresch, Anatole commented on TAMAYA-64:
Ladies and Gentlemen,
I am curre
Hi all
I already proposed config/Tamaya for GeeCon. Looking at the last years IFAIK
they were always quite short term for the final commitment fi a speech is
accepted or not...
So lets see...
Cheers,
Anatole
-Original Message-
From: Werner Keil [mailto:werner.k...@gmail.com]
Sent: Don
Hi all
for the ones that did not yet have seen
http://www.infoq.com/news/2015/01/java-8-auto-update-java-7-end
Seems that Oracle adds one gear for phasing out Java 7 ;)
Cheers,
Anatole Tresch
Platform Strategy & Strategic Projects, KGVX 42
+41 44 334 03 89 (*414 0389)
Well, for me it is questionable if we need this:
1) I don’t see much advantages adding another abstraction for that
2) we HAVE a well defined order currently based on prio and class name, so
there are no conflicts!
BTW throwing exception in a EE environment can have disastrous consequences, so
cy than a
>> collector, no? - just trying to identify the right level of the
>> feature
>>
>>
>> Romain Manni-Bucau
>> @rmannibucau
>> http://www.tomitribe.com
>> http://rmannibucau.wordpress.com
>> https://github.com/rmannibucau
>>
>>
&
gt; >> evaluated based on the values returned by the (multiple) property
>>> >> sources
>>> >> >>
>>> >> >> Both festures I think would also be useful for single values. So we
>>> >> might
>>> >> >> define
inline as usual
2015-01-22 16:56 GMT+01:00 Tresch, Anatole :
> Feedback inline:
>
> -Original Message-
> From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
> Sent: Donnerstag, 22. Januar 2015 16:18
> To: dev@tamaya.incubator.apache.org
> Subject: Re: Prope
ava 8 as a
first citizen, many people here on the list would probably leave the project.
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2015-01-22 16:01 GMT+01:00 Tresch, Anatole :
> Hi Romain
>
>>well why I want
structively with the
discussion instead of throwing woods into our legs all the times. That
would be great!
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2015-01-22 13:47 GMT+01:00 Tresch, Anatole :
> Hi Romain/a
el ;).
>
>
>
> Romain Manni-Bucau
> @rmannibucau
> http://www.tomitribe.com
> http://rmannibucau.wordpress.com
> https://github.com/rmannibucau
>
>
>
> 2015-01-22 13:47 GMT+01:00 Tresch, Anatole
> :
>> Hi Romain/all
>>
>> I think
Hi Romain/all
I think we have quite a common agreement on the basic functions designed so far
and I do not want to
reinvent or change any of the basic mechanism. I simply come up with a simple
request to use the algorithm pattern
for a small subset of a functionality (how the final property valu
Hi is also how it is implemented currently, despite point 4: currently it
throws an exception, but we do not have finished discussion how to provide the
supported formats:
a) implement a second (optional) format
b) define/add an annotation
c) add an additional method (loosing functional interfac
Yep, it says, the converter is not able to parse the value. In that case,
within the chain of converters, it says go ahead the chain and try the next. If
at the end of the chain no converter was able to convert the value, a
ConfigException is thrown. That would the are, where we can also add add
Hi all
- throwing an exception basically would work, returning null is the better
(more efficient approach).
- Returning a non null value, will stop evaluation and the default value
returned will be the final result,
subsequent converters that may be able to parse it correctly will never be
au
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2015-01-21 10:17 GMT+01:00 Tresch, Anatole :
> Hi Romain
>
> originally we discussed adding array support to the PropertySource. Given
> that we have 2 types of config entries return
Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2015-01-21 9:21 GMT+01:00 Tresch, Anatole :
> Hi all
>
>
>
> I would even say, generally speaking, collections are only one use case of
> the broader concept, multi-value s
Hi all
I would even say, generally speaking, collections are only one use case of the
broader concept, multi-value support.
With normal value we do:
String get(String key);
T get(String key, Class type);
T get(String key, PropertyConverter converter);
Basically for multivalues we cou
Hi all
I have a couple of questions regarding the current state:
1)In Java 7 we have introduced a ConfigurationProvider, which is necessary,
since static methods on interfaces are not supported by Java 7. In Java 8 we
introduced the according Configuration.current(). I would in that case
@Anatole I don't question everything, but as the discussions are still ongoing
I wanted to have a clean sheet discussion about it.
-> Easy! I just tried to summarize the main point IMO, no bad feelings. I think
we have found a good discussion culture now, and I am happy when we can keep
that ;)
Good morning all. Time that I jump in again (inline) ;)
-Original Message-
From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
> ..
>Hehe, do you know how many frameworks you just killed?
-> Now all dead as a water (just a joke)...
> As example for Logging: you also only have one fac
inline... ;)
-Original Message-
From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
Sent: Mittwoch, 7. Januar 2015 16:37
To: dev@tamaya.incubator.apache.org
Subject: Re: Configuration.current()
same ;)
2015-01-07 16:26 GMT+01:00 Tresch, Anatole :
> Hi Romain
>
> trying
It's just there for full compatibility.
LieGrue,
strub
> On Wednesday, 7 January 2015, 16:07, "Tresch, Anatole"
> wrote:
> > Hi Mark
>
> I am almost fine with it. One thing I missed in the java7 version are the
> with
> and query functions. I think these a
Hi Romain
trying inline as well ;)
-Original Message-
>>> Here the reasons:
>>> 1) this make tamaya context/environment aware - I know these words
>>> means a lot so in more words I mean tamaya knows applications and when
>>> you'll have read 2 it knows all parts of an app
>
> Tamaya does
Hi Mark
I am almost fine with it. One thing I missed in the java7 version are the with
and query functions. I think these are important parts for future extendibility
and can simply be implemented in Java 7 manner, by adding
interface ConfigurationOperator {
Configuration operate(Configuratio
Hi all
basically yes, the only difference is that it gets its input source from
outside, whereas a property provider knows it by itself.
But that doesn't matter. I am personally not yet satisfied with the
ConfigurationFormat interface, since I also miss some aspects and don’t have
any good i
Hi all
I start commenting here in between. Even staged default configuration can be
deployed with the application (I neclect any security conerns as of now), e.g.
for application config in Credit Suisse we have the following defined classpath
structure:
cfg/${STAGE}/config/**/*.xml
cfg/GLOBAL/
Hi Romain/all
>> Hello guys,
>>
>> I'd like to discuss - again sorry - Configuration.current().
>>
>> Here the reasons:
>> 1) this make tamaya context/environment aware - I know these words
>> means a lot so in more words I mean tamaya knows applications and when
>> you'll have read 2 it knows all
tp://rmannibucau.wordpress.com
https://github.com/rmannibucau
2015-01-05 16:31 GMT+01:00 Tresch, Anatole :
> See inline again...
>
> -Original Message-
> From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
> Sent: Montag, 5. Januar 2015 10:05
> To: dev@tamaya.in
See inline again...
-Original Message-
From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
Sent: Montag, 5. Januar 2015 10:05
To: dev@tamaya.incubator.apache.org
Subject: Re: DefaultConfiguration
inline as well
2015-01-05 9:54 GMT+01:00 Anatole Tresch :
> @Romain inline
>
> 2015-01-
Hi Reinhard,
yep I will add it later...
Cheers,
Anatole
-Original Message-
From: Reinhard Sandtner [mailto:reinhard.sandt...@gmail.com]
Sent: Montag, 5. Januar 2015 11:52
To: dev@tamaya.incubator.apache.org
Subject: broken build - missing pom.xml
hey,
master is broken…
the pom.xml in
[
https://issues.apache.org/jira/browse/TAMAYA-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253495#comment-14253495
]
Tresch, Anatole commented on TAMAYA-7:
---
Ladies and Gentlemen,
I am currently
See inline...
-Original Message-
From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
Sent: Donnerstag, 18. Dezember 2014 09:21
To: dev@tamaya.incubator.apache.org
Subject: Re: UC: Configuration Injection (SE)
using pseudo code to make it shorter:
public class MyConfig {
@C
So your idea is to add more complex configuration structures, e.g. JSON into a
value and therefore have the possibility to serialize back changes, done to the
config...
We will have to add that use case. It would also simplify supporting complex
datastructures like collections, etc.
-Orig
Hi Mark
let me do a last try to clarifiy my ideas, I am open to discuss things (and do
add some ideas at the end, so we can start the discussions right away ;) ):
1) my idea was to define a minimalistic interface for properties first. It
should as simple as possible to implement. Just using Map
For me it is OK to drop. I would definitively discourage putting exception into
a separate package. Often you have only a few ones (in Tamaya it is AFAIK
currently one).Additionally you create unnecessary package dependencies etc and
you did probably not think enough to where the exception shoul
3) not sure if I get the point... some (but not all) SPIs may have a default
implementation, that is loaded ONLY, if nothing else is available from the
Bootstrap (as a minimal fallback). This can be arguable, of course.
4) you can even mix things, e.g. for providers you can first use the service
Renaming annot to annotation I am indifferent. If many others use the long name
that's OK for me.
Most of the annotations in the package are for controlling the aspects of
config injection. So spreading them makes not much sense. Also an advantage is
that developers
also can start typing tamaya
ud environment.
What was used there aside from obvious (JSON) data exchange or output one
might consider "format" is more towards "ConfigReport" or whatever you
might call that.
We used Asciidoc and with several Asciidoc and Asciidoctor affine members
here I guess that could
ot; or whatever you
might call that.
We used Asciidoc and with several Asciidoc and Asciidoctor affine members
here I guess that could also work for Tamya;-)
Werner
On Wed, Dec 3, 2014 at 1:08 PM, Tresch, Anatole <
anatole.tre...@credit-suisse.com> wrote:
> @Romain
>
> The concept
Hi Oli
adding information also to my previous mail I try to provide you an example:
PropertyProvider cfg = PropertyProviders.fromPath(AggregationPolicy.EXCEPTION,
"META-INF/cfg/*.xml", "META-INF/cfg/*.ini");
PropertyProvider messages =
PropertyProviders.fromPath(AggregationPolicy.EXCEPTION,
"M
@Romain
The concept is - as I said - that you can describe, from which source a
configuration should be read. This descriptions goes first to a reader, which
knows how to resolve the location and resolves to a number of URIs/input
streams.
These input streams can come in multiple formats (even
Yep, will add it later, from the bank here I am not able to submit anything ;(
-Original Message-
From: John D. Ament [mailto:johndam...@apache.org]
Sent: Montag, 1. Dezember 2014 00:22
To: dev@tamaya.incubator.apache.org
Subject: Re: Podling Report
If there's no other feedback, I think
+1 String support is mandatory. CharSequence for me, often is a good thing, but
sometimes also is simply not needed. Typically it is very useful, where you
have some kind of String handling in place, as it is typical for parsing or
formatting. In cases where you typically pass constant keys only
Hi Gerhard
as I said granularity is not matching in your example. Comparing concepts on
the same granularity level it would be:
String myValue = ConfigResolver.getPropertyValue("myKey"); // Deltaspike
compared to:
String myValue = Configuration.of().get("myKey").orElse(null); // Tam
Hi John
can you tell INFRA to setup a CMS in (https://svn.apache.org/repos/asf/tamaya I
assume), so we can start the homepage setup. Would be good if we have something
up there asap.
If you need an existing template "deltaspike" looks quite good for me ;)
Cheers,
Anatole
-Original Message
63 matches
Mail list logo
