[prev in list] [next in list] [prev in thread] [next in thread]
List: wsas-java-dev
Subject: Re: [Dev] [Architecture] Maintaining IS-Archetypes
From: Inthirakumaaran Tharmakulasingham <inthirakumaaran () wso2 ! com>
Date: 2019-12-25 4:59:24
Message-ID: CAMC2_df2fne=r1xFKc5QDPp5XVQZEXiJSEB8Zt5yinVgRY84dw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi Darshana,
Currently we don't have an archetype for that.
Regards,
Kumaaran
On Tue, 24 Dec 2019, 20:17 Darshana Gunawardana, <darshana@wso2.com> wrote:
> Do we have an archetype for PostAuthenticationHandlers?
>
> On Wed, Oct 9, 2019 at 3:37 PM Inthirakumaaran Tharmakulasingham <
> inthirakumaaran@wso2.com> wrote:
>
> > Hi all,
> >
> > We had an offline discussion with @Darshana Gunawardana
> > <darshana@wso2.com> @Omindu Rathnaweera <omindu@wso2.com> @Jayanga
> > Kaushalya <jayangak@wso2.com> @Yasara Yasawardhana <yasaray@wso2.com> @Janak
> > Amarasena <janak@wso2.com> @Pulasthi Mahawithana <pulasthim@wso2.com>.
> > There we decided the following
> >
> > - Regarding Maintenance:
> > - Have a separate repo for IS-archetypes. We planned to go with
> > the name *archetypes-is* for the repo
> > - Go with four-digit release
> > - major -- product release
> > - minor -- addition of a new archetype
> > - patch -- improve
> > - 4th digit -- track archetype life
> > - For each product version, a branch will be created and
> > compatible archetypes for that versions will be maintained there
> > - Archetype Structure:
> > - The structure in the above mail is acceptable.
> > - Within comments, have the sample codes for the methods.
> > - Have the data holder pattern. But according to the situation, we
> > can drop this.
> > - The component name will be taken as input and appended as a
> > prefix.
> > - eg for user operation event listener --
> > {listener-name}UserOperationEventListener.java
> >
> > Please share your thoughts on this
> >
> > Thanks and Regards
> > kumaaran
> >
> > On Wed, Sep 11, 2019 at 9:20 PM Inthirakumaaran Tharmakulasingham <
> > inthirakumaaran@wso2.com> wrote:
> >
> > > Hi all,
> > >
> > > We have updated the dependency of user-event-listener-archetype[1] and
> > > now it can work on IS 5.8.0. While deciding on where to put these
> > > archetypes, let's try to finalize the format of archetypes by analyzing the
> > > user-event-listener-archetype.
> > >
> > > Following is the structure of this archetype.
> > >
> > > carbon-user-operation-eventListener-archetype
> > > > └── src
> > > > ├── main
> > > > │ └── resources
> > > > │ ├── META-INF
> > > > │ │ └── maven
> > > > │ │ └── archetype-metadata.xml
> > > > │ └── archetype-resources
> > > > │ ├── pom.xml
> > > > │ └── src
> > > > │ └── main
> > > > │ └── java
> > > > │ ├──
> > > > __listener-name-prefix__UserOperationEventListener.java
> > > > │ └── internal
> > > > │ └──
> > > > __listener-name-prefix__UserOperationEventListenerServiceComponent.java
> > > > └── test
> > > > └── resources
> > > > └── projects
> > > > └── basic
> > > > ├── archetype.properties
> > > > └── goal.txt
> > >
> > >
> > > We have to think of the components we can add to this archetypes. Eg we
> > > can add data-holder class which could help the user to customize these
> > > archetypes.
> > >
> > > Then we have to consider the naming as well, eg what group id should be
> > > given for which archetype or how the classes in the archetype should be
> > > named whether to add a suffix or have a fixed name
> > >
> > > Please share your thoughts on this
> > >
> > > [1]https://github.com/wso2-extensions/archetypes/pull/26
> > >
> > > On Wed, Aug 7, 2019 at 7:25 PM Kanapriya Kuleswararajan <
> > > kanapriya@wso2.com> wrote:
> > >
> > > > Hi Shankar,
> > > >
> > > > On Wed, Aug 7, 2019 at 4:56 PM Selvaratnam Uthaiyashankar <
> > > > shankar@wso2.com> wrote:
> > > >
> > > > >
> > > > >
> > > > > On Wed, Aug 7, 2019 at 2:23 PM Tharindu Bandara <tharindub@wso2.com>
> > > > > wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > Find the best approach to maintain the archetypes (in a single repo
> > > > > > > or inside the feature repo).
> > > > > >
> > > > > >
> > > > > I didn't understand what do we meant by feature repo here. Still it is
> > > > > going to be single repo right?
> > > > >
> > > >
> > > > The feature repo means, we thought to maintain the archetype in the
> > > > same repository where the feature is in. In that way, if we upgrade the
> > > > product or any feature component with the latest dependencies, we can
> > > > update the archetypes and can maintain the releases for archetypes as well
> > > > (we may need to maintain the old archetype version as there can be users
> > > > who still use the old product versions with lower dependency versions).
> > > >
> > > > >
> > > > > When we created the extensions, we make a conscious decision to have a
> > > > > separate repo for each extension. Each extension has its own release cycle.
> > > > > archetypes are also considered extensions. The version of the archetypes
> > > > > doesn't need to have a matching product version.
> > > > >
> > > > > Any difficulty we are facing by keeping them in separate repositories?
> > > > >
> > > >
> > > > I don't think any other difficulties in having each archetype in a
> > > > separate repo except the maintenance. Because, we have a couple of
> > > > archetypes in repo [1], but it's not in a stable state to use in latest
> > > > product versions as we (Developer) forget to update the archetype along
> > > > with the dependency upgrades. IMO, this may lead to a separate effort to
> > > > maintain each archetype if we have it in the separate repos?
> > > >
> > > > WDYT?
> > > >
> > > > [1] https://github.com/wso2-extensions/archetypes
> > > > <https://www.google.com/url?q=https://github.com/wso2-extensions/archetypes&sa=D&source=hangouts&ust=1564833739149000&usg=AFQjCNFopSwDYqHH3VV8GZORIXe7CmhGTQ>
> > > >
> > > > Thanks
> > > >
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > Shall we finalize on the approach to maintain the archetypes? This
> > > > > > would be helpful to proceed with the effort [1].
> > > > > >
> > > > > > [1] "[IS] Maven Archetype for Custom Event Handlers"
> > > > > >
> > > > > > Thanks,
> > > > > > Tharindu.
> > > > > >
> > > > > > On Mon, Aug 5, 2019 at 10:40 AM Kanapriya Kuleswararajan <
> > > > > > kanapriya@wso2.com> wrote:
> > > > > >
> > > > > > > In the repo [1] we have archetypes for IS extensions and seems they
> > > > > > > are outdated as it still uses the old dependency of carbon-identity. \
> > > > > > > This need to be improved/refactor in order to make this to a stable \
> > > > > > > with the latest product version.
> > > > > > >
> > > > > > > BTW, we couldn't see any specific reason to have all archetypes here
> > > > > > > under the repo [1]. Hence we thought to move all the IS-related \
> > > > > > > archetypes
> > > > > > > - To a separate repo? But here we have to decide, how we are
> > > > > > > going to maintain the releases (major or minor) if we have all the
> > > > > > > archetypes in the same repo? In this way, there can be chances that \
> > > > > > > some archetypes get released unnecessary (ie, without any changes).
> > > > > > > - Or else we can keep the archetypes inside the feature repo
> > > > > > > itself?
> > > > > > >
> > > > > > > Appreciate your valuable suggestions on the above?
> > > > > > >
> > > > > > > Further, In this effort, we (myself and @Inthi) are planning the
> > > > > > > following as the initial step:
> > > > > > >
> > > > > > > - Refactor the existing archetypes and Making that to work with
> > > > > > > IS 5.8.0 for now.
> > > > > > > - Find the best approach to maintain the archetypes (in a single
> > > > > > > repo or inside the feature repo).
> > > > > > > - Add more archetypes as part of this effort. We could see a
> > > > > > > couple of archetypes already developed, but that need to be reviewed \
> > > > > > > and we have to add those to the specific repo. @Inthirakumaaran
> > > > > > > Tharmakulasingham <inthirakumaaran@wso2.com> will share the
> > > > > > > details on this.
> > > > > > > - Generate guidance for creating an archetype.
> > > > > > >
> > > > > > > Please share your thoughts and suggestions about this effort, that
> > > > > > > will be very helpful to us to continue on this :)
> > > > > > >
> > > > > > > [1] https://github.com/wso2-extensions/archetypes
> > > > > > > <https://www.google.com/url?q=https://github.com/wso2-extensions/archety \
> > > > > > > pes&sa=D&source=hangouts&ust=1564833739149000&usg=AFQjCNFopSwDYqHH3VV8GZORIXe7CmhGTQ>
> > > > > > >
> > > > > > > Thanks
> > > > > > > Kanapriya Kuleswararajan
> > > > > > > Senior Software Engineer
> > > > > > > Mobile : - 0774894438
> > > > > > > Mail: - kanapriya@wso2.com
> > > > > > > LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/
> > > > > > > WSO2, Inc.
> > > > > > > lean. enterprise. middleware
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > *Tharindu Bandara*
> > > > > > Software Engineer | WSO2
> > > > > >
> > > > > > Email : tharindub@wso2.com
> > > > > > Mobile : +94 714221776
> > > > > > web : http://wso2.com
> > > > > > <https://www.google.com/url?q=http://wso2.com&sa=D&ust=1517653383990000&usg=AFQjCNFggB4bSJTKmdqKcBV0VY9xx1ABKg>
> > > > > >
> > > > > > https://wso2.com/signature
> > > > > > _______________________________________________
> > > > > > Architecture mailing list
> > > > > > Architecture@wso2.org
> > > > > > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > *S.Uthaiyashankar* | SVP Engineering | WSO2 Inc. <http://wso2.com/>
> > > > > (M)+94 774895474 | (E) shankar@wso2.com
> > > > > <https://wso2.com/signature>
> > > > >
> > > >
> > >
> > > --
> > > *Inthirakumaaran*
> > > Software Engineer | WSO2
> > >
> > > E-mail:Inthirakumaaran@wso2.com
> > > Mobile:+94775558050
> > > Web:https://wso2.com
> > >
> > > <http://wso2.com/signature>
> > >
> > >
> > >
> >
> > --
> > *Inthirakumaaran*
> > Software Engineer | WSO2
> >
> > E-mail:Inthirakumaaran@wso2.com
> > Mobile:+94775558050
> > Web:https://wso2.com
> >
> > <http://wso2.com/signature>
> >
> >
> >
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Technical Lead
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darshana@wso2.com <darshana@wso2.com>*
> *Mobile: +94718566859*Lean . Enterprise . Middleware
>
[Attachment #5 (text/html)]
<div dir="auto"><div dir="auto"></div>Hi Darshana, <div dir="auto"><br></div><div \
dir="auto">Currently we don't have an archetype for that. </div><div \
dir="auto"><br></div><div dir="auto">Regards, </div><div \
dir="auto">Kumaaran</div><div dir="auto"><br></div><div dir="auto"><br><div \
class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Tue, 24 Dec 2019, \
20:17 Darshana Gunawardana, <<a href="mailto:darshana@wso2.com" target="_blank" \
rel="noreferrer">darshana@wso2.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">Do we have an archetype for \
PostAuthenticationHandlers?</div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Wed, Oct 9, 2019 at 3:37 PM Inthirakumaaran Tharmakulasingham \
<<a href="mailto:inthirakumaaran@wso2.com" rel="noreferrer noreferrer" \
target="_blank">inthirakumaaran@wso2.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi all,<div><br></div><div>We had \
an offline discussion with <a class="gmail_plusreply" \
id="m_5978479603267702579m_-7074814894061721634gmail-m_813541204978185469gmail-m_5983411215239646388plusReplyChip-0" \
href="mailto:darshana@wso2.com" rel="noreferrer noreferrer" target="_blank">@Darshana \
Gunawardana</a> <a class="gmail_plusreply" \
id="m_5978479603267702579m_-7074814894061721634gmail-m_813541204978185469gmail-m_5983411215239646388plusReplyChip-1" \
href="mailto:omindu@wso2.com" rel="noreferrer noreferrer" target="_blank">@Omindu \
Rathnaweera</a> <a class="gmail_plusreply" \
id="m_5978479603267702579m_-7074814894061721634gmail-m_813541204978185469gmail-m_5983411215239646388plusReplyChip-2" \
href="mailto:jayangak@wso2.com" rel="noreferrer noreferrer" target="_blank">@Jayanga \
Kaushalya</a> <a class="gmail_plusreply" \
id="m_5978479603267702579m_-7074814894061721634gmail-m_813541204978185469gmail-m_5983411215239646388plusReplyChip-3" \
href="mailto:yasaray@wso2.com" rel="noreferrer noreferrer" target="_blank">@Yasara \
Yasawardhana</a> <a class="gmail_plusreply" \
id="m_5978479603267702579m_-7074814894061721634gmail-m_813541204978185469gmail-m_5983411215239646388plusReplyChip-4" \
href="mailto:janak@wso2.com" rel="noreferrer noreferrer" target="_blank">@Janak \
Amarasena</a> <a class="gmail_plusreply" \
id="m_5978479603267702579m_-7074814894061721634gmail-m_813541204978185469gmail-m_5983411215239646388plusReplyChip-5" \
href="mailto:pulasthim@wso2.com" rel="noreferrer noreferrer" \
target="_blank">@Pulasthi Mahawithana</a>. There we decided the following \
</div><div><ul><li>Regarding Maintenance:</li><ul><li>Have a separate repo for \
IS-archetypes. We planned to go with the name <b>archetypes-is</b> for the \
repo</li><li>Go with four-digit release</li><ul><li>major -- product \
release</li><li>minor -- addition of a new archetype</li><li>patch -- \
improve</li><li>4th digit -- track archetype life</li></ul><li>For each product \
version, a branch will be created and compatible archetypes for that versions will \
be maintained there</li></ul><li>Archetype Structure:</li><ul><li>The structure in \
the above mail is acceptable.</li><li>Within comments, have the sample codes for the \
methods.</li><li>Have the data holder pattern. But according to the situation, we can \
drop this.</li><li>The component name will be taken as input and appended as a \
prefix.</li><ul><li>eg for user operation event listener -- \
{listener-name}UserOperationEventListener.java</li></ul></ul></ul>Please share your \
thoughts on this</div><div><br></div><div>Thanks and \
Regards</div><div>kumaaran</div></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Wed, Sep 11, 2019 at 9:20 PM Inthirakumaaran Tharmakulasingham \
<<a href="mailto:inthirakumaaran@wso2.com" rel="noreferrer noreferrer" \
target="_blank">inthirakumaaran@wso2.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi \
all,</div><div><br></div><div>We have updated the dependency of \
user-event-listener-archetype[1] and now it can work on IS 5.8.0. While deciding on \
where to put these archetypes, let's try to finalize the format of archetypes by \
analyzing the user-event-listener-archetype.</div><div><br></div><div>Following is \
the structure of this archetype. </div><div><br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">carbon-user-operation-eventListener-archetype<br>└── \
src<br> ├── main<br> │ └── resources<br> │ \
├── META-INF<br> │ │ └── maven<br> │ \
│ └── archetype-metadata.xml<br> │ └── \
archetype-resources<br> │ ├── pom.xml<br> │ \
└── src<br> │ └── main<br> │ \
└── java<br> │ ├── \
__listener-name-prefix__UserOperationEventListener.java<br> │ \
└── internal<br> │ └── \
__listener-name-prefix__UserOperationEventListenerServiceComponent.java<br> \
└── test<br> └── resources<br> └── \
projects<br> └── basic<br> \
├── archetype.properties<br> └── \
goal.txt</blockquote><div><br></div><div>We have to think of the components we can \
add to this archetypes. Eg we can add data-holder class which could help the user to \
customize these archetypes. </div><div><br></div><div>Then we have to consider the \
naming as well, eg what group id should be given for which archetype or how the \
classes in the archetype should be named whether to add a suffix or have a fixed \
name</div><div><br></div><div>Please share your thoughts on \
this</div><div><br></div><div>[1]<a \
href="https://github.com/wso2-extensions/archetypes/pull/26" rel="noreferrer \
noreferrer" target="_blank">https://github.com/wso2-extensions/archetypes/pull/26</a></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 7, 2019 at 7:25 PM \
Kanapriya Kuleswararajan <<a href="mailto:kanapriya@wso2.com" rel="noreferrer \
noreferrer" target="_blank">kanapriya@wso2.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">Hi \
Shankar,</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, \
Aug 7, 2019 at 4:56 PM Selvaratnam Uthaiyashankar <<a \
href="mailto:shankar@wso2.com" rel="noreferrer noreferrer" \
target="_blank">shankar@wso2.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 7, 2019 at 2:23 PM \
Tharindu Bandara <<a href="mailto:tharindub@wso2.com" rel="noreferrer noreferrer" \
target="_blank">tharindub@wso2.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi all,<div><br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">Find the best approach to maintain the archetypes \
(in a single repo or inside the feature \
repo).</blockquote></div></blockquote><div><br></div><div>I didn't understand \
what do we meant by feature repo here. Still it is going to be single repo right? \
</div></div></div></blockquote><div><br></div><div>The feature repo means, we thought \
to maintain the archetype in the same repository where the feature is in. In that \
way, if we upgrade the product or any feature component with the latest dependencies, \
we can update the archetypes and can maintain the releases for archetypes as well (we \
may need to maintain the old archetype version as there can be users who still use \
the old product versions with lower dependency versions).<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div \
class="gmail_quote"><div><br></div><div>When we created the extensions, we make a \
conscious decision to have a separate repo for each extension. Each extension has its \
own release cycle. archetypes are also considered extensions. The version of the \
archetypes doesn't need to have a matching product version. \
</div><div><br></div><div>Any difficulty we are facing by keeping them in separate \
repositories? </div></div></div></blockquote><div><br></div><div>I don't think \
any other difficulties in having each archetype in a separate repo except the \
maintenance. Because, we have a couple of archetypes in repo [1], but it's not in \
a stable state to use in latest product versions as we (Developer) forget to update \
the archetype along with the dependency upgrades. IMO, this may lead to a separate \
effort to maintain each archetype if we have it in the separate \
repos?</div><div><br></div><div>WDYT?</div><div><br></div><div>[1] <a rel="nofollow \
noreferrer noopener noreferrer noreferrer" \
href="https://www.google.com/url?q=https://github.com/wso2-extensions/archetypes&s \
a=D&source=hangouts&ust=1564833739149000&usg=AFQjCNFopSwDYqHH3VV8GZORIXe7CmhGTQ" \
dir="ltr" style="font-size:13px;color:rgb(38,50,56);unicode-bidi:isolate;font-family:Roboto,sans-serif" \
target="_blank">https://github.com/wso2-extensions/archetypes</a></div><div><br></div><div>Thanks</div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div \
class="gmail_quote"><div><br></div><div> </div><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div> </div><div>Shall we finalize \
on the approach to maintain the archetypes? This would be helpful to proceed with the \
effort [1].</div><div><br></div><div>[1] "[IS] Maven Archetype for Custom Event \
Handlers"</div><div><br></div><div>Thanks,</div><div>Tharindu.</div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 5, 2019 at 10:40 AM \
Kanapriya Kuleswararajan <<a href="mailto:kanapriya@wso2.com" rel="noreferrer \
noreferrer" target="_blank">kanapriya@wso2.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr">In the repo [1] we have archetypes \
for IS extensions and seems they are outdated as it still uses the old dependency of \
carbon-identity. This need to be improved/refactor in order to make this to a stable \
with the latest product version. <div><br></div><div>BTW, we couldn't see any \
specific reason to have all archetypes here under the repo [1]. Hence we thought to \
move all the IS-related archetypes<br><ul><li style="margin-left:15px">To a separate \
repo? But here we have to decide, how we are going to maintain the releases (major or \
minor) if we have all the archetypes in the same repo? In this way, there can be \
chances that some archetypes get released unnecessary (ie, without any \
changes).</li><li style="margin-left:15px">Or else we can keep the archetypes inside \
the feature repo itself?<br><br> Appreciate your valuable suggestions on the \
above?</li></ul></div><div>Further, In this effort, we (myself and @Inthi) are \
planning the following as the initial step:</div><div><ul><li \
style="margin-left:15px">Refactor the existing archetypes and Making that to work \
with IS 5.8.0 for now.</li><li style="margin-left:15px">Find the best approach to \
maintain the archetypes (in a single repo or inside the feature repo).</li><li \
style="margin-left:15px">Add more archetypes as part of this effort. We could see a \
couple of archetypes already developed, but that need to be reviewed and we have to \
add those to the specific repo. <a class="gmail_plusreply" \
id="m_5978479603267702579m_-7074814894061721634gmail-m_813541204978185469gmail-m_61469 \
6501877855309gmail-m_-7212960420460992705gmail-m_-4326841308539322332gmail-m_-75241579 \
72481778484gmail-m_364520534675371546gmail-m_1450474196349504663gmail-m_3835732149839160358gmail-m_8973724407150983096m_3182164673113536485plusReplyChip-5" \
href="mailto:inthirakumaaran@wso2.com" rel="noreferrer noreferrer" \
target="_blank">@Inthirakumaaran Tharmakulasingham</a> will share the details on \
this. </li><li style="margin-left:15px">Generate guidance for creating an \
archetype.</li></ul></div><div>Please share your thoughts and suggestions about this \
effort, that will be very helpful to us to continue on this \
:)</div><div><br></div><div>[1] <a rel="nofollow noreferrer noopener noreferrer \
noreferrer" href="https://www.google.com/url?q=https://github.com/wso2-extensions/arch \
etypes&sa=D&source=hangouts&ust=1564833739149000&usg=AFQjCNFopSwDYqHH3VV8GZORIXe7CmhGTQ" \
dir="ltr" style="color:rgb(38,50,56);font-size:13px;unicode-bidi:isolate;font-family:Roboto,sans-serif" \
target="_blank">https://github.com/wso2-extensions/archetypes</a></div><div><br></div><div>Thanks</div><div><div \
dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div \
dir="ltr"><div><div><div>Kanapriya Kuleswararajan<br></div><span \
style="color:rgb(102,102,102)">Senior Software Engineer</span><span \
style="color:rgb(153,153,153)"></span></div>Mobile : - 0774894438<br></div>Mail: - <a \
href="mailto:kanapriya@wso2.com" rel="noreferrer noreferrer" \
target="_blank">kanapriya@wso2.com</a><br><font color="#666666"><span \
style="color:rgb(0,0,0)">LinkedIn : -</span> <span style="color:rgb(0,0,0)"><a \
href="https://www.linkedin.com/in/kanapriya-kules-94712685/" rel="noreferrer \
noreferrer" target="_blank">https://www.linkedin.com/in/kanapriya-kules-94712685/</a></span></font><br><span><font \
color="#888888"><span><font color="#888888"><span><div><div \
style="color:rgb(34,34,34)"><font color="#666666">WSO2, Inc. </font></div><div \
style="color:rgb(34,34,34)"><font color="#666666">lean. enterprise. \
middleware</font></div></div> \
</span></font></span></font></span><br></div></div></div></div></div></div></div></div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div \
dir="ltr"><span style="text-align:left" dir="ltr"><b>Tharindu Bandara</b><br>Software \
Engineer | WSO2<br><br>Email : <a href="mailto:tharindub@wso2.com" rel="noreferrer \
noreferrer" target="_blank">tharindub@wso2.com</a> <br>Mobile : +94 714221776<br>web \
: <a rel="nofollow noreferrer noreferrer noreferrer" \
href="https://www.google.com/url?q=http://wso2.com&sa=D&ust=1517653383990000&usg=AFQjCNFggB4bSJTKmdqKcBV0VY9xx1ABKg" \
dir="ltr" target="_blank">http://wso2.com</a><br><br></span><a \
href="https://wso2.com/signature" rel="noreferrer noreferrer" \
target="_blank">https://wso2.com/signature</a><img \
src="http://c.content.wso2.com/signatures/wso2-signature-general.png"><br></div></div>
_______________________________________________<br>
Architecture mailing list<br>
<a href="mailto:Architecture@wso2.org" rel="noreferrer noreferrer" \
target="_blank">Architecture@wso2.org</a><br> <a \
href="https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture" rel="noreferrer \
noreferrer noreferrer" \
target="_blank">https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture</a><br> \
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div \
dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div \
dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div \
dir="ltr"><div><div dir="ltr"><b>S<span>.</span>Uthaiyashankar</b> | SVP Engineering \
| <a href="http://wso2.com/" rel="noreferrer noreferrer" target="_blank">WSO2 \
Inc.</a><div>(M)+94 774895474 | (E) <a href="mailto:shankar@wso2.com" rel="noreferrer \
noreferrer" target="_blank">shankar@wso2.com</a></div><div><a \
href="https://wso2.com/signature" rel="noreferrer noreferrer" target="_blank"><img \
src="http://c.content.wso2.com/signatures/wso2-mail-signature-general.png"></a><br></d \
iv></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
</blockquote></div>
</div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div \
dir="ltr"><div><div><b>Inthirakumaaran</b></div><div>Software Engineer | \
WSO2</div><div><br></div><div>E-mail:<a href="mailto:Inthirakumaaran@wso2.com" \
rel="noreferrer noreferrer" \
target="_blank">Inthirakumaaran@wso2.com</a></div><div>Mobile:+94775558050</div><div>Web:<a \
href="https://wso2.com/" rel="noreferrer noreferrer" \
target="_blank">https://wso2.com</a></div></div><div><br></div><div><a \
href="http://wso2.com/signature" rel="noreferrer noreferrer" target="_blank"><img \
src="http://c.content.wso2.com/signatures/wso2-signature-general.png"></a><br></div><div><br></div><br></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div \
dir="ltr"><div><div><b>Inthirakumaaran</b></div><div>Software Engineer | \
WSO2</div><div><br></div><div>E-mail:<a href="mailto:Inthirakumaaran@wso2.com" \
rel="noreferrer noreferrer" \
target="_blank">Inthirakumaaran@wso2.com</a></div><div>Mobile:+94775558050</div><div>Web:<a \
href="https://wso2.com/" rel="noreferrer noreferrer" \
target="_blank">https://wso2.com</a></div></div><div><br></div><div><a \
href="http://wso2.com/signature" rel="noreferrer noreferrer" target="_blank"><img \
src="http://c.content.wso2.com/signatures/wso2-signature-general.png"></a><br></div><div><br></div><br></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div \
dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><font \
face="georgia, serif">Regards,</font><div><font face="georgia, \
serif"><br></font><div><font face="georgia, serif"><font><b><div><b><font \
size="2">Darshana Gunawardana</font></b><br></div></b></font><span \
style="color:rgb(51,51,51)"><font size="2">Technical \
Lead</font></span></font></div><div><font face="georgia, serif"><font size="1"><span \
style="color:rgb(51,51,51)">WSO2 Inc.; <a href="http://wso2.com" rel="noreferrer \
noreferrer" target="_blank">http://wso2.com</a></span><i \
style="color:rgb(51,51,51)"><br>E-mail: <a href="mailto:darshana@wso2.com" \
rel="noreferrer noreferrer" target="_blank">darshana@wso2.com</a><br></i></font><i \
style="color:rgb(51,51,51)"><font size="1">Mobile: +94718566859</font><br></i><span \
style="color:rgb(51,51,51)"><font size="1">Lean . Enterprise . \
Middleware</font></span></font><br></div></div></div></div></div></div></div></div></div></div>
</blockquote></div></div></div>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic