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

2016-01-06 Thread Sagara Gunathunga
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] - http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-274/


Thanks !

>
> 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
>> 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 (
>> https://repo.maven.apache.org/maven2) and 'parent.relativePath' points
>> at wrong local POM @ line 22, column 13
>>
>> On Wed, Jan 6, 2016 at 3:29 PM, Samiyuru Senarathne 
>> 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
>>> 
>>>
>>> *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
>>> *
>>>
>>>
>>> [ ] 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
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> web: http://udaraliyanage.wordpress.com
>> phone: +94 71 443 6897
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sagara Gunathunga

Architect; WSO2, Inc.;  http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ;  http://ssagara.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


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

2016-01-06 Thread Afkham Azeez
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
> 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 (
> https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
> wrong local POM @ line 22, column 13
>
> On Wed, Jan 6, 2016 at 3:29 PM, Samiyuru Senarathne 
> 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
>> 
>>
>> *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
>> *
>>
>>
>> [ ] 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
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


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

2016-01-06 Thread Samiyuru Senarathne
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


*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
*


[ ] 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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


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

2016-01-06 Thread Udara Liyanage
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 (
https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
wrong local POM @ line 22, column 13

On Wed, Jan 6, 2016 at 3:29 PM, Samiyuru Senarathne 
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
> 
>
> *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
> *
>
>
> [ ] 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
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


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

2016-01-06 Thread Afkham Azeez
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:

> 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
> 
>
> *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
> *
>
>
> [ ] 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/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


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

2016-01-06 Thread Dimuthu Leelarathne
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 is missing in the immediate pom file and hence the
sample is not very useful.


org.apache.maven.plugins
maven-jar-plugin



$
{microservice.resourceClasses}







2 - Bunle sample is worse. I had to trace back to following pom to take the
bundle plugin (with Samiyuru's help).

org.wso2
wso2
2


thanks,

Dimuthu



On Wed, Jan 6, 2016 at 11:18 PM, Afkham Azeez  wrote:

> 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:
>
>> 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
>> 
>>
>> *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
>> *
>>
>>
>> [ ] 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/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



-- 
Dimuthu Leelarathne
Director

WSO2, Inc. (http://wso2.com)
email: dimut...@wso2.com
Mobile : 0773661935

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


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

2016-01-06 Thread Samiyuru Senarathne
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
that we cannot assume ahead, I think we will have to add dynamic import to
mss bundle. That way deployable jars will also see all exported classes
since mss bundle gets to see them.

On Wed, Jan 6, 2016 at 11:18 PM, Afkham Azeez  wrote:

> 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:
>
>> 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
>> 
>>
>> *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
>> *
>>
>>
>> [ ] 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/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



-- 
Samiyuru Senarathne
*Software Engineer*
Mobile : +94 (0) 71 134 6087
samiy...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


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

2016-01-06 Thread Afkham Azeez
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
bundle or jar. With some basic Maven knowledge, you can figure out from
where the relevant plugins are inherited.

On Thu, Jan 7, 2016 at 10:50 AM, Dimuthu Leelarathne 
wrote:

> 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 is missing in the immediate pom file and hence the
> sample is not very useful.
>
> 
> org.apache.maven.plugins
> maven-jar-plugin
> 
> 
> 
> $
> {microservice.resourceClasses}
>
> 
> 
> 
> 
> 
>
> 2 - Bunle sample is worse. I had to trace back to following pom to take
> the bundle plugin (with Samiyuru's help).
>
> org.wso2
> wso2
> 2
>
>
> thanks,
>
> Dimuthu
>
>
>
> On Wed, Jan 6, 2016 at 11:18 PM, Afkham Azeez  wrote:
>
>> 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:
>>
>>> 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
>>> 
>>>
>>> *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
>>> *
>>>
>>>
>>> [ ] 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/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> Dimuthu Leelarathne
> Director
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
> Mobile : 0773661935
>
> Lean . Enterprise . Middleware
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


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

2016-01-06 Thread Afkham Azeez
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 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
> that we cannot assume ahead, I think we will have to add dynamic import to
> mss bundle. That way deployable jars will also see all exported classes
> since mss bundle gets to see them.
>
> On Wed, Jan 6, 2016 at 11:18 PM, Afkham Azeez  wrote:
>
>> 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:
>>
>>> 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
>>> 
>>>
>>> *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
>>> *
>>>
>>>
>>> [ ] 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/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> 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/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


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

2016-01-06 Thread Dimuthu Leelarathne
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 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 bundle or jar. With some basic Maven knowledge, you can figure
>> out from where the relevant plugins are inherited.
>>
>
>
> Yes. One can figure out. But, not developer friendly. IMO, we need to
> include the jar-plugin configuration. That is not making it verbose, but
> rather user friendly.
>

Why do I have to browse the internet looking for a pom file (if I haven't
built the MSS myself)? I believe we need to minimally include the
jar-plugin configuration.


>
>
>
>>
>> On Thu, Jan 7, 2016 at 10:50 AM, Dimuthu Leelarathne 
>> wrote:
>>
>>> 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 is missing in the immediate pom file and hence the
>>> sample is not very useful.
>>>
>>> 
>>> org.apache.maven.plugins
>>> maven-jar-plugin
>>> 
>>> 
>>> 
>>> $
>>> {microservice.resourceClasses}
>>>
>>> 
>>> 
>>> 
>>> 
>>> 
>>>
>>> 2 - Bunle sample is worse. I had to trace back to following pom to take
>>> the bundle plugin (with Samiyuru's help).
>>>
>>> org.wso2
>>> wso2
>>> 2
>>>
>>>
>>> thanks,
>>>
>>> Dimuthu
>>>
>>>
>>>
>>> On Wed, Jan 6, 2016 at 11:18 PM, Afkham Azeez  wrote:
>>>
 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:

> 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
> 
>
> *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
> *
>
>
> [ ] 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/
 * *
 *email: **az...@wso2.com* 
 * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
 *http://blog.afkham.org* 
 *twitter: **http://twitter.com/afkham_azeez*
 
 *linked-in: **http://lk.linkedin.com/in/afkhamazeez
 *

 *Lean . Enterprise . Middleware*

>>>
>>>
>>>
>>> --
>>> Dimuthu Leelarathne
>>> Director
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: dimut...@wso2.com
>>> Mobile : 0773661935
>>>
>>> Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> Dimuthu Leelarathne
> Director
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
> Mobile : 0773661935
>
> Lean . Enterprise . Middleware
>



-- 
Dimuthu Leelarathne
Director

WSO2, Inc. 

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

2016-01-06 Thread Afkham Azeez
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 
wrote:

> I prefer not to search internet for a pom/plugin when I have not built MSS.
>
> On Thu, Jan 7, 2016 at 12:02 PM, Afkham Azeez  wrote:
>
>> What you are saying is, you don't like;
>>
>> 
>> 
>> org.wso2.carbon.mss.example.Application
>> 
>>
>>
>> You prefer;
>>
>> 
>> org.apache.maven.plugins
>> maven-shade-plugin
>> 
>> 
>> package
>> 
>> shade
>> 
>> 
>> 
>> 
>> *:*
>> 
>> META-INF/*.SF
>> META-INF/*.DSA
>> META-INF/*.RSA
>> 
>> 
>> 
>> 
>> > 
>> implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
>> ${microservice.mainClass}
>> 
>> 
>> 
>> 
>> 
>> 
>>
>> and you want to copy and paste all this every time.
>>
>>
>>
>> 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 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 bundle or jar. With some basic Maven knowledge, you can figure
 out from where the relevant plugins are inherited.

>>>
>>>
>>> Yes. One can figure out. But, not developer friendly. IMO, we need to
>>> include the jar-plugin configuration. That is not making it verbose, but
>>> rather user friendly.
>>>
>>>
>>>

 On Thu, Jan 7, 2016 at 10:50 AM, Dimuthu Leelarathne  wrote:

> 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 is missing in the immediate pom file and hence the
> sample is not very useful.
>
> 
> org.apache.maven.plugins
> maven-jar-plugin
> 
> 
> 
> $
> {microservice.resourceClasses}
>
> 
> 
> 
> 
> 
>
> 2 - Bunle sample is worse. I had to trace back to following pom to
> take the bundle plugin (with Samiyuru's help).
>
> org.wso2
> wso2
> 2
>
>
> thanks,
>
> Dimuthu
>
>
>
> On Wed, Jan 6, 2016 at 11:18 PM, Afkham Azeez  wrote:
>
>> 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
>>> 
>>>
>>> *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
>>> *
>>>
>>>
>>> [ ] 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
>>>
>>
>>
>>
>> --
>>