/pom.xml#L124
Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com
From: Simone Tripodi simonetrip...@apache.org
To: Commons Developers List dev@commons.apache.org
Sent: Thursday, 26 July 2012 4:58 AM
Subject: Re: [chain2] configuration
Hi Elijah/all,
I just checked out latest modifications to see the changes - well done
and thanks for leading that! - I have few questions:
* the main façade is a little obscure to me - how the parser
returns the Catalog/Chain to Parser clients? Would it be useful adding
a method (or modify the
Simo,
I love ALL of those ideas. It took me quite a bit of time to get to
where we are now and I considered it a first draft that we would then
refactor from. So, yes please!
-Elijah
On Fri, Jul 27, 2012 at 4:16 AM, Simone Tripodi
simonetrip...@apache.org wrote:
Hi Elijah/all,
I just checked
From: Simone Tripodi simonetrip...@apache.org
To: Commons Developers List dev@commons.apache.org
Sent: Thursday, 26 July 2012 4:58 AM
Subject: Re: [chain2] configuration façade APIs
I may draft up a prototype using YAML as a configuration source, just
to make sure
Hi Elijah,
thanks a lot for the prompt feedback! I will start just moving the
modules (don't think that this deserves an issue) than will fill
issues for new tasks - and feel free to submit code!!!
Thanks a lot!
-Simo
http://people.apache.org/~simonetripodi/
://tupilabs.com
From: Simone Tripodi simonetrip...@apache.org
To: Commons Developers List dev@commons.apache.org
Sent: Thursday, 26 July 2012 4:58 AM
Subject: Re: [chain2] configuration façade APIs
I may draft up a prototype using YAML as a configuration source, just
to make
I may draft up a prototype using YAML as a configuration source, just
to make sure that it in fact is a good abstraction. I noticed that the
SnakeYaml parser is under the Apache 2.0 license
(http://code.google.com/p/snakeyaml/). I'm assuming that it wouldn't
be a problem to take it as a
@commons.apache.org
Sent: Thursday, 26 July 2012 4:58 AM
Subject: Re: [chain2] configuration façade APIs
I may draft up a prototype using YAML as a configuration source, just
to make sure that it in fact is a good abstraction. I noticed that the
SnakeYaml parser is under the Apache 2.0 license
(http
@commons.apache.org
Sent: Thursday, 26 July 2012 4:58 AM
Subject: Re: [chain2] configuration façade APIs
I may draft up a prototype using YAML as a configuration source, just
to make sure that it in fact is a good abstraction. I noticed that the
SnakeYaml parser is under the Apache 2.0 license
(http
/testng/blob/master/pom.xml#L124
Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com
From: Simone Tripodi simonetrip...@apache.org
To: Commons Developers List dev@commons.apache.org
Sent: Thursday, 26 July 2012 4:58 AM
Subject: Re: [chain2] configuration
Developers List dev@commons.apache.org
Sent: Thursday, 26 July 2012 4:58 AM
Subject: Re: [chain2] configuration façade APIs
I may draft up a prototype using YAML as a configuration source, just
to make sure that it in fact is a good abstraction. I noticed that the
SnakeYaml parser is under the Apache
Developers List dev@commons.apache.org
Sent: Thursday, 26 July 2012 4:58 AM
Subject: Re: [chain2] configuration façade APIs
I may draft up a prototype using YAML as a configuration source, just
to make sure that it in fact is a good abstraction. I noticed that
the
SnakeYaml parser is under
Hi everyone,
I've created a first draft of refactoring chain so that it uses a
facade for configuration.
Please see the diff attached to this ticket to get my proposed
changes: https://issues.apache.org/jira/browse/CHAIN-72
Here is a summary of what I have done:
* Removed the module
I may draft up a prototype using YAML as a configuration source, just
to make sure that it in fact is a good abstraction. I noticed that the
SnakeYaml parser is under the Apache 2.0 license
(http://code.google.com/p/snakeyaml/). I'm assuming that it wouldn't
be a problem to take it as a
Hi Simo and Elijah,
Am 23.07.2012 21:55, schrieb Simone Tripodi:
Thanks a lot Oliver, much more than appreciated!
If you could have a look at current configuration stuff at [chain2]
and share what you think would be already *great*!
I had a look at the current config module. I understand
Good morning all,
so I continue proposing the already proposed roadmap: let's add the
façade APIs for the [chain] configuration stuff, adapt the existing
XML configuration reader, use the [configuration] in future releases
for new [chain] configurations.
How does it sound?
best,
-Simo
Hi Simo,
That sounds good to me. However, I'm having trouble separating the
existing Catalog implementation from the rest of chain. Digester is
tightly coupled across components, so it is a non-trivial refactor to
make a configuration facade. I'm working on it, but it will take some
time.
I've been going through the chain source for about a day looking for a
way to decouple the digester configuration. Sadly, I don't think that
I will be able to do it without removing digester. I may just jump
ahead and remove [digester] completely and then move us to
[configuration] for creating
Am 23.07.2012 09:00, schrieb Simone Tripodi:
Good morning all,
so I continue proposing the already proposed roadmap: let's add the
façade APIs for the [chain] configuration stuff, adapt the existing
XML configuration reader, use the [configuration] in future releases
for new [chain]
Hi Elijah,
not sure we understand each other there, please confirm IIUC - in my
mind I would have extracted configurations APIs (mainly interfaces
and few abstract classes maybe) from the configuration module and put
in the core, then renamed the actual configuration module to
`xml-configuration`
Thanks a lot Oliver, much more than appreciated!
If you could have a look at current configuration stuff at [chain2]
and share what you think would be already *great*!
then, feel free to put your hands and help us on defining the façade :)
alles gute,
-Simo
Just tracked CHAIN-72 and assigned to Elijah
best,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Sat, Jul 21, 2012 at 11:27 PM, Simone Tripodi
simonetrip...@apache.org wrote:
Hi all guys,
Thanks!
On Sat, Jul 21, 2012 at 11:54 PM, Simone Tripodi
simonetrip...@apache.org wrote:
Just tracked CHAIN-72 and assigned to Elijah
best,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On
Is there any relation or overlap to [configuration]?
Depending on your concrete requirements, this is probably over-sized.
But maybe a source of inspiration?
Oliver
Am 22.07.2012 10:00, schrieb Elijah Zupancic:
Thanks!
On Sat, Jul 21, 2012 at 11:54 PM, Simone Tripodi
Good point Oliver,
I honestly didn't think about [configuration], please apologize! since
[chain] already had a way to be configured via an XML wrapper around
the Digester, we thought it would have been good having a façade and
plug other textual format...
Anyway, we are open to suggestions -
Hi Simo,
Am 22.07.2012 17:54, schrieb Simone Tripodi:
Good point Oliver,
I honestly didn't think about [configuration], please apologize! since
[chain] already had a way to be configured via an XML wrapper around
the Digester, we thought it would have been good having a façade and
plug other
Hi Oliver,
Configuration seems like it might be useful if I end up redoing the
XML configuration portion. Are there any plans to support YAML?
Thanks,
-Elijah
On Sun, Jul 22, 2012 at 1:16 PM, Oliver Heger
oliver.he...@oliver-heger.de wrote:
Hi Simo,
Am 22.07.2012 17:54, schrieb Simone
Hi all guys,
Elijah and and I had a chat and we thought that, since chain2 hasn't
released yet, we are still in time to define a façade API for textual
configurations and rename the current XML configuration module to
xml-configuration (and adapt it to new API) - new formats such as YAML
and JSON
28 matches
Mail list logo
