On Thu, Mar 6, 2014 at 1:02 AM, Sagara Gunathunga <sag...@wso2.com> wrote:

>
>
>
> On Thu, Mar 6, 2014 at 12:31 AM, Madhuka Udantha <madh...@wso2.com> wrote:
>
>> Hi,
>>
>> Currently jaggery master[1] features[2] and components pom files are also
>> parent POM files.
>> we used to added jaggery component as svn external to svn also we have to
>> release jaggery repo each time.
>> As other products moving in to Git[3] and jaggery contain it's component
>> inside jaggery product so when even we release jaggery-component means we
>> have to release jaggery.
>>
>> Therefore are we going to have only one root(parent) pom for jaggery (in
>> root level) or we will continue as jaggery was. (Where we have parent pom
>> for components and features)?
>>
>
> We have separated code base into number of GItHub repos in a logical
> manner so that sub-modules/components of a particular repo get released
> together and will use  same version number, with this explanation it's
> logical to have only one parent POM per GitHub repo. In technical side this
> rule make ease for snapshot based development and  make it possible to
> apply Maven release plugin for releases. in my POV it's make sense to have
> one parent POM for  jaggery.
>
>>
>> Where Other WSO2 product will have only one root parent pom as[3].
>>
>
> Yes this will be a compulsory rule to execute new development governance
> process and we are developing some tooling support to check this.
>
Currently I have created and built jaggery brunch[1] from one root pom
(parent pom).

I am +1 for to have one parent pom for jaggery as wso2 product moving to
git.

[1] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0

>
> Thanks !
>
>>
>> [1] https://github.com/wso2/jaggery
>> [2] https://github.com/wso2/jaggery/blob/master/features/pom.xml
>> [3] Email Subjected "Guidelines to move project into GitHub" @
>> dev@wso2.org
>>
>> Thanks
>> --
>> *Madhuka* Udantha
>> Senior Software Engineer
>> Development Technologies
>> WSO2 Inc. : http://wso2.com
>>
>> *Mobile*: +94774066336
>> *Blog*: http://madhukaudantha.blogspot.com/
>>
>
>
>
> --
> Sagara Gunathunga
>
> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;    http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
>
>


-- 
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com

*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to