+1 On Fri, Oct 31, 2014 at 2:48 PM, Kasun De Silva <[email protected]> wrote:
> Hi All, > > Since we are implementing native way of versioning mechanism for .NET > apptypes, we no longer need the pom.xml created with the archetype. So IMO > we should not keep it, WDYT? > > Thanks, > Kasun > > *Kasun de Silva* > Software Engineer | *WSO2 Inc.*; http://wso2.com > lean.enterprise.middleware > > email : [email protected] > mobile : +94 77 794 4260 > > > On Fri, Oct 31, 2014 at 1:35 PM, Gayan Dhanushka <[email protected]> wrote: > >> Hi Roshan, >> >> AFAIK this comes in the archetype generation time. When we are creating a >> new version what happens is we clone the original repository which has the >> above format and replace the source version with the target version. >> >> Regards >> GayanD >> >> On Fri, Oct 31, 2014 at 1:14 PM, Roshan Deniyage <[email protected]> >> wrote: >> >>> In all the app types, application versioning is done according to the >>> format "<APP_NAME>-<APP_VERSION>-default". Here, what is the use of >>> "-default" part? Is it just a string? >>> >>> Roshan Deniyage >>> Associate Technical Lead >>> WSO2, Inc: http://wso2.com >>> >>> Mobile : +94 777636406 >>> Twitter : *https://twitter.com/roshku <https://twitter.com/roshku>* >>> LinkedIn : https://www.linkedin.com/in/roshandeniyage >>> >>> >>> On Fri, Oct 31, 2014 at 11:16 AM, Danushka Fernando <[email protected]> >>> wrote: >>> >>>> Hi Gayan >>>> Where this versioning concept is implemented? If it is in >>>> ApplicationType Processor may be we can merge .NET and PHP application type >>>> processors and create an application type processor named something like >>>> SingleTenantApplicationTypeProcessor. WDYT? >>>> >>>> Thanks & Regards >>>> Danushka Fernando >>>> Software Engineer >>>> WSO2 inc. http://wso2.com/ >>>> Mobile : +94716332729 >>>> >>>> On Fri, Oct 31, 2014 at 10:25 AM, Gayan Dhanushka <[email protected]> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> According to the current implementation in .NET applications >>>>> versioning is done through the pom file generated with the .NET >>>>> application >>>>> archetype. This is not ideal since pom file is essentially used for >>>>> artifact versioning and the concept is different from application >>>>> versioning. The fact that we only use the maven archetype to build the >>>>> .NET >>>>> application also reiterate the need for proper versioning in .NET >>>>> applications. >>>>> >>>>> As a solution I have done a fix to create a copy of the source version >>>>> and rename it according to the format "<APP_NAME>-<APP_VERSION>-default" >>>>> when creating a new version of a .NET application. This coincide with the >>>>> way that we version PHP applications as well. >>>>> >>>>> Please share your thoughts on this. >>>>> >>>>> Regards >>>>> GayanD >>>>> >>>>> -- >>>>> Gayan Dhanuska >>>>> Software Engineer >>>>> http://wso2.com/ >>>>> Lean Enterprise Middleware >>>>> >>>>> Mobile >>>>> 071 666 2327 >>>>> >>>>> Office >>>>> Tel : 94 11 214 5345 >>>>> Fax : 94 11 214 5300 >>>>> >>>>> Twitter : https://twitter.com/gayanlggd >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >> >> >> -- >> Gayan Dhanuska >> Software Engineer >> http://wso2.com/ >> Lean Enterprise Middleware >> >> Mobile >> 071 666 2327 >> >> Office >> Tel : 94 11 214 5345 >> Fax : 94 11 214 5300 >> >> Twitter : https://twitter.com/gayanlggd >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > -- Gayan Dhanuska Software Engineer http://wso2.com/ Lean Enterprise Middleware Mobile 071 666 2327 Office Tel : 94 11 214 5345 Fax : 94 11 214 5300 Twitter : https://twitter.com/gayanlggd
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
