If we do changes (in future) then we can solve that then :-) e.g. we can do two releases.
Paul On 14 March 2011 07:13, Isuru Suriarachchi <[email protected]> wrote: > > > On Mon, Mar 14, 2011 at 12:33 PM, Samisa Abeysinghe <[email protected]>wrote: > >> >> >> On Mon, Mar 14, 2011 at 12:28 PM, Isuru Suriarachchi <[email protected]>wrote: >> >>> >>> >>> On Mon, Mar 14, 2011 at 12:23 PM, Samisa Abeysinghe <[email protected]>wrote: >>> >>>> >>>> >>>> On Mon, Mar 14, 2011 at 12:19 PM, Isuru Suriarachchi <[email protected]>wrote: >>>> >>>>> >>>>> >>>>> On Mon, Mar 14, 2011 at 7:41 AM, Samisa Abeysinghe <[email protected]>wrote: >>>>> >>>>>> We have branched the codependencies already for the trunk. So we can >>>>>> deploy these plugins to maven repo. >>>>>> Pradeep please note! >>>>>> >>>>> >>>>> I think the solution should be to refer to the last released version >>>>> rather than deploying the current version. That's what we've been doing in >>>>> previous releases as well. >>>>> >>>> >>>> We will never patch these plugins, would we? If so why not just deploy >>>> them? >>>> >>> >>> Yes normally we don't patch those :). But the safer (or theoretically >>> correct) option is to go with the latest released version. >>> >> >> But in theory, that is wrong too, you are building version X with version >> X-1 plugin. >> > > Yes if the version X-1 plugin is compatible with version X, there's nothing > wrong in doing that. But when we deploy the new plugin, if we'll come up > with a change later, we are in trouble :). > > Anyway for this particular problem, both ways are ok as we don't do changes > in these plugins. > > Thanks, > ~Isuru > > >> >> Thanks, >> Samisa... >> >> Samisa Abeysinghe >> VP Engineering >> WSO2 Inc. >> http://wso2.com >> http://wso2.org >> >> >> > > > > -- > Isuru Suriarachchi > Technical Lead & Product Manager, WSO2 Application Server > > WSO2 Inc. http://wso2.com > email : [email protected] > blog : http://isurues.wordpress.com/ > > lean . enterprise . middleware > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse Office: +44 844 484 8143 Cell: +44 798 447 4618 blog: http://pzf.fremantle.org twitter.com/pzfreo [email protected] wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
