Hi Sameera, Azeez, On Mon, Feb 28, 2011 at 9:28 PM, Afkham Azeez <[email protected]> wrote:
> Yes, this has been added by registry folks. Henceforth, nobody should make > changes to dependencies without consulting others. I think we should have a > team responsible for approving such dependency changes. > > On Mon, Feb 28, 2011 at 3:02 PM, Sameera Jayasoma <[email protected]>wrote: > >> Hi >> >> We are using Abdera 1.0 version and Abdera-extensions 0.4 in Carbon >> trunk. These are the versions wrapped as orbits. It seems like we have >> recently added an Abdera branch to trunk/dependencies. Please inform the >> list if you doing such drastic changes. >> >> Btw, inside this Abdera branch, Abdera-extensions version 1.0 module is >> also available. Why are we not using that instead an older version of abdera >> extensions (0.4)? >> > We should be using 1.0.0.wso2v2 and not 0.4. The 1.0.0.wso2v1 version of Abdera was introduced sometime back, and at that point in time, we decided to move to this version of Abdera, which has not happened in the Mashup components. And, FYI, non of the registry components use the abdera-extensions dependency. However, I don't understand what you mean by drastic in here, since all that has been done is patching the existing 1.0.0.wso2v1 version of Abdera to suit some recent changes done to Axiom. API changes in Axiom are not backward compatible, and there are lots of bad practices with regard to deprecation. But these changes are correcting the initial design flaws, and moving backwards does not seem to be the right choice. So, after having an offline discussion with Samisa, we decided to fix Abdera instead of Axiom. So, in essence, what happened was the introduction of Abdera 1.0.0.wso2v2 which adds a minor fix to Abdera 1.0.0.wso2v2. And, we need to fix the dependency versions of the Mashup components which use an ancient release of Abdera, :). Thanks, Senaka. > >> Thanks >> Sameera >> >> -- >> Sameera Jayasoma >> Technical Lead and Product Manager, WSO2 Carbon >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> blog: http://tech.jayasoma.org >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > *Afkham Azeez* > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, > * > * > *Member; Apache Software Foundation; > **http://www.apache.org/*<http://www.apache.org/> > * > email: **[email protected]* <[email protected]>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2, Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://www.linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
