[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wsas-java-dev
Subject:    Re: [Dev] Better to stop using $project.version in branch poms
From:       Supun Malinga <supunm () wso2 ! com>
Date:       2013-01-30 5:52:06
Message-ID: CACd4kV+vo_6L=Q1LQCupnQH-Ktb_pmFZzPVXNqa6botHTOc8ig () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi Tharindu,

+1
That's the correct way to do. But we tend to simply change the versions
manually..

thanks,


On Wed, Jan 30, 2013 at 10:36 AM, Tharindu Mathew <tharindu@wso2.com> wrote:

> Hi,
>
> I have seen that the maven property project.version has been used by many
> in poms. I believe it's a better practice to define the version in
> properties like <carbon.platform.patch.version.407>
>
> What happens otherwise is when a new version of the component or feature
> is made, it will eventually break the build. This is because some of the
> dependencies will not have the new version of the component. In the case of
> the feature, sometimes you will not know you broke the build until a
> product's p2-profile-gen is built.
>
> WDYT?
>
> --
> Regards,
>
> Tharindu Mathew
>
> Associate Technical Lead, WSO2 BAM
> Member - Data Mgmt. Committee
>
> blog: http://tharindumathew.com/
> M: +94777759908
>
> _______________________________________________
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Supun Malinga,

Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - supunm@wso2.com <supuna@wso2.com>
mobile - 071 56 91 321

[Attachment #5 (text/html)]

<div dir="ltr">Hi Tharindu,<div><br></div><div>+1</div><div style>That&#39;s the \
correct way to do. But we tend to simply change the versions manually.. </div><div \
style><br></div><div style>thanks,</div></div><div class="gmail_extra">

<br><br><div class="gmail_quote">On Wed, Jan 30, 2013 at 10:36 AM, Tharindu Mathew \
<span dir="ltr">&lt;<a href="mailto:tharindu@wso2.com" \
target="_blank">tharindu@wso2.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">

Hi,<br><br>I have seen that the maven property project.version has been used by many \
in poms. I believe it&#39;s a better practice to define the version in properties \
like &lt;carbon.platform.patch.version.407&gt;<br><br>

What happens otherwise is when a new version of the component or feature is made, it \
will eventually break the build. This is because some of the dependencies will not \
have the new version of the component. In the case of the feature, sometimes you will \
not know you broke the build until a product&#39;s p2-profile-gen is built.<br>



<br>WDYT?<span class="HOEnZb"><font color="#888888"><br clear="all"><br>-- \
<br>Regards,<br><br>Tharindu Mathew<br><br>Associate Technical Lead, WSO2 \
BAM<br>Member - Data Mgmt. Committee<br><div><br></div><div>blog: <a \
href="http://tharindumathew.com/" \
target="_blank">http://tharindumathew.com/</a></div>



<div>M: <a href="tel:%2B94777759908" value="+94777759908" \
target="_blank">+94777759908</a></div> \
</font></span><br>_______________________________________________<br> Dev mailing \
list<br> <a href="mailto:Dev@wso2.org">Dev@wso2.org</a><br>
<a href="http://wso2.org/cgi-bin/mailman/listinfo/dev" \
target="_blank">http://wso2.org/cgi-bin/mailman/listinfo/dev</a><br> \
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Supun \
Malinga,<br><br>Software Engineer,<br>WSO2 Inc.<br><a href="http://wso2.com" \
target="_blank">http://wso2.com</a><br><a href="http://wso2.org" \
target="_blank">http://wso2.org</a><br>

email - <a href="mailto:supuna@wso2.com" \
target="_blank">supunm@wso2.com</a><br>mobile - 071 56 91 321<br> </div>



_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[prev in list] [next in list] [prev in thread] [next in thread]