On Fri, Feb 6, 2015 at 1:00 PM, Viraj Rajaguru <vi...@wso2.com> wrote:
> Hi, > > Since "Eclipse Che" currently does not support for creating JAX-RS and > JAX-WS projects and we are going to implement project types for JAX-RS and > JAX-WS for Eclipse Che, I think its better to categorize them under Java > --> Maven category not under the WSO2 category.(Following the convention > for existing webapps creation in Eclipse Che) > +1, so that non wso2 people also can use this feature to create apps for tomcat. > > Thanks, > Viraj. > > On Thu, Feb 5, 2015 at 9:35 PM, Susinda Perera <susi...@wso2.com> wrote: > >> Hi All >> >> We are in the process of $subject. One of the decision point we faced is >> how to implement the 3 level project hierarchy as i have discussed in the >> below mail. (added below[1] is the mail discussion i had with codenvy >> team). According to them there is no such option in 3.5.0 release but will >> be there in 3.7.0. However the plugin we already being developing is >> handled this issue by having a wizard page. But according to the training >> we had it seems that better way to do this is by having project generator >> for each project. Therefore i think till we got that thing implemented by >> codenvy we could go in a project structure as one of the options(1, 2) >> below. >> >> [opt1] >> WSO2 ESB >> -- ESB config project >> WSO2 AppServer >> -- webapp project >> -- JAX-WS project >> -- JAX-RS project >> >> [opt2] >> WSO2 >> -- ESB project >> -- AppServer JAX-WS projet >> -- AppServer JAX-RS projet >> -- AppServer webapp projet >> >> I prefer option one since, when we get 3 level support implemented we can >> easily move 'WSO2' >> as the top level. Please give your suggestions. >> >> Thanks >> >> >> >> [1] >> ---------- Forwarded message ---------- >> From: Vitalii Parfonov <vparfo...@codenvy.com> >> Date: Thu, Feb 5, 2015 at 7:30 PM >> Subject: Re: 3 level hierarchy of projects and pom creation >> To: Tyler Jewell <tjew...@codenvy.com> >> Cc: wso2-engagement <wso2-engagem...@codenvy.com>, Gennady Azarenkov < >> gazaren...@codenvy.com>, Susinda Perera <susi...@wso2.com>, Evgen >> Vidolob <evido...@codenvy.com>, Andrii Plotnikov <aplotni...@codenvy.com> >> >> >> >> >> Vitaly Parfonov -- codenvy >> >> On Thu, Feb 5, 2015 at 2:57 PM, Tyler Jewell <tjew...@codenvy.com> wrote: >> >>> Adding Gennady. He should have some suggestions. In 3.7, we are >>> introducing an improved project type abstraction. It supports sub project >>> types, project modules, and authorship in a single class. >>> >>> We will use this to create the deployment abstractions as a type of >>> project. It should also simplify what you need for this structure. >>> >>> >>> _____________________________ >>> From: Susinda Perera <susi...@wso2.com> >>> Sent: Wednesday, February 4, 2015 9:58 PM >>> Subject: 3 level hierarchy of projects and pom creation >>> To: wso2-engagement <wso2-engagem...@codenvy.com>, Andrii Plotnikov < >>> aplotni...@codenvy.com>, Evgen Vidolob <evido...@codenvy.com> >>> >>> >>> Hi Andrii/Evgin >>> >>> This is to get some advices and best-practises for following 2 items. >>> >>> 1.We are thinking of developing a project based on following structure >>> >>> WSO2 >>> -- ESB Project >>> -- AppServer Project >>> -- JAX-WS Project >>> -- Webapp Project >>> >>> Is this structure is supported from codenvy.? Do you recomend to go in >>> this approach >>> Alternative approach that we are thinking of is giving a single wizard >>> for AppServer Project and there we give another wizard page to select the >>> project type and depending on project type execute a project generator. >>> But i feel like having a separate project generator for each project >>> type would be good, however to implement that way might need to have above >>> 3 level support. >>> >> >> Yes, no reason do something until we ship 3.7.0 >> >> >>> >>> 2. We want to add repositories and pluginRepositories for the pom, >>> however i could not find a method in com .codenvy.ide.maven.tools.Model >>> to do this. As an alternative we can write to the pom file directly >>> (or can we use model .setPomFile() to do the same). >>> >> >> We will add this method to our model. I have created issue on it. >> >> >>> >>> Appreciate your inputs and thoughts. >>> >>> Thanks >>> >>> >>> -- >>> *Susinda Perera* >>> Software Engineer >>> Mobile: (+94)716049075 >>> >>> WSO2 Inc. http://wso2.com/ >>> Tel : 94 11 214 5345 Fax :94 11 <11%C2%A0%202145300>2145300 >>> <11%C2%A0%202145300> >>> >>> >>> >>> >> >> >> >> -- >> *Susinda Perera* >> Software Engineer >> Mobile:(+94)716049075 >> >> WSO2 Inc. http://wso2.com/ >> Tel : 94 11 214 5345 Fax :94 11 2145300 >> >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Viraj Rajaguru > Senior Software Engineer > WSO2 Inc. : http://wso2.com > > Mobile: +94 77 3683068 > > > > -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
