You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directmemory.apache.org by Maurizio Cucchiara <mc...@apache.org> on 2011/12/30 12:55:21 UTC

Re: Code Formatting

Hi all,
before it is too late, we should take a decision at this point, the
code in terms of formatting is going to become a big mess.
I personally saw at least 3 different kinds of code styles.
I'd strongly advise to use maven code style (though I'm not nuts about
it) and configure maven checkstyle plugin.
WDYT?


Twitter     :http://www.twitter.com/m_cucchiara
G+          :https://plus.google.com/107903711540963855921
Linkedin    :http://www.linkedin.com/in/mauriziocucchiara

Maurizio Cucchiara



On 21 October 2011 21:30, Raffaele P. Guidi <ra...@gmail.com> wrote:
> I hate line breaks before curly braces - I couldn't stand it even in csharp
> where it's the standard:
>
> public class MyMojo
> {
>
>
>
> Also I find horrible and boring listing function names and parameters that
> are (or should be) self explicable. Would find them disturbing even if they
> were automatically generated - but could cope with that if needed
>
>    /**
>     * Artifact factory.
>     *
>     * @component
>     */
>    private ArtifactFactory artifactFactory;
>
>
>    // ----------------------------------------------------------------------
>    // Mojo parameters
>    // ----------------------------------------------------------------------
>
>    /**
>     * The POM.
>     *
>     * @parameter expression="${project}"
>     * @required
>     */
>
>
> Ok for everything else.
>
> Ciao,
>    R
>
>
> 2011/10/21 Akash Ashok <th...@gmail.com>
>
>> Along with the formatted for eclipse here's a link which defines the coding
>> standards
>>
>> http://maven.apache.org/developers/conventions/code.html
>>
>> It would be nice if we could come to a consensus on the standards soon so
>> that we dnt run into too much of maintenance issues.
>>
>> I would like to hear what every1 has to say about it.
>>
>> Cheers,
>> Akash A
>>
>> 2011/10/21 Raffaele P. Guidi <ra...@gmail.com>
>>
>> > Yes, nice feature. It's a team saver ;)
>> >
>> > On Thu, Oct 20, 2011 at 9:40 PM, Maurizio Cucchiara
>> > <mc...@apache.org>wrote:
>> >
>> > > Personally I don't like the maven code style, but I have to admit that
>> > > I like the idea behind a ready-to-go-style.
>> > >
>> > >
>> > > Twitter     :http://www.twitter.com/m_cucchiara
>> > > G+          :https://plus.google.com/107903711540963855921
>> > > Linkedin    :http://www.linkedin.com/in/mauriziocucchiara
>> > >
>> > > Maurizio Cucchiara
>> > >
>> > >
>> > >
>> > > 2011/10/20 Olivier Lamy <ol...@apache.org>:
>> > > > Yup check provided files here
>> > > > http://maven.apache.org/developers/committer-environment.html
>> > > > Files exists for idea and eclipse.
>> > > >
>> > > >
>> > > > 2011/10/20 Raffaele P. Guidi <ra...@gmail.com>:
>> > > >> I heard something like automated IDE setup of this? Is it possible?
>> > > >>
>> > > >> On Thursday, October 20, 2011, Akash Ashok <th...@gmail.com>
>> > > wrote:
>> > > >>> +1 on spaces and -1 on tabs. :)  I'd personally prefer 2, but 4
>> also
>> > > >> sounds
>> > > >>> good.
>> > > >>>
>> > > >>> Cheers,
>> > > >>> Akash A
>> > > >>>
>> > > >>> On Thu, Oct 20, 2011 at 7:26 PM, Ioannis Canellos <
>> iocanel@gmail.com
>> > >
>> > > >> wrote:
>> > > >>>
>> > > >>>> I don't like tabs either.
>> > > >>>> I would also like to suggest using 4 spaces ident. I think its the
>> > > most
>> > > >>>> common ident and will help a lot of us changing our settings all
>> the
>> > > >> time.
>> > > >>>>
>> > > >>>> On 20 Οκτ 2011, at 4:52 μ.μ., Olivier Lamy wrote:
>> > > >>>>
>> > > >>>> > Agree something to be defined.
>> > > >>>> > Perso I don't like tabs :-)
>> > > >>>> >
>> > > >>>> > I can propose the maven codestyle if you agree.
>> > > >>>> > All files for ide are here
>> > > >>>> > http://maven.apache.org/developers/committer-environment.html
>> > > >>>> >
>> > > >>>> > And a checktyle file is embeded in the maven checktyle plugin.
>> > > >>>> >
>> > > >>>> > As you want folks
>> > > >>>> >
>> > > >>>> > 2011/10/20 Akash Ashok <th...@gmail.com>:
>> > > >>>> >> I see that we use tabs at someplaces and spaces someplace else
>> > for
>> > > >>>> >> indentation. Do we have a coding guideline in place ?
>> > > >>>> >> If not may be we need to get one in place and have a consistent
>> > > >>>> formatting
>> > > >>>> >> across the entire codebase,
>> > > >>>> >>
>> > > >>>> >> Cheers,
>> > > >>>> >> Akash A
>> > > >>>> >>
>> > > >>>> >
>> > > >>>> >
>> > > >>>> >
>> > > >>>> > --
>> > > >>>> > Olivier Lamy
>> > > >>>> > Talend : http://talend.com
>> > > >>>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>> > > >>>>
>> > > >>>>
>> > > >>>
>> > > >>
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > Olivier Lamy
>> > > > Talend : http://talend.com
>> > > > http://twitter.com/olamy | http://linkedin.com/in/olamy
>> > > >
>> > >
>> >
>>

Re: Code Formatting

Posted by Maurizio Cucchiara <mc...@apache.org>.
> I don't care which code style, because it's like churchs, everyone
> prefers it's own :)
You're right :) and, although I dislike the maven code style, I won't
start a religious war.
Moreover it looks like the maven one is the better defined and widely adopted.

Twitter     :http://www.twitter.com/m_cucchiara
G+          :https://plus.google.com/107903711540963855921
Linkedin    :http://www.linkedin.com/in/mauriziocucchiara

Maurizio Cucchiara

Re: Code Formatting

Posted by Maurizio Cucchiara <mc...@apache.org>.
Good news guys: I have just configured maven checkstyle plugin.
Bad news: there are 2368 checkstyle errors :(
I'm going to fix them, needless to say any help will be appreciated

Twitter     :http://www.twitter.com/m_cucchiara
G+          :https://plus.google.com/107903711540963855921
Linkedin    :http://www.linkedin.com/in/mauriziocucchiara

Maurizio Cucchiara



On 30 December 2011 15:03, Olivier Lamy <ol...@apache.org> wrote:
> Hello,
> Perso cannot agree more :P
>
> 2011/12/30 Raffaele P. Guidi <ra...@gmail.com>:
>> You are right this can turn out complicated. Let's go with the maven
>> standard, then, if the team agre es.
>>
>> Ciao,
>>    R
>> Il giorno 30/dic/2011 14:27, "Maurizio Cucchiara" <
>> maurizio.cucchiara@gmail.com> ha scritto:
>>
>>> Personally I don't like too and as I said before I am not a big fan of this
>>> code style, but I think it's just a matter of taste.
>>> Many of the committers (and maybe some new coming contributors) are
>>> involved in other OS projects, there is a big advantage in choosing a
>>> standard way instead of a permutation of the same style (maven w/o line
>>> breaks,....)
>>> There is an high risk that we get a mix of maven permutations and, beleive
>>> me, it is not so funny to format other's people code
>>>
>>> On 30 December 2011 13:52, Raffaele P. Guidi <ra...@gmail.com>
>>> wrote:
>>> > Agreed with the exception of linea breaks before curly braces
>>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Code Formatting

Posted by Olivier Lamy <ol...@apache.org>.
Hello,
Perso cannot agree more :P

2011/12/30 Raffaele P. Guidi <ra...@gmail.com>:
> You are right this can turn out complicated. Let's go with the maven
> standard, then, if the team agre es.
>
> Ciao,
>    R
> Il giorno 30/dic/2011 14:27, "Maurizio Cucchiara" <
> maurizio.cucchiara@gmail.com> ha scritto:
>
>> Personally I don't like too and as I said before I am not a big fan of this
>> code style, but I think it's just a matter of taste.
>> Many of the committers (and maybe some new coming contributors) are
>> involved in other OS projects, there is a big advantage in choosing a
>> standard way instead of a permutation of the same style (maven w/o line
>> breaks,....)
>> There is an high risk that we get a mix of maven permutations and, beleive
>> me, it is not so funny to format other's people code
>>
>> On 30 December 2011 13:52, Raffaele P. Guidi <ra...@gmail.com>
>> wrote:
>> > Agreed with the exception of linea breaks before curly braces
>>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Code Formatting

Posted by "Raffaele P. Guidi" <ra...@gmail.com>.
You are right this can turn out complicated. Let's go with the maven
standard, then, if the team agre es.

Ciao,
    R
Il giorno 30/dic/2011 14:27, "Maurizio Cucchiara" <
maurizio.cucchiara@gmail.com> ha scritto:

> Personally I don't like too and as I said before I am not a big fan of this
> code style, but I think it's just a matter of taste.
> Many of the committers (and maybe some new coming contributors) are
> involved in other OS projects, there is a big advantage in choosing a
> standard way instead of a permutation of the same style (maven w/o line
> breaks,....)
> There is an high risk that we get a mix of maven permutations and, beleive
> me, it is not so funny to format other's people code
>
> On 30 December 2011 13:52, Raffaele P. Guidi <ra...@gmail.com>
> wrote:
> > Agreed with the exception of linea breaks before curly braces
>

Re: Code Formatting

Posted by Maurizio Cucchiara <ma...@gmail.com>.
Personally I don't like too and as I said before I am not a big fan of this
code style, but I think it's just a matter of taste.
Many of the committers (and maybe some new coming contributors) are
involved in other OS projects, there is a big advantage in choosing a
standard way instead of a permutation of the same style (maven w/o line
breaks,....)
There is an high risk that we get a mix of maven permutations and, beleive
me, it is not so funny to format other's people code

On 30 December 2011 13:52, Raffaele P. Guidi <ra...@gmail.com>
wrote:
> Agreed with the exception of linea breaks before curly braces

Re: Code Formatting

Posted by "Raffaele P. Guidi" <ra...@gmail.com>.
Agreed with the exception of linea breaks before curly braces
Il giorno 30/dic/2011 13:47, "Maurizio Cucchiara" <mc...@apache.org>
ha scritto:

> Ciao Raffaele,
> the only thread about the code style I have found is this one, and I
> still don't understand what style we have chosen.
> Do you agree to use the maven code style pointed out by Olivier [1]
> (see also [2])?
> [1] http://goo.gl/7V2hQ
> [2] http://goo.gl/D8Qxt
>
> Twitter     :http://www.twitter.com/m_cucchiara
> G+          :https://plus.google.com/107903711540963855921
> Linkedin    :http://www.linkedin.com/in/mauriziocucchiara
>
> Maurizio Cucchiara
>
>
>
> On 30 December 2011 13:20, Raffaele P. Guidi <ra...@gmail.com>
> wrote:
> > We already discussed this and there also should be some pointers to
> > configuration files for eclipse. Search in the ml archives.
>

Re: Code Formatting

Posted by Maurizio Cucchiara <mc...@apache.org>.
Ciao Raffaele,
the only thread about the code style I have found is this one, and I
still don't understand what style we have chosen.
Do you agree to use the maven code style pointed out by Olivier [1]
(see also [2])?
[1] http://goo.gl/7V2hQ
[2] http://goo.gl/D8Qxt

Twitter     :http://www.twitter.com/m_cucchiara
G+          :https://plus.google.com/107903711540963855921
Linkedin    :http://www.linkedin.com/in/mauriziocucchiara

Maurizio Cucchiara



On 30 December 2011 13:20, Raffaele P. Guidi <ra...@gmail.com> wrote:
> We already discussed this and there also should be some pointers to
> configuration files for eclipse. Search in the ml archives.

Re: Code Formatting

Posted by "Raffaele P. Guidi" <ra...@gmail.com>.
We already discussed this and there also should be some pointers to
configuration files for eclipse. Search in the ml archives.

Ciao,
   R
Il giorno 30/dic/2011 13:05, "Benoit Perroud" <be...@noisette.ch> ha
scritto:

> absolutely +1
>
> I don't care which code style, because it's like churchs, everyone
> prefers it's own :)
> It's up to you, commiters, to state on this point.
>
>
> 2011/12/30 Maurizio Cucchiara <mc...@apache.org>:
> > Hi all,
> > before it is too late, we should take a decision at this point, the
> > code in terms of formatting is going to become a big mess.
> > I personally saw at least 3 different kinds of code styles.
> > I'd strongly advise to use maven code style (though I'm not nuts about
> > it) and configure maven checkstyle plugin.
> > WDYT?
> >
> >
> > Twitter     :http://www.twitter.com/m_cucchiara
> > G+          :https://plus.google.com/107903711540963855921
> > Linkedin    :http://www.linkedin.com/in/mauriziocucchiara
> >
> > Maurizio Cucchiara
> >
> >
> >
> > On 21 October 2011 21:30, Raffaele P. Guidi <ra...@gmail.com>
> wrote:
> >> I hate line breaks before curly braces - I couldn't stand it even in
> csharp
> >> where it's the standard:
> >>
> >> public class MyMojo
> >> {
> >>
> >>
> >>
> >> Also I find horrible and boring listing function names and parameters
> that
> >> are (or should be) self explicable. Would find them disturbing even if
> they
> >> were automatically generated - but could cope with that if needed
> >>
> >>    /**
> >>     * Artifact factory.
> >>     *
> >>     * @component
> >>     */
> >>    private ArtifactFactory artifactFactory;
> >>
> >>
> >>    //
> ----------------------------------------------------------------------
> >>    // Mojo parameters
> >>    //
> ----------------------------------------------------------------------
> >>
> >>    /**
> >>     * The POM.
> >>     *
> >>     * @parameter expression="${project}"
> >>     * @required
> >>     */
> >>
> >>
> >> Ok for everything else.
> >>
> >> Ciao,
> >>    R
> >>
> >>
> >> 2011/10/21 Akash Ashok <th...@gmail.com>
> >>
> >>> Along with the formatted for eclipse here's a link which defines the
> coding
> >>> standards
> >>>
> >>> http://maven.apache.org/developers/conventions/code.html
> >>>
> >>> It would be nice if we could come to a consensus on the standards soon
> so
> >>> that we dnt run into too much of maintenance issues.
> >>>
> >>> I would like to hear what every1 has to say about it.
> >>>
> >>> Cheers,
> >>> Akash A
> >>>
> >>> 2011/10/21 Raffaele P. Guidi <ra...@gmail.com>
> >>>
> >>> > Yes, nice feature. It's a team saver ;)
> >>> >
> >>> > On Thu, Oct 20, 2011 at 9:40 PM, Maurizio Cucchiara
> >>> > <mc...@apache.org>wrote:
> >>> >
> >>> > > Personally I don't like the maven code style, but I have to admit
> that
> >>> > > I like the idea behind a ready-to-go-style.
> >>> > >
> >>> > >
> >>> > > Twitter     :http://www.twitter.com/m_cucchiara
> >>> > > G+          :https://plus.google.com/107903711540963855921
> >>> > > Linkedin    :http://www.linkedin.com/in/mauriziocucchiara
> >>> > >
> >>> > > Maurizio Cucchiara
> >>> > >
> >>> > >
> >>> > >
> >>> > > 2011/10/20 Olivier Lamy <ol...@apache.org>:
> >>> > > > Yup check provided files here
> >>> > > > http://maven.apache.org/developers/committer-environment.html
> >>> > > > Files exists for idea and eclipse.
> >>> > > >
> >>> > > >
> >>> > > > 2011/10/20 Raffaele P. Guidi <ra...@gmail.com>:
> >>> > > >> I heard something like automated IDE setup of this? Is it
> possible?
> >>> > > >>
> >>> > > >> On Thursday, October 20, 2011, Akash Ashok <
> thehellmaker@gmail.com>
> >>> > > wrote:
> >>> > > >>> +1 on spaces and -1 on tabs. :)  I'd personally prefer 2, but 4
> >>> also
> >>> > > >> sounds
> >>> > > >>> good.
> >>> > > >>>
> >>> > > >>> Cheers,
> >>> > > >>> Akash A
> >>> > > >>>
> >>> > > >>> On Thu, Oct 20, 2011 at 7:26 PM, Ioannis Canellos <
> >>> iocanel@gmail.com
> >>> > >
> >>> > > >> wrote:
> >>> > > >>>
> >>> > > >>>> I don't like tabs either.
> >>> > > >>>> I would also like to suggest using 4 spaces ident. I think
> its the
> >>> > > most
> >>> > > >>>> common ident and will help a lot of us changing our settings
> all
> >>> the
> >>> > > >> time.
> >>> > > >>>>
> >>> > > >>>> On 20 Οκτ 2011, at 4:52 μ.μ., Olivier Lamy wrote:
> >>> > > >>>>
> >>> > > >>>> > Agree something to be defined.
> >>> > > >>>> > Perso I don't like tabs :-)
> >>> > > >>>> >
> >>> > > >>>> > I can propose the maven codestyle if you agree.
> >>> > > >>>> > All files for ide are here
> >>> > > >>>> >
> http://maven.apache.org/developers/committer-environment.html
> >>> > > >>>> >
> >>> > > >>>> > And a checktyle file is embeded in the maven checktyle
> plugin.
> >>> > > >>>> >
> >>> > > >>>> > As you want folks
> >>> > > >>>> >
> >>> > > >>>> > 2011/10/20 Akash Ashok <th...@gmail.com>:
> >>> > > >>>> >> I see that we use tabs at someplaces and spaces someplace
> else
> >>> > for
> >>> > > >>>> >> indentation. Do we have a coding guideline in place ?
> >>> > > >>>> >> If not may be we need to get one in place and have a
> consistent
> >>> > > >>>> formatting
> >>> > > >>>> >> across the entire codebase,
> >>> > > >>>> >>
> >>> > > >>>> >> Cheers,
> >>> > > >>>> >> Akash A
> >>> > > >>>> >>
> >>> > > >>>> >
> >>> > > >>>> >
> >>> > > >>>> >
> >>> > > >>>> > --
> >>> > > >>>> > Olivier Lamy
> >>> > > >>>> > Talend : http://talend.com
> >>> > > >>>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>> > > >>>>
> >>> > > >>>>
> >>> > > >>>
> >>> > > >>
> >>> > > >
> >>> > > >
> >>> > > >
> >>> > > > --
> >>> > > > Olivier Lamy
> >>> > > > Talend : http://talend.com
> >>> > > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>> > > >
> >>> > >
> >>> >
> >>>
>
>
>
> --
> sent from my Nokia 3210
>

Re: Code Formatting

Posted by Benoit Perroud <be...@noisette.ch>.
absolutely +1

I don't care which code style, because it's like churchs, everyone
prefers it's own :)
It's up to you, commiters, to state on this point.


2011/12/30 Maurizio Cucchiara <mc...@apache.org>:
> Hi all,
> before it is too late, we should take a decision at this point, the
> code in terms of formatting is going to become a big mess.
> I personally saw at least 3 different kinds of code styles.
> I'd strongly advise to use maven code style (though I'm not nuts about
> it) and configure maven checkstyle plugin.
> WDYT?
>
>
> Twitter     :http://www.twitter.com/m_cucchiara
> G+          :https://plus.google.com/107903711540963855921
> Linkedin    :http://www.linkedin.com/in/mauriziocucchiara
>
> Maurizio Cucchiara
>
>
>
> On 21 October 2011 21:30, Raffaele P. Guidi <ra...@gmail.com> wrote:
>> I hate line breaks before curly braces - I couldn't stand it even in csharp
>> where it's the standard:
>>
>> public class MyMojo
>> {
>>
>>
>>
>> Also I find horrible and boring listing function names and parameters that
>> are (or should be) self explicable. Would find them disturbing even if they
>> were automatically generated - but could cope with that if needed
>>
>>    /**
>>     * Artifact factory.
>>     *
>>     * @component
>>     */
>>    private ArtifactFactory artifactFactory;
>>
>>
>>    // ----------------------------------------------------------------------
>>    // Mojo parameters
>>    // ----------------------------------------------------------------------
>>
>>    /**
>>     * The POM.
>>     *
>>     * @parameter expression="${project}"
>>     * @required
>>     */
>>
>>
>> Ok for everything else.
>>
>> Ciao,
>>    R
>>
>>
>> 2011/10/21 Akash Ashok <th...@gmail.com>
>>
>>> Along with the formatted for eclipse here's a link which defines the coding
>>> standards
>>>
>>> http://maven.apache.org/developers/conventions/code.html
>>>
>>> It would be nice if we could come to a consensus on the standards soon so
>>> that we dnt run into too much of maintenance issues.
>>>
>>> I would like to hear what every1 has to say about it.
>>>
>>> Cheers,
>>> Akash A
>>>
>>> 2011/10/21 Raffaele P. Guidi <ra...@gmail.com>
>>>
>>> > Yes, nice feature. It's a team saver ;)
>>> >
>>> > On Thu, Oct 20, 2011 at 9:40 PM, Maurizio Cucchiara
>>> > <mc...@apache.org>wrote:
>>> >
>>> > > Personally I don't like the maven code style, but I have to admit that
>>> > > I like the idea behind a ready-to-go-style.
>>> > >
>>> > >
>>> > > Twitter     :http://www.twitter.com/m_cucchiara
>>> > > G+          :https://plus.google.com/107903711540963855921
>>> > > Linkedin    :http://www.linkedin.com/in/mauriziocucchiara
>>> > >
>>> > > Maurizio Cucchiara
>>> > >
>>> > >
>>> > >
>>> > > 2011/10/20 Olivier Lamy <ol...@apache.org>:
>>> > > > Yup check provided files here
>>> > > > http://maven.apache.org/developers/committer-environment.html
>>> > > > Files exists for idea and eclipse.
>>> > > >
>>> > > >
>>> > > > 2011/10/20 Raffaele P. Guidi <ra...@gmail.com>:
>>> > > >> I heard something like automated IDE setup of this? Is it possible?
>>> > > >>
>>> > > >> On Thursday, October 20, 2011, Akash Ashok <th...@gmail.com>
>>> > > wrote:
>>> > > >>> +1 on spaces and -1 on tabs. :)  I'd personally prefer 2, but 4
>>> also
>>> > > >> sounds
>>> > > >>> good.
>>> > > >>>
>>> > > >>> Cheers,
>>> > > >>> Akash A
>>> > > >>>
>>> > > >>> On Thu, Oct 20, 2011 at 7:26 PM, Ioannis Canellos <
>>> iocanel@gmail.com
>>> > >
>>> > > >> wrote:
>>> > > >>>
>>> > > >>>> I don't like tabs either.
>>> > > >>>> I would also like to suggest using 4 spaces ident. I think its the
>>> > > most
>>> > > >>>> common ident and will help a lot of us changing our settings all
>>> the
>>> > > >> time.
>>> > > >>>>
>>> > > >>>> On 20 Οκτ 2011, at 4:52 μ.μ., Olivier Lamy wrote:
>>> > > >>>>
>>> > > >>>> > Agree something to be defined.
>>> > > >>>> > Perso I don't like tabs :-)
>>> > > >>>> >
>>> > > >>>> > I can propose the maven codestyle if you agree.
>>> > > >>>> > All files for ide are here
>>> > > >>>> > http://maven.apache.org/developers/committer-environment.html
>>> > > >>>> >
>>> > > >>>> > And a checktyle file is embeded in the maven checktyle plugin.
>>> > > >>>> >
>>> > > >>>> > As you want folks
>>> > > >>>> >
>>> > > >>>> > 2011/10/20 Akash Ashok <th...@gmail.com>:
>>> > > >>>> >> I see that we use tabs at someplaces and spaces someplace else
>>> > for
>>> > > >>>> >> indentation. Do we have a coding guideline in place ?
>>> > > >>>> >> If not may be we need to get one in place and have a consistent
>>> > > >>>> formatting
>>> > > >>>> >> across the entire codebase,
>>> > > >>>> >>
>>> > > >>>> >> Cheers,
>>> > > >>>> >> Akash A
>>> > > >>>> >>
>>> > > >>>> >
>>> > > >>>> >
>>> > > >>>> >
>>> > > >>>> > --
>>> > > >>>> > Olivier Lamy
>>> > > >>>> > Talend : http://talend.com
>>> > > >>>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>>> > > >>>>
>>> > > >>>>
>>> > > >>>
>>> > > >>
>>> > > >
>>> > > >
>>> > > >
>>> > > > --
>>> > > > Olivier Lamy
>>> > > > Talend : http://talend.com
>>> > > > http://twitter.com/olamy | http://linkedin.com/in/olamy
>>> > > >
>>> > >
>>> >
>>>



-- 
sent from my Nokia 3210