Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

On Wed, Jan 6, 2016 at 4:02 PM, Afkham Azeez wrote: > You may have to build the whole product because the POM is not hosted yet > The simplest solution is temporally add staging repo [1] into the sample POM file. [1] -

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

You may have to build the whole product because the POM is not hosted yet On Wed, Jan 6, 2016 at 3:56 PM, Udara Liyanage wrote: > Hi, > > I get following error when I tried building hello world sample inside the > product. Is this a known issue? > > Non-resolvable parent POM for

[Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

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

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

Hi, I get following error when I tried building hello world sample inside the product. Is this a known issue? Non-resolvable parent POM for org.wso2.carbon.mss.sample:helloworld:[unknown-version]: Could not find artifact org.wso2.carbon.mss:mss-lite-parent:pom:1.0.0 in central (

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

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 wrote: >

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

Hi, Additionally I don't think the MSS samples are very developer friendly. I think we have gone too far to minimize pom.xmls. 1 - In deployble-jar sample I was trying to figure out which plugin is copying the property "Microservices" to the MANIFEST.MF file. The following very important plugin

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

Currently deployable jars have access to the classes in mss bundle. That is how the deployable jars have access to mss annotations etc. IMO the deployable jars were expected to have their dependencies inside themselves. But, If we need to provide access to classes exported by all other bundles

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

No I totally disagree with you. We have made our POMs less verbose so that the developers can focus on what is necessary. We put in a lot of thought before going for this minimized POMs. Instead of copying & pasting a lot of XML, you focus on only the bits that are relevant to your microservice

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

OSGi experts, is there a better way to do this rather than add DynamicImport-Packages: * ? On Thu, Jan 7, 2016 at 11:09 AM, Samiyuru Senarathne wrote: > Currently deployable jars have access to the classes in mss bundle. That > is how the deployable jars have access to mss

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

On Thu, Jan 7, 2016 at 11:51 AM, Dimuthu Leelarathne wrote: > > > On Thu, Jan 7, 2016 at 11:18 AM, Afkham Azeez wrote: > >> No I totally disagree with you. We have made our POMs less verbose so >> that the developers can focus on what is necessary. We put in a

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

We prefer that people don't copy & paste loads of XML, make mistakes, and make it difficult for us to make changes in the future, and we prefer to simply document the relevant properties people need to be aware of to make their life easy. On Thu, Jan 7, 2016 at 12:09 PM, Dimuthu Leelarathne