artifacts at the top level seems too abstract. We will have a p2 repo as
well, and people may wonder why those things cannot go into artifacts.

Azeez

On Tue, Feb 16, 2010 at 10:45 AM, Ruwan Linton <[email protected]> wrote:

> Isuru Suriarachchi wrote:
> >
> >
> > On Tue, Feb 16, 2010 at 9:22 AM, Ruwan Linton <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> >     Sumedha Rubasinghe wrote:
> >     >
> >     > On Mon, Feb 15, 2010 at 4:09 PM, Afkham Azeez <[email protected]
> >     <mailto:[email protected]>
> >     > <mailto:[email protected] <mailto:[email protected]>>> wrote:
> >     >
> >     >     It should be
> >     >
> >     >     repository
> >     >         |
> >     >         |- axis2
> >     >               |- server
> >     >                      |-artifacts
> >     >                            |- modules
> >     >                            |- services
> >     >
> >     >
> >     > +1 .. This looks meaningful.
> >     >
> >     > Would it sound odd if we rename 'services' into 'axis2services'?
> >     > Rationale is we will be having other deployer related folders (eg:
> >     > dataservices,bpel,jsservice) here & 'services' along sound too
> >     > abstract. (I know this was how we had before.)
> >     Also, do we have to have axis2 on the top level? because we will be
> >     having different deployers (for example BPEL) which shouldn't
> >     necessarily show off axis2, same with synapse.
> >
> >     What are the things that can some under server folder except
> artifacts
> >     ?? If there is nothing, why don't we fall back to;
> >
> >
> > +1. That's what I also mentioned in my previous mail. I think we can
> > omit 'artifacts' there and use it instead of 'axis2', so that it will
> > look like this..
> >
> > repository
> >        |
> >        |- artifacts
> >                |- server
> >                        |- modules
> >                        |- services
> >                |- client
> +1
>
> If there is no objections lets do this for the next build (within next 2
> days).
>
> Thanks,
> Ruwan
> >
> > Thanks,
> > ~Isuru
> >
> >
> >     repository/server
> >     repository/client
> >
> >     So inside the repository/server you will have directories like;
> >
> >     axis2Services
> >     axis2Modules
> >     dataServices
> >     jarServices
> >     bpel
> >     mediators
> >
> >     A carbon server is more than an axis2 server, we should be able to
> >     share
> >     a single repository within carbon.
> >
> >     WDYT?
> >
> >     Thanks,
> >     Ruwan
> >
> >     >
> >     > /sumedha
> >     >
> >     >
> >     >
> >     >     repository/axis2/server/repository looks weird so we decided to
> >     >     call it, repository/axis2/server/artifacts
> >     >
> >     >     Azeez
> >     >
> >     >
> >     >     On Mon, Feb 15, 2010 at 3:27 PM, Isuru Suriarachchi
> >     >     <[email protected] <mailto:[email protected]>
> >     <mailto:[email protected] <mailto:[email protected]>>> wrote:
> >     >
> >     >
> >     >
> >     >         On Mon, Feb 15, 2010 at 3:16 PM, Ruwan Linton
> >     <[email protected] <mailto:[email protected]>
> >     >         <mailto:[email protected] <mailto:[email protected]>>> wrote:
> >     >
> >     >             Axis2 repo path is
> >     >
> >     >             repository/axis2/service/artifacts
> >     >
> >     >
> >     >         I think this model was proposed during our discussion on
> >     >         refactoring Carbon folder structure (done by lahiru).
> >     "axis2"
> >     >         folder is to isolate axis2 related stuff as we have
> >     other OSGi
> >     >         stuff also in repository. "service" folder is to isolate
> the
> >     >         server side repository (however I think this should be
> >     >         'server' rather than 'service'). I think we have
> >     axis2/service
> >     >         and axis2/client. I'm not sure about what's the use of
> >     having
> >     >         the "artifacts" folder.
> >     >
> >     >         Thanks,
> >     >         ~Isuru
> >     >
> >     >
> >     >
> >     >             Why do we have service there??? :-(
> >     >
> >     >             Thanks,
> >     >             Ruwan
> >     >
> >     >             --
> >     >             Ruwan Linton
> >     >             Technical Lead & Product Manager; WSO2 ESB;
> >     >             http://wso2.org/esb
> >     >             WSO2 <http://wso2.org/esb%0AWSO2> Inc.;
> http://wso2.org
> >     >             email: [email protected] <mailto:[email protected]>
> >     <mailto:[email protected] <mailto:[email protected]>>; cell: +94
> >     >             77 341 3097
> >     >             blog: http://blog.ruwan.org
> >     >
> >     >             Lean . Enterprise . Middleware
> >     >
> >     >
> >     >             _______________________________________________
> >     >             Carbon-dev mailing list
> >     >             [email protected] <mailto:[email protected]>
> >     <mailto:[email protected] <mailto:[email protected]>>
> >     >
> >     https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >     >
> >     >
> >     >
> >     >         _______________________________________________
> >     >         Carbon-dev mailing list
> >     >         [email protected] <mailto:[email protected]>
> >     <mailto:[email protected] <mailto:[email protected]>>
> >     >         https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >     >
> >     >
> >     >
> >     >
> >     >     --
> >     >     --
> >     >     Afkham Azeez
> >     >     [email protected] <mailto:[email protected]>
> >     <mailto:[email protected] <mailto:[email protected]>>
> >     >
> >     >     WSO2 Inc. http://wso2.com
> >     >     Blog: http://afkham.org
> >     >
> >     >     _______________________________________________
> >     >     Carbon-dev mailing list
> >     >     [email protected] <mailto:[email protected]>
> >     <mailto:[email protected] <mailto:[email protected]>>
> >     >     https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >     >
> >     >
> >     >
> >
> ------------------------------------------------------------------------
> >     >
> >     > _______________________________________________
> >     > Carbon-dev mailing list
> >     > [email protected] <mailto:[email protected]>
> >     > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >     >
> >
> >
> >     --
> >     Ruwan Linton
> >     Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> >     WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org
> >     email: [email protected] <mailto:[email protected]>; cell: +94 77 341 3097
> >     blog: http://blog.ruwan.org
> >
> >     Lean . Enterprise . Middleware
> >
> >
> >     _______________________________________________
> >     Carbon-dev mailing list
> >     [email protected] <mailto:[email protected]>
> >     https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Carbon-dev mailing list
> > [email protected]
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: [email protected]; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
>
> Lean . Enterprise . Middleware
>
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
--
Afkham Azeez
[email protected]
WSO2 Inc. http://wso2.com
Blog: http://afkham.org
_______________________________________________
Carbon-dev mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to