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
