DimuthuL reported that in the case of deployable jar mode, the classes coming from OSGi bundles in the enviroment are not visible to the classes inside the deployable jar. I think this is a blocker for the release.
On Wed, Jan 6, 2016 at 3:29 PM, Samiyuru Senarathne <samiy...@wso2.com> wrote: > Hi Devs, > > This is the 2nd Release Candidate of WSO2 Microservices Server 1.0.0. > > Please download, test the product and vote. > > *​Source and binary distribution files:* > https://github.com/wso2/product-mss/releases/tag/v1.0.0-RC2 > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fwso2%2Fproduct-mss%2Freleases%2Ftag%2Fv1.0.0-RC2&sa=D&sntz=1&usg=AFQjCNEPlH9995oXWdOhW8f6_PUmLlt0cw> > > *Maven staging repository:* > http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-274 > > *The tag to be voted upon:* > *https://github.com/wso2/product-mss/tree/v1.0.0-RC2 > <https://github.com/wso2/product-mss/tree/v1.0.0-RC2>* > > > [ ] Broken - do not release (explain why) > [ ] Stable - go ahead and release > > Note: Since the artifacts that have to be uploaded to the maven central > are not yet uploaded please make sure to first build the project from the > source in order to make all artifacts available in the maven local > repository. > > Thank you, > Carbon Team > > -- > Samiyuru Senarathne > *Software Engineer* > Mobile : +94 (0) 71 134 6087 > samiy...@wso2.com > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>* *email: **az...@wso2.com* <az...@wso2.com> * cell: +94 77 3320919blog: **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 <http://lk.linkedin.com/in/afkhamazeez>* *Lean . Enterprise . Middleware*
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
