You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Abhijit Sarkar <so...@outlook.com> on 2014/01/23 06:57:22 UTC
CDI parent pom
I was going through the CDI examples today and all of them declare the same things over and over again (compiler plugin, dependencies, ...). I propose that the commonalities are centralized in a parent pom. That way, if we ever wanted to migrate all these example from Java 6 (current configuration) to Java 7, we could change one pom and not a dozen. Of course the Java migration is a lame example, but you get the point.
I'm volunteering if this sounds like a good idea.
Regards,Abhijit
Re: CDI parent pom
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Sorry I don't get the point, you can check all examples you want this
way and each time you just play with it and not others or a weird
hierarchy like other examples source bases which are not usable when
you want to check a single feature. The only drawback is for us which
is small enough to be assumed IMO.
That said if you want to create a little utility ensuring we use the
latest openejb/tomee and javaee version (from org.apache.openejb of
course) it can be useful for releases.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014/1/23 Abhijit Sarkar <so...@outlook.com>:
> It can be reasoned that someone who could check out one project, could do another one as well. Seems like a deviation from DRY.
> Anyway, it was just a suggestion.
>
>
>> Date: Thu, 23 Jan 2014 07:12:08 +0100
>> Subject: Re: CDI parent pom
>> From: rmannibucau@gmail.com
>> To: dev@tomee.apache.org
>>
>> Hi
>>
>> The goal is the following: download the example and run it without needing
>> anything else so I think we should keep it. Btw updating it can be done
>> with sed or mvn version plugin iirc so not an issue in practise.
>>
>> Le jeudi 23 janvier 2014, Abhijit Sarkar <so...@outlook.com> a écrit :
>> > I was going through the CDI examples today and all of them declare the
>> same things over and over again (compiler plugin, dependencies, ...). I
>> propose that the commonalities are centralized in a parent pom. That way,
>> if we ever wanted to migrate all these example from Java 6 (current
>> configuration) to Java 7, we could change one pom and not a dozen. Of
>> course the Java migration is a lame example, but you get the point.
>> > I'm volunteering if this sounds like a good idea.
>> > Regards,Abhijit
>>
>> --
>> *Romain Manni-Bucau*
>> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>> *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
>> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau
>> <http://fr.linkedin.com/in/rmannibucau>*
>> *Github: https://github.com/rmannibucau <https://github.com/rmannibucau>*
>
RE: CDI parent pom
Posted by Abhijit Sarkar <so...@outlook.com>.
It can be reasoned that someone who could check out one project, could do another one as well. Seems like a deviation from DRY.
Anyway, it was just a suggestion.
> Date: Thu, 23 Jan 2014 07:12:08 +0100
> Subject: Re: CDI parent pom
> From: rmannibucau@gmail.com
> To: dev@tomee.apache.org
>
> Hi
>
> The goal is the following: download the example and run it without needing
> anything else so I think we should keep it. Btw updating it can be done
> with sed or mvn version plugin iirc so not an issue in practise.
>
> Le jeudi 23 janvier 2014, Abhijit Sarkar <so...@outlook.com> a écrit :
> > I was going through the CDI examples today and all of them declare the
> same things over and over again (compiler plugin, dependencies, ...). I
> propose that the commonalities are centralized in a parent pom. That way,
> if we ever wanted to migrate all these example from Java 6 (current
> configuration) to Java 7, we could change one pom and not a dozen. Of
> course the Java migration is a lame example, but you get the point.
> > I'm volunteering if this sounds like a good idea.
> > Regards,Abhijit
>
> --
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau
> <http://fr.linkedin.com/in/rmannibucau>*
> *Github: https://github.com/rmannibucau <https://github.com/rmannibucau>*
Re: CDI parent pom
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
The goal is the following: download the example and run it without needing
anything else so I think we should keep it. Btw updating it can be done
with sed or mvn version plugin iirc so not an issue in practise.
Le jeudi 23 janvier 2014, Abhijit Sarkar <so...@outlook.com> a écrit :
> I was going through the CDI examples today and all of them declare the
same things over and over again (compiler plugin, dependencies, ...). I
propose that the commonalities are centralized in a parent pom. That way,
if we ever wanted to migrate all these example from Java 6 (current
configuration) to Java 7, we could change one pom and not a dozen. Of
course the Java migration is a lame example, but you get the point.
> I'm volunteering if this sounds like a good idea.
> Regards,Abhijit
--
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau
<http://fr.linkedin.com/in/rmannibucau>*
*Github: https://github.com/rmannibucau <https://github.com/rmannibucau>*