On Thu, Jan 7, 2016 at 11:51 AM, Dimuthu Leelarathne <dimut...@wso2.com>
wrote:
>
>
> On Thu, Jan 7, 2016 at 11:18 AM, Afkham Azeez <az...@wso2.com> 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 <dimut...@wso2.com>
>> 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.
>>>
>>> <plugin>
>>> <groupId>org.apache.maven.plugins</groupId>
>>> <artifactId>maven-jar-plugin</artifactId>
>>> <configuration>
>>> <archive>
>>> <manifestEntries>
>>> <Microservices>$
>>> {microservice.resourceClasses}
>>>
>>> </Microservices>
>>> </manifestEntries>
>>> </archive>
>>> </configuration>
>>> </plugin>
>>>
>>> 2 - Bunle sample is worse. I had to trace back to following pom to take
>>> the bundle plugin (with Samiyuru's help).
>>>
>>> <groupId>org.wso2</groupId>
>>> <artifactId>wso2</artifactId>
>>> <version>2</version>
>>>
>>>
>>> thanks,
>>>
>>> Dimuthu
>>>
>>>
>>>
>>> On Wed, Jan 6, 2016 at 11:18 PM, Afkham Azeez <az...@wso2.com> 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
>>>>> <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 3320919 <%2B94%2077%203320919>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
>>>> <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/
>> * <http://www.apache.org/>*
>> *email: **az...@wso2.com* <az...@wso2.com>
>> * cell: +94 77 3320919 <%2B94%2077%203320919>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
>> <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. (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
