HI Samisa, The reason for this is that UES was released with a more later version of Jaggery. Jaggery which is in AS is quite old (4.1.0 initial release), We have branched from jaggery trunk for carbon 4.2.0 and with next platform release AS and AF will be updated to new Jaggery.
Regards, /Nuwan On Wed, Aug 7, 2013 at 5:53 AM, Samisa Abeysinghe <[email protected]> wrote: > What is the $subject? > > For e.g. we have faced this issue with the internal project we ran. UES > features we use in WES does not work with the AS version. > > Now, this could be seen as an AS issue. Yet, for us now, given the move to > AF, it is an AF issue too... > > -- > > Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Thanks & Regards, Nuwan Bandara Technical Lead; **WSO2 Inc. * *lean . enterprise . middleware | http://wso2.com * *blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 9629 * <http://www.nuwanbando.com/>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
