Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
+1. This looks much more structured. Also addresses the concern mentioned by Pradeepan above. The term graphite will no longer be used with this structure? /sumedha On Mon, Feb 13, 2012 at 5:41 PM, Sameera Jayasoma same...@wso2.com wrote: Hi Samisa, As per the offline discussion we had with (you, Azeez, Isuru, Pradeep and others), we identified that the existing structure has its own complexities as illustrated by the Samisa. The proposal was to come up with a toplevel project called carbon and maintain the structure illustrated in the attached image. This change will be a simple SVN move. We will do this once the tomcat OSGification is applied to the carbon trunk. Thanks, Sameera. On Mon, Feb 13, 2012 at 3:59 PM, Samisa Abeysinghe sam...@wso2.comwrote: Graphite brings in complexities in comprehension - is it a new project, part of Carbon, extend Carbon etc etc Imagine telling a story along the lines of Carbon has this concpet called P2 and you install Graphite components onto Carbon products using feature manager component On Mon, Feb 13, 2012 at 11:00 AM, Supun Malinga sup...@wso2.com wrote: On Mon, Feb 13, 2012 at 9:28 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Azeez, Let me explain the rationale behind this orbit level change. If you look at the orbit project keeping Carbon aside, it can be considered as a third party project, completely independent from Carbon and Graphite projects. The purpose of the orbit project is to produce OSGi bundles out of third party legacy jars. So the orbit project is not related to Carbon or Graphite by any means. And also changes to these orbit projects is rare, unless we created them in a sloppy manner. Ideally we can upload orbit projects and then developers do not need to build them at all. But, over the time we've missed used the orbit concept. e.g. we have orbit projects corresponding the dependencies projects. These orbits change frequently, since the corresponding dependencies change. By considering all these aspects, we came up with the following structure *orbit* (Consists of all the orbit projects which are used by both Carbon and Graphite projects.) *carbon* *|--* *dependencies* *|-- orbit* (These orbit projects produce bundles out of the Carbon level dependencies.) *graphite* *|-- dependencies* *|-- orbit* (These orbit projects produce bundles out of the Graphite level dependencies.) Please let us know your views on this. +1 thanks, Thanks, Sameera. On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez az...@wso2.com wrote: In this model,. what happens to dependencies orbits that are common to both Carbon Graphite? On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, We have plans commit Pradeep's change in a hackathon mode. His changes is again platform wide change. We can get help from the AS and Jaggery team as well. Lets plan this during the todays meeting. Thanks, Sameera. On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.com wrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *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 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* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
No graphite. There never was :-) -- Afkham Azeez Sent from my phone On Feb 18, 2012 7:11 PM, Sumedha Rubasinghe sume...@wso2.com wrote: +1. This looks much more structured. Also addresses the concern mentioned by Pradeepan above. The term graphite will no longer be used with this structure? /sumedha On Mon, Feb 13, 2012 at 5:41 PM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, As per the offline discussion we had with (you, Azeez, Isuru, Pradeep and others), we identified that the existing structure has its own complexities as illustrated by the Samisa. The proposal was to come up with a toplevel project called carbon and maintain the structure illustrated in the attached image. This change will be a simple SVN move. We will do this once the tomcat OSGification is applied to the carbon trunk. Thanks, Sameera. On Mon, Feb 13, 2012 at 3:59 PM, Samisa Abeysinghe sam...@wso2.comwrote: Graphite brings in complexities in comprehension - is it a new project, part of Carbon, extend Carbon etc etc Imagine telling a story along the lines of Carbon has this concpet called P2 and you install Graphite components onto Carbon products using feature manager component On Mon, Feb 13, 2012 at 11:00 AM, Supun Malinga sup...@wso2.com wrote: On Mon, Feb 13, 2012 at 9:28 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Azeez, Let me explain the rationale behind this orbit level change. If you look at the orbit project keeping Carbon aside, it can be considered as a third party project, completely independent from Carbon and Graphite projects. The purpose of the orbit project is to produce OSGi bundles out of third party legacy jars. So the orbit project is not related to Carbon or Graphite by any means. And also changes to these orbit projects is rare, unless we created them in a sloppy manner. Ideally we can upload orbit projects and then developers do not need to build them at all. But, over the time we've missed used the orbit concept. e.g. we have orbit projects corresponding the dependencies projects. These orbits change frequently, since the corresponding dependencies change. By considering all these aspects, we came up with the following structure *orbit* (Consists of all the orbit projects which are used by both Carbon and Graphite projects.) *carbon* *|--* *dependencies* *|-- orbit* (These orbit projects produce bundles out of the Carbon level dependencies.) *graphite* *|-- dependencies* *|-- orbit* (These orbit projects produce bundles out of the Graphite level dependencies.) Please let us know your views on this. +1 thanks, Thanks, Sameera. On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez az...@wso2.com wrote: In this model,. what happens to dependencies orbits that are common to both Carbon Graphite? On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, We have plans commit Pradeep's change in a hackathon mode. His changes is again platform wide change. We can get help from the AS and Jaggery team as well. Lets plan this during the todays meeting. Thanks, Sameera. On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.com wrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.com wrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *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 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* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog:
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
Does the term platform correct here? we have Platform-mc to manage carbon kernel (as given here) and in effect rest of the teams mange other parts which has mentioned as platform here. IMHO we need to use terms in same meaning every where. thanks, Amila. On Mon, Feb 13, 2012 at 5:41 PM, Sameera Jayasoma same...@wso2.com wrote: Hi Samisa, As per the offline discussion we had with (you, Azeez, Isuru, Pradeep and others), we identified that the existing structure has its own complexities as illustrated by the Samisa. The proposal was to come up with a toplevel project called carbon and maintain the structure illustrated in the attached image. This change will be a simple SVN move. We will do this once the tomcat OSGification is applied to the carbon trunk. Thanks, Sameera. On Mon, Feb 13, 2012 at 3:59 PM, Samisa Abeysinghe sam...@wso2.comwrote: Graphite brings in complexities in comprehension - is it a new project, part of Carbon, extend Carbon etc etc Imagine telling a story along the lines of Carbon has this concpet called P2 and you install Graphite components onto Carbon products using feature manager component On Mon, Feb 13, 2012 at 11:00 AM, Supun Malinga sup...@wso2.com wrote: On Mon, Feb 13, 2012 at 9:28 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Azeez, Let me explain the rationale behind this orbit level change. If you look at the orbit project keeping Carbon aside, it can be considered as a third party project, completely independent from Carbon and Graphite projects. The purpose of the orbit project is to produce OSGi bundles out of third party legacy jars. So the orbit project is not related to Carbon or Graphite by any means. And also changes to these orbit projects is rare, unless we created them in a sloppy manner. Ideally we can upload orbit projects and then developers do not need to build them at all. But, over the time we've missed used the orbit concept. e.g. we have orbit projects corresponding the dependencies projects. These orbits change frequently, since the corresponding dependencies change. By considering all these aspects, we came up with the following structure *orbit* (Consists of all the orbit projects which are used by both Carbon and Graphite projects.) *carbon* *|--* *dependencies* *|-- orbit* (These orbit projects produce bundles out of the Carbon level dependencies.) *graphite* *|-- dependencies* *|-- orbit* (These orbit projects produce bundles out of the Graphite level dependencies.) Please let us know your views on this. +1 thanks, Thanks, Sameera. On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez az...@wso2.com wrote: In this model,. what happens to dependencies orbits that are common to both Carbon Graphite? On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, We have plans commit Pradeep's change in a hackathon mode. His changes is again platform wide change. We can get help from the AS and Jaggery team as well. Lets plan this during the todays meeting. Thanks, Sameera. On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.com wrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *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 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* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
Hi Sumedha, Pradeeban, Well it looks much more structured, but it does not address the concern from Pradeeban. With this structure, someone cannot in anyway do a single checkout of the whole thing. But in anyway, that should never be a requirement to anyone in the future. The reason to need to checkout the whole of carbon is totally because carbon, components and everything related was always treated as a single chunk and this is an approach to cleanly separate those concerns. Someone working on component Y will use or extend the kernel, and should be able to live in total independence. But there can be situations that a bug in the kernel limits you from doing something. That would be similar to any other bug in Axis2. From a developer's perspective, while its important that we spend time and get things done right, I'd like to to see us agreeing on something soon, since every move means a new checkout and a new build, which seems to be taking an age to get through with nasty issues like the missing Jarvana repository. Thanks, Senaka. On Sat, Feb 18, 2012 at 9:18 PM, Afkham Azeez az...@wso2.com wrote: No graphite. There never was :-) -- Afkham Azeez Sent from my phone On Feb 18, 2012 7:11 PM, Sumedha Rubasinghe sume...@wso2.com wrote: +1. This looks much more structured. Also addresses the concern mentioned by Pradeepan above. The term graphite will no longer be used with this structure? /sumedha On Mon, Feb 13, 2012 at 5:41 PM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, As per the offline discussion we had with (you, Azeez, Isuru, Pradeep and others), we identified that the existing structure has its own complexities as illustrated by the Samisa. The proposal was to come up with a toplevel project called carbon and maintain the structure illustrated in the attached image. This change will be a simple SVN move. We will do this once the tomcat OSGification is applied to the carbon trunk. Thanks, Sameera. On Mon, Feb 13, 2012 at 3:59 PM, Samisa Abeysinghe sam...@wso2.comwrote: Graphite brings in complexities in comprehension - is it a new project, part of Carbon, extend Carbon etc etc Imagine telling a story along the lines of Carbon has this concpet called P2 and you install Graphite components onto Carbon products using feature manager component On Mon, Feb 13, 2012 at 11:00 AM, Supun Malinga sup...@wso2.comwrote: On Mon, Feb 13, 2012 at 9:28 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Azeez, Let me explain the rationale behind this orbit level change. If you look at the orbit project keeping Carbon aside, it can be considered as a third party project, completely independent from Carbon and Graphite projects. The purpose of the orbit project is to produce OSGi bundles out of third party legacy jars. So the orbit project is not related to Carbon or Graphite by any means. And also changes to these orbit projects is rare, unless we created them in a sloppy manner. Ideally we can upload orbit projects and then developers do not need to build them at all. But, over the time we've missed used the orbit concept. e.g. we have orbit projects corresponding the dependencies projects. These orbits change frequently, since the corresponding dependencies change. By considering all these aspects, we came up with the following structure *orbit* (Consists of all the orbit projects which are used by both Carbon and Graphite projects.) *carbon* *|--* *dependencies* *|-- orbit* (These orbit projects produce bundles out of the Carbon level dependencies.) *graphite* *|-- dependencies* *|-- orbit* (These orbit projects produce bundles out of the Graphite level dependencies.) Please let us know your views on this. +1 thanks, Thanks, Sameera. On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez az...@wso2.com wrote: In this model,. what happens to dependencies orbits that are common to both Carbon Graphite? On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, We have plans commit Pradeep's change in a hackathon mode. His changes is again platform wide change. We can get help from the AS and Jaggery team as well. Lets plan this during the todays meeting. Thanks, Sameera. On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.com wrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.com wrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.com wrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
On Sat, Feb 18, 2012 at 10:19 PM, Senaka Fernando sen...@wso2.com wrote: Hi Sumedha, Pradeeban, Well it looks much more structured, but it does not address the concern from Pradeeban. With this structure, someone cannot in anyway do a single checkout of the whole thing. But in anyway, that should never be a requirement to anyone in the future. The reason to need to checkout the whole of carbon is totally because carbon, components and everything related was always treated as a single chunk and this is an approach to cleanly separate those concerns. Someone working on component Y will use or extend the kernel, and should be able to live in total independence. But there can be situations that a bug in the kernel limits you from doing something. That would be similar to any other bug in Axis2. +1. I am also thinking in same direction. I feel this re grouping is going backward. The idea of this re structuring is to *think* orbit, core and others (currently named as graphite) are independent things. So all of them should be in top level. As Senaka pointed out in future people should be able to build graphite without checking out core. i.e. it should point to a stable core version. IMHO this checking out every thing is the old concept. The other point is when looking at the re groping I got the feeling that we have just bring the branching point to second level which was there in the carbon level. thanks, Amila. From a developer's perspective, while its important that we spend time and get things done right, I'd like to to see us agreeing on something soon, since every move means a new checkout and a new build, which seems to be taking an age to get through with nasty issues like the missing Jarvana repository. Thanks, Senaka. On Sat, Feb 18, 2012 at 9:18 PM, Afkham Azeez az...@wso2.com wrote: No graphite. There never was :-) -- Afkham Azeez Sent from my phone On Feb 18, 2012 7:11 PM, Sumedha Rubasinghe sume...@wso2.com wrote: +1. This looks much more structured. Also addresses the concern mentioned by Pradeepan above. The term graphite will no longer be used with this structure? /sumedha On Mon, Feb 13, 2012 at 5:41 PM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, As per the offline discussion we had with (you, Azeez, Isuru, Pradeep and others), we identified that the existing structure has its own complexities as illustrated by the Samisa. The proposal was to come up with a toplevel project called carbon and maintain the structure illustrated in the attached image. This change will be a simple SVN move. We will do this once the tomcat OSGification is applied to the carbon trunk. Thanks, Sameera. On Mon, Feb 13, 2012 at 3:59 PM, Samisa Abeysinghe sam...@wso2.comwrote: Graphite brings in complexities in comprehension - is it a new project, part of Carbon, extend Carbon etc etc Imagine telling a story along the lines of Carbon has this concpet called P2 and you install Graphite components onto Carbon products using feature manager component On Mon, Feb 13, 2012 at 11:00 AM, Supun Malinga sup...@wso2.comwrote: On Mon, Feb 13, 2012 at 9:28 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Azeez, Let me explain the rationale behind this orbit level change. If you look at the orbit project keeping Carbon aside, it can be considered as a third party project, completely independent from Carbon and Graphite projects. The purpose of the orbit project is to produce OSGi bundles out of third party legacy jars. So the orbit project is not related to Carbon or Graphite by any means. And also changes to these orbit projects is rare, unless we created them in a sloppy manner. Ideally we can upload orbit projects and then developers do not need to build them at all. But, over the time we've missed used the orbit concept. e.g. we have orbit projects corresponding the dependencies projects. These orbits change frequently, since the corresponding dependencies change. By considering all these aspects, we came up with the following structure *orbit* (Consists of all the orbit projects which are used by both Carbon and Graphite projects.) *carbon* *|--* *dependencies* *|-- orbit* (These orbit projects produce bundles out of the Carbon level dependencies.) *graphite* *|-- dependencies* *|-- orbit* (These orbit projects produce bundles out of the Graphite level dependencies.) Please let us know your views on this. +1 thanks, Thanks, Sameera. On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez az...@wso2.comwrote: In this model,. what happens to dependencies orbits that are common to both Carbon Graphite? On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma same...@wso2.com wrote: Hi Samisa, We have plans commit Pradeep's change in a hackathon mode. His changes is again platform wide change. We can get help from the AS and Jaggery team as well. Lets plan this during the todays
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
HI On Sat, Feb 18, 2012 at 10:19 PM, Senaka Fernando sen...@wso2.com wrote: Hi Sumedha, Pradeeban, Well it looks much more structured, but it does not address the concern from Pradeeban. With this structure, someone cannot in anyway do a single checkout of the whole thing. But in anyway, that should never be a requirement to anyone in the future. The reason to need to checkout the whole of carbon is totally because carbon, components and everything related was always treated as a single chunk and this is an approach to cleanly separate those concerns. Someone working on component Y will use or extend the kernel, and should be able to live in total independence. But there can be situations that a bug in the kernel limits you from doing something. That would be similar to any other bug in Axis2. +1, this is correct and IMO, this is what Sameera had suggested in his mail. We have three top level projects; kernal, orbit and platform, each has a separate parent pom, and each has a separate trunk and a branch, so someone who is working on a platform component can checkout the platform stuff, and work on it. he doesn't need to checkout the kernel. Same goes to the kernal. IMO, this structure is clean so +1, I also feel grouping all three of these projects as Carbon also correct coz all three of these projects are maintained as segments of WSO2 Carbon. From a developer's perspective, while its important that we spend time and get things done right, I'd like to to see us agreeing on something soon, since every move means a new checkout and a new build, which seems to be taking an age to get through with nasty issues like the missing Jarvana repository. +1, true lets finalize on one thing and do a restructure, else it causes alot of valuable time. It took at least two days to get the stuff build correctly after the restructure happened last weekend. Regards, /Nuwan Thanks, Senaka. On Sat, Feb 18, 2012 at 9:18 PM, Afkham Azeez az...@wso2.com wrote: No graphite. There never was :-) -- Afkham Azeez Sent from my phone On Feb 18, 2012 7:11 PM, Sumedha Rubasinghe sume...@wso2.com wrote: +1. This looks much more structured. Also addresses the concern mentioned by Pradeepan above. The term graphite will no longer be used with this structure? /sumedha On Mon, Feb 13, 2012 at 5:41 PM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, As per the offline discussion we had with (you, Azeez, Isuru, Pradeep and others), we identified that the existing structure has its own complexities as illustrated by the Samisa. The proposal was to come up with a toplevel project called carbon and maintain the structure illustrated in the attached image. This change will be a simple SVN move. We will do this once the tomcat OSGification is applied to the carbon trunk. Thanks, Sameera. On Mon, Feb 13, 2012 at 3:59 PM, Samisa Abeysinghe sam...@wso2.comwrote: Graphite brings in complexities in comprehension - is it a new project, part of Carbon, extend Carbon etc etc Imagine telling a story along the lines of Carbon has this concpet called P2 and you install Graphite components onto Carbon products using feature manager component On Mon, Feb 13, 2012 at 11:00 AM, Supun Malinga sup...@wso2.comwrote: On Mon, Feb 13, 2012 at 9:28 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Azeez, Let me explain the rationale behind this orbit level change. If you look at the orbit project keeping Carbon aside, it can be considered as a third party project, completely independent from Carbon and Graphite projects. The purpose of the orbit project is to produce OSGi bundles out of third party legacy jars. So the orbit project is not related to Carbon or Graphite by any means. And also changes to these orbit projects is rare, unless we created them in a sloppy manner. Ideally we can upload orbit projects and then developers do not need to build them at all. But, over the time we've missed used the orbit concept. e.g. we have orbit projects corresponding the dependencies projects. These orbits change frequently, since the corresponding dependencies change. By considering all these aspects, we came up with the following structure *orbit* (Consists of all the orbit projects which are used by both Carbon and Graphite projects.) *carbon* *|--* *dependencies* *|-- orbit* (These orbit projects produce bundles out of the Carbon level dependencies.) *graphite* *|-- dependencies* *|-- orbit* (These orbit projects produce bundles out of the Graphite level dependencies.) Please let us know your views on this. +1 thanks, Thanks, Sameera. On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez az...@wso2.comwrote: In this model,. what happens to dependencies orbits that are common to both Carbon Graphite? On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma same...@wso2.com wrote: Hi Samisa, We have plans commit Pradeep's change
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
Graphite brings in complexities in comprehension - is it a new project, part of Carbon, extend Carbon etc etc Imagine telling a story along the lines of Carbon has this concpet called P2 and you install Graphite components onto Carbon products using feature manager component On Mon, Feb 13, 2012 at 11:00 AM, Supun Malinga sup...@wso2.com wrote: On Mon, Feb 13, 2012 at 9:28 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Azeez, Let me explain the rationale behind this orbit level change. If you look at the orbit project keeping Carbon aside, it can be considered as a third party project, completely independent from Carbon and Graphite projects. The purpose of the orbit project is to produce OSGi bundles out of third party legacy jars. So the orbit project is not related to Carbon or Graphite by any means. And also changes to these orbit projects is rare, unless we created them in a sloppy manner. Ideally we can upload orbit projects and then developers do not need to build them at all. But, over the time we've missed used the orbit concept. e.g. we have orbit projects corresponding the dependencies projects. These orbits change frequently, since the corresponding dependencies change. By considering all these aspects, we came up with the following structure *orbit* (Consists of all the orbit projects which are used by both Carbon and Graphite projects.) *carbon* *|--* *dependencies* *|-- orbit* (These orbit projects produce bundles out of the Carbon level dependencies.) *graphite* *|-- dependencies* *|-- orbit* (These orbit projects produce bundles out of the Graphite level dependencies.) Please let us know your views on this. +1 thanks, Thanks, Sameera. On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez az...@wso2.com wrote: In this model,. what happens to dependencies orbits that are common to both Carbon Graphite? On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, We have plans commit Pradeep's change in a hackathon mode. His changes is again platform wide change. We can get help from the AS and Jaggery team as well. Lets plan this during the todays meeting. Thanks, Sameera. On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.comwrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *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 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* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
This more like it. On Mon, Feb 13, 2012 at 5:41 PM, Sameera Jayasoma same...@wso2.com wrote: Hi Samisa, As per the offline discussion we had with (you, Azeez, Isuru, Pradeep and others), we identified that the existing structure has its own complexities as illustrated by the Samisa. The proposal was to come up with a toplevel project called carbon and maintain the structure illustrated in the attached image. This change will be a simple SVN move. We will do this once the tomcat OSGification is applied to the carbon trunk. Thanks, Sameera. On Mon, Feb 13, 2012 at 3:59 PM, Samisa Abeysinghe sam...@wso2.comwrote: Graphite brings in complexities in comprehension - is it a new project, part of Carbon, extend Carbon etc etc Imagine telling a story along the lines of Carbon has this concpet called P2 and you install Graphite components onto Carbon products using feature manager component On Mon, Feb 13, 2012 at 11:00 AM, Supun Malinga sup...@wso2.com wrote: On Mon, Feb 13, 2012 at 9:28 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Azeez, Let me explain the rationale behind this orbit level change. If you look at the orbit project keeping Carbon aside, it can be considered as a third party project, completely independent from Carbon and Graphite projects. The purpose of the orbit project is to produce OSGi bundles out of third party legacy jars. So the orbit project is not related to Carbon or Graphite by any means. And also changes to these orbit projects is rare, unless we created them in a sloppy manner. Ideally we can upload orbit projects and then developers do not need to build them at all. But, over the time we've missed used the orbit concept. e.g. we have orbit projects corresponding the dependencies projects. These orbits change frequently, since the corresponding dependencies change. By considering all these aspects, we came up with the following structure *orbit* (Consists of all the orbit projects which are used by both Carbon and Graphite projects.) *carbon* *|--* *dependencies* *|-- orbit* (These orbit projects produce bundles out of the Carbon level dependencies.) *graphite* *|-- dependencies* *|-- orbit* (These orbit projects produce bundles out of the Graphite level dependencies.) Please let us know your views on this. +1 thanks, Thanks, Sameera. On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez az...@wso2.com wrote: In this model,. what happens to dependencies orbits that are common to both Carbon Graphite? On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, We have plans commit Pradeep's change in a hackathon mode. His changes is again platform wide change. We can get help from the AS and Jaggery team as well. Lets plan this during the todays meeting. Thanks, Sameera. On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.com wrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *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 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* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email -
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
kernel - This contains the carbon-core related stuff. platform - This is the new graphite project. This is a simple svn mv. I will write a detailed document explaining above projects as well as branching strategy, support process etc. Thanks, Sameera. On Mon, Feb 13, 2012 at 5:41 PM, Sameera Jayasoma same...@wso2.com wrote: Hi Samisa, As per the offline discussion we had with (you, Azeez, Isuru, Pradeep and others), we identified that the existing structure has its own complexities as illustrated by the Samisa. The proposal was to come up with a toplevel project called carbon and maintain the structure illustrated in the attached image. This change will be a simple SVN move. We will do this once the tomcat OSGification is applied to the carbon trunk. Thanks, Sameera. On Mon, Feb 13, 2012 at 3:59 PM, Samisa Abeysinghe sam...@wso2.comwrote: Graphite brings in complexities in comprehension - is it a new project, part of Carbon, extend Carbon etc etc Imagine telling a story along the lines of Carbon has this concpet called P2 and you install Graphite components onto Carbon products using feature manager component On Mon, Feb 13, 2012 at 11:00 AM, Supun Malinga sup...@wso2.com wrote: On Mon, Feb 13, 2012 at 9:28 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Azeez, Let me explain the rationale behind this orbit level change. If you look at the orbit project keeping Carbon aside, it can be considered as a third party project, completely independent from Carbon and Graphite projects. The purpose of the orbit project is to produce OSGi bundles out of third party legacy jars. So the orbit project is not related to Carbon or Graphite by any means. And also changes to these orbit projects is rare, unless we created them in a sloppy manner. Ideally we can upload orbit projects and then developers do not need to build them at all. But, over the time we've missed used the orbit concept. e.g. we have orbit projects corresponding the dependencies projects. These orbits change frequently, since the corresponding dependencies change. By considering all these aspects, we came up with the following structure *orbit* (Consists of all the orbit projects which are used by both Carbon and Graphite projects.) *carbon* *|--* *dependencies* *|-- orbit* (These orbit projects produce bundles out of the Carbon level dependencies.) *graphite* *|-- dependencies* *|-- orbit* (These orbit projects produce bundles out of the Graphite level dependencies.) Please let us know your views on this. +1 thanks, Thanks, Sameera. On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez az...@wso2.com wrote: In this model,. what happens to dependencies orbits that are common to both Carbon Graphite? On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, We have plans commit Pradeep's change in a hackathon mode. His changes is again platform wide change. We can get help from the AS and Jaggery team as well. Lets plan this during the todays meeting. Thanks, Sameera. On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.com wrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *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 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* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
On Mon, Feb 13, 2012 at 5:45 PM, Sameera Jayasoma same...@wso2.com wrote: kernel - This contains the carbon-core related stuff. platform - This is the new graphite project. This is a simple svn mv. I will write a detailed document explaining above projects as well as branching strategy, support process etc. We might want to wait till wider feedback on this. Thanks, Sameera. On Mon, Feb 13, 2012 at 5:41 PM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, As per the offline discussion we had with (you, Azeez, Isuru, Pradeep and others), we identified that the existing structure has its own complexities as illustrated by the Samisa. The proposal was to come up with a toplevel project called carbon and maintain the structure illustrated in the attached image. This change will be a simple SVN move. We will do this once the tomcat OSGification is applied to the carbon trunk. Thanks, Sameera. On Mon, Feb 13, 2012 at 3:59 PM, Samisa Abeysinghe sam...@wso2.comwrote: Graphite brings in complexities in comprehension - is it a new project, part of Carbon, extend Carbon etc etc Imagine telling a story along the lines of Carbon has this concpet called P2 and you install Graphite components onto Carbon products using feature manager component On Mon, Feb 13, 2012 at 11:00 AM, Supun Malinga sup...@wso2.com wrote: On Mon, Feb 13, 2012 at 9:28 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Azeez, Let me explain the rationale behind this orbit level change. If you look at the orbit project keeping Carbon aside, it can be considered as a third party project, completely independent from Carbon and Graphite projects. The purpose of the orbit project is to produce OSGi bundles out of third party legacy jars. So the orbit project is not related to Carbon or Graphite by any means. And also changes to these orbit projects is rare, unless we created them in a sloppy manner. Ideally we can upload orbit projects and then developers do not need to build them at all. But, over the time we've missed used the orbit concept. e.g. we have orbit projects corresponding the dependencies projects. These orbits change frequently, since the corresponding dependencies change. By considering all these aspects, we came up with the following structure *orbit* (Consists of all the orbit projects which are used by both Carbon and Graphite projects.) *carbon* *|--* *dependencies* *|-- orbit* (These orbit projects produce bundles out of the Carbon level dependencies.) *graphite* *|-- dependencies* *|-- orbit* (These orbit projects produce bundles out of the Graphite level dependencies.) Please let us know your views on this. +1 thanks, Thanks, Sameera. On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez az...@wso2.com wrote: In this model,. what happens to dependencies orbits that are common to both Carbon Graphite? On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, We have plans commit Pradeep's change in a hackathon mode. His changes is again platform wide change. We can get help from the AS and Jaggery team as well. Lets plan this during the todays meeting. Thanks, Sameera. On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.com wrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.com wrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *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 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* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
Hi, Also it would be a good idea to make sure code can be frozen from each sub level(kernel, orbit and platform). AFAIU it has to be configured with svn. thanks, On Mon, Feb 13, 2012 at 5:41 PM, Sameera Jayasoma same...@wso2.com wrote: Hi Samisa, As per the offline discussion we had with (you, Azeez, Isuru, Pradeep and others), we identified that the existing structure has its own complexities as illustrated by the Samisa. The proposal was to come up with a toplevel project called carbon and maintain the structure illustrated in the attached image. This change will be a simple SVN move. We will do this once the tomcat OSGification is applied to the carbon trunk. Thanks, Sameera. On Mon, Feb 13, 2012 at 3:59 PM, Samisa Abeysinghe sam...@wso2.comwrote: Graphite brings in complexities in comprehension - is it a new project, part of Carbon, extend Carbon etc etc Imagine telling a story along the lines of Carbon has this concpet called P2 and you install Graphite components onto Carbon products using feature manager component On Mon, Feb 13, 2012 at 11:00 AM, Supun Malinga sup...@wso2.com wrote: On Mon, Feb 13, 2012 at 9:28 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Azeez, Let me explain the rationale behind this orbit level change. If you look at the orbit project keeping Carbon aside, it can be considered as a third party project, completely independent from Carbon and Graphite projects. The purpose of the orbit project is to produce OSGi bundles out of third party legacy jars. So the orbit project is not related to Carbon or Graphite by any means. And also changes to these orbit projects is rare, unless we created them in a sloppy manner. Ideally we can upload orbit projects and then developers do not need to build them at all. But, over the time we've missed used the orbit concept. e.g. we have orbit projects corresponding the dependencies projects. These orbits change frequently, since the corresponding dependencies change. By considering all these aspects, we came up with the following structure *orbit* (Consists of all the orbit projects which are used by both Carbon and Graphite projects.) *carbon* *|--* *dependencies* *|-- orbit* (These orbit projects produce bundles out of the Carbon level dependencies.) *graphite* *|-- dependencies* *|-- orbit* (These orbit projects produce bundles out of the Graphite level dependencies.) Please let us know your views on this. +1 thanks, Thanks, Sameera. On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez az...@wso2.com wrote: In this model,. what happens to dependencies orbits that are common to both Carbon Graphite? On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, We have plans commit Pradeep's change in a hackathon mode. His changes is again platform wide change. We can get help from the AS and Jaggery team as well. Lets plan this during the todays meeting. Thanks, Sameera. On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.com wrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *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 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* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org
[Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
Hi Devs, We have now completed the SVN restructure effort. Please checkout orbit[1], carbon[2] and graphite[3] svn repositories. Carefully go through the following instructions before building. 1) Take fresh checkouts of the orbit[1], carbon[2] and graphite[3] svn repositories. Avoid using the existing local carbon checkout, if any. 2) Backup your .m2 repository and start the build with a fresh one. This step is optional. 3) Build orbit[1] project. 4) Build carbon[2] project. 5) Build graphite[3] project. Apart from some test failures, build is stable now. I would like to thank Pradeep, Dileepa and Chethiya for their help to get this done during the past two days. Thanks, Sameera. [1] https://svn.wso2.org/repos/wso2/trunk/orbit/ [2] https://svn.wso2.org/repos/wso2/trunk/carbon/ [3] https://svn.wso2.org/repos/wso2/trunk/graphite/ -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
Great job guys :). This will help tremendously as we go forward with Carbon becoming more and more of a stable platform! Sanjiva. On Mon, Feb 13, 2012 at 12:25 AM, Sameera Jayasoma same...@wso2.com wrote: Hi Devs, We have now completed the SVN restructure effort. Please checkout orbit[1], carbon[2] and graphite[3] svn repositories. Carefully go through the following instructions before building. 1) Take fresh checkouts of the orbit[1], carbon[2] and graphite[3] svn repositories. Avoid using the existing local carbon checkout, if any. 2) Backup your .m2 repository and start the build with a fresh one. This step is optional. 3) Build orbit[1] project. 4) Build carbon[2] project. 5) Build graphite[3] project. Apart from some test failures, build is stable now. I would like to thank Pradeep, Dileepa and Chethiya for their help to get this done during the past two days. Thanks, Sameera. [1] https://svn.wso2.org/repos/wso2/trunk/orbit/ [2] https://svn.wso2.org/repos/wso2/trunk/carbon/ [3] https://svn.wso2.org/repos/wso2/trunk/graphite/ -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sanjiva Weerawarana, Ph.D. Founder, Chairman CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
Hmmm is there a future step we need to take to make each of the repos into
separate projects? That is:
/repos/wso2/{orbit,carbon,graphite}/{trunk,branches,tags}
I guess without that we still have to branch etc. all together. I guess
this change is the one which is a lot more dramatic in terms of impact to
support etc..
Sanjiva.
On Mon, Feb 13, 2012 at 5:00 AM, Sanjiva Weerawarana sanj...@wso2.comwrote:
Great job guys :). This will help tremendously as we go forward with
Carbon becoming more and more of a stable platform!
Sanjiva.
On Mon, Feb 13, 2012 at 12:25 AM, Sameera Jayasoma same...@wso2.comwrote:
Hi Devs,
We have now completed the SVN restructure effort. Please checkout
orbit[1], carbon[2] and graphite[3] svn repositories. Carefully go through
the following instructions before building.
1) Take fresh checkouts of the orbit[1], carbon[2] and graphite[3] svn
repositories. Avoid using the existing local carbon checkout, if any.
2) Backup your .m2 repository and start the build with a fresh one. This
step is optional.
3) Build orbit[1] project.
4) Build carbon[2] project.
5) Build graphite[3] project.
Apart from some test failures, build is stable now.
I would like to thank Pradeep, Dileepa and Chethiya for their help to get
this done during the past two days.
Thanks,
Sameera.
[1] https://svn.wso2.org/repos/wso2/trunk/orbit/
[2] https://svn.wso2.org/repos/wso2/trunk/carbon/
[3] https://svn.wso2.org/repos/wso2/trunk/graphite/
--
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon
WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org
Lean . Enterprise . Middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman CEO; WSO2, Inc.; http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/
Lean . Enterprise . Middleware
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman CEO; WSO2, Inc.; http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/
Lean . Enterprise . Middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
On Mon, Feb 13, 2012 at 12:25 AM, Sameera Jayasoma same...@wso2.com wrote: Hi Devs, We have now completed the SVN restructure effort. Please checkout orbit[1], carbon[2] and graphite[3] svn repositories. Carefully go through the following instructions before building. 1) Take fresh checkouts of the orbit[1], carbon[2] and graphite[3] svn repositories. Avoid using the existing local carbon checkout, if any. 2) Backup your .m2 repository and start the build with a fresh one. This step is optional. 3) Build orbit[1] project. 4) Build carbon[2] project. 5) Build graphite[3] project. Apart from some test failures, build is stable now. I would like to thank Pradeep, Dileepa and Chethiya for their help to get this done during the past two days. and charith and shammi, for helping out with bamboo builds. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.com wrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. thanks, --Pradeep ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.com wrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.comwrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
On Mon, Feb 13, 2012 at 7:57 AM, Pradeep Fernando prad...@wso2.com wrote: On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.comwrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. please have it 12 noon. after * 12 noon thanks, --Pradeep -- Pradeep Fernando Software Engineer WSO2 Inc; http://wso2.com/ blog: http://pradeepfernando.blogspot.com/ m: +94776603662 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.com wrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.comwrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. please have it 12 noon. thanks, --Pradeep ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
Invite was sent last Friday On Mon, Feb 13, 2012 at 7:58 AM, Pradeep Fernando prad...@wso2.com wrote: On Mon, Feb 13, 2012 at 7:57 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.comwrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. please have it 12 noon. after * 12 noon thanks, --Pradeep -- Pradeep Fernando Software Engineer WSO2 Inc; http://wso2.com/ blog: http://pradeepfernando.blogspot.com/ m: +94776603662 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
On Mon, Feb 13, 2012 at 8:32 AM, Samisa Abeysinghe sam...@wso2.com wrote: Invite was sent last Friday On Mon, Feb 13, 2012 at 7:58 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 7:57 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.comwrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. please have it 12 noon. after * 12 noon o my bad. sorry. thanks, --Pradeep -- Pradeep Fernando Software Engineer WSO2 Inc; http://wso2.com/ blog: http://pradeepfernando.blogspot.com/ m: +94776603662 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Pradeep Fernando Software Engineer WSO2 Inc; http://wso2.com/ blog: http://pradeepfernando.blogspot.com/ m: +94776603662 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
Hi Sanjiva,
Following is model we've been following. We have top level trunk, branches
and tags repositories.
https://svn.wso2.org/repos/wso2/trunk/
https://svn.wso2.org/repos/wso2/branches/
https://svn.wso2.org/repos/wso2/tags/
e.g. Previous Carbon project trunk, branch and tags were created as
following.
https://svn.wso2.org/repos/wso2/trunk/carbon/
https://svn.wso2.org/repos/wso2/branches/carbon/
https://svn.wso2.org/repos/wso2/tags/carbon/
We thought of following the same structure for these new orbit and graphite
projects.
I understand your point. Lets have a discussion on this.
Thanks,
Sameera.
On Mon, Feb 13, 2012 at 5:04 AM, Sanjiva Weerawarana sanj...@wso2.comwrote:
Hmmm is there a future step we need to take to make each of the repos into
separate projects? That is:
/repos/wso2/{orbit,carbon,graphite}/{trunk,branches,tags}
I guess without that we still have to branch etc. all together. I guess
this change is the one which is a lot more dramatic in terms of impact to
support etc..
Sanjiva.
On Mon, Feb 13, 2012 at 5:00 AM, Sanjiva Weerawarana sanj...@wso2.comwrote:
Great job guys :). This will help tremendously as we go forward with
Carbon becoming more and more of a stable platform!
Sanjiva.
On Mon, Feb 13, 2012 at 12:25 AM, Sameera Jayasoma same...@wso2.comwrote:
Hi Devs,
We have now completed the SVN restructure effort. Please checkout
orbit[1], carbon[2] and graphite[3] svn repositories. Carefully go through
the following instructions before building.
1) Take fresh checkouts of the orbit[1], carbon[2] and graphite[3] svn
repositories. Avoid using the existing local carbon checkout, if any.
2) Backup your .m2 repository and start the build with a fresh one. This
step is optional.
3) Build orbit[1] project.
4) Build carbon[2] project.
5) Build graphite[3] project.
Apart from some test failures, build is stable now.
I would like to thank Pradeep, Dileepa and Chethiya for their help to
get this done during the past two days.
Thanks,
Sameera.
[1] https://svn.wso2.org/repos/wso2/trunk/orbit/
[2] https://svn.wso2.org/repos/wso2/trunk/carbon/
[3] https://svn.wso2.org/repos/wso2/trunk/graphite/
--
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon
WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org
Lean . Enterprise . Middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman CEO; WSO2, Inc.; http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/
Lean . Enterprise . Middleware
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman CEO; WSO2, Inc.; http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/
Lean . Enterprise . Middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon
WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org
Lean . Enterprise . Middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
Hi Samisa, We have plans commit Pradeep's change in a hackathon mode. His changes is again platform wide change. We can get help from the AS and Jaggery team as well. Lets plan this during the todays meeting. Thanks, Sameera. On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.com wrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.comwrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
In this model,. what happens to dependencies orbits that are common to both Carbon Graphite? On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma same...@wso2.com wrote: Hi Samisa, We have plans commit Pradeep's change in a hackathon mode. His changes is again platform wide change. We can get help from the AS and Jaggery team as well. Lets plan this during the todays meeting. Thanks, Sameera. On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.comwrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *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 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* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
Currently [1] lists the below, - .. https://svn.wso2.org/repos/wso2/ - carbon/ https://svn.wso2.org/repos/wso2/trunk/carbon/ - commons/ https://svn.wso2.org/repos/wso2/trunk/commons/ - graphite/ https://svn.wso2.org/repos/wso2/trunk/graphite/ - interop/ https://svn.wso2.org/repos/wso2/trunk/interop/ - orbit/ https://svn.wso2.org/repos/wso2/trunk/orbit/ - ozone/ https://svn.wso2.org/repos/wso2/trunk/ozone/ - stratos/ https://svn.wso2.org/repos/wso2/trunk/stratos/ - tools/ https://svn.wso2.org/repos/wso2/trunk/tools/ - wsf/ https://svn.wso2.org/repos/wso2/trunk/wsf/ It is somewhat misleading in the importance scale and a bit more difficult in checking out. Presence of ozone, stratos, and wsf here are somewhat confusing, at least for me. If someone wants to have a one-checkout of all from [1], he will be checking out unrelated stuff like the above I mentioned. We might need a bit of clean up in [1], I feel. [1] https://svn.wso2.org/repos/wso2/trunk/ Regards, Pradeeban. On Mon, Feb 13, 2012 at 12:25 AM, Sameera Jayasoma same...@wso2.com wrote: Hi Devs, We have now completed the SVN restructure effort. Please checkout orbit[1], carbon[2] and graphite[3] svn repositories. Carefully go through the following instructions before building. 1) Take fresh checkouts of the orbit[1], carbon[2] and graphite[3] svn repositories. Avoid using the existing local carbon checkout, if any. 2) Backup your .m2 repository and start the build with a fresh one. This step is optional. 3) Build orbit[1] project. 4) Build carbon[2] project. 5) Build graphite[3] project. Apart from some test failures, build is stable now. I would like to thank Pradeep, Dileepa and Chethiya for their help to get this done during the past two days. Thanks, Sameera. [1] https://svn.wso2.org/repos/wso2/trunk/orbit/ [2] https://svn.wso2.org/repos/wso2/trunk/carbon/ [3] https://svn.wso2.org/repos/wso2/trunk/graphite/ -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Kathiravelu Pradeeban. Software Engineer. Cloud Technologies Team. WSO2 Inc. Blog: [Llovizna] http://kkpradeeban.blogspot.com/ M: +94 776 477 976 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
Hi Azeez, Let me explain the rationale behind this orbit level change. If you look at the orbit project keeping Carbon aside, it can be considered as a third party project, completely independent from Carbon and Graphite projects. The purpose of the orbit project is to produce OSGi bundles out of third party legacy jars. So the orbit project is not related to Carbon or Graphite by any means. And also changes to these orbit projects is rare, unless we created them in a sloppy manner. Ideally we can upload orbit projects and then developers do not need to build them at all. But, over the time we've missed used the orbit concept. e.g. we have orbit projects corresponding the dependencies projects. These orbits change frequently, since the corresponding dependencies change. By considering all these aspects, we came up with the following structure *orbit* (Consists of all the orbit projects which are used by both Carbon and Graphite projects.) *carbon* *|--* *dependencies* *|-- orbit* (These orbit projects produce bundles out of the Carbon level dependencies.) *graphite* *|-- dependencies* *|-- orbit* (These orbit projects produce bundles out of the Graphite level dependencies.) Please let us know your views on this. Thanks, Sameera. On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez az...@wso2.com wrote: In this model,. what happens to dependencies orbits that are common to both Carbon Graphite? On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, We have plans commit Pradeep's change in a hackathon mode. His changes is again platform wide change. We can get help from the AS and Jaggery team as well. Lets plan this during the todays meeting. Thanks, Sameera. On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.comwrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *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 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* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
Sounds good. On Mon, Feb 13, 2012 at 9:28 AM, Sameera Jayasoma same...@wso2.com wrote: Hi Azeez, Let me explain the rationale behind this orbit level change. If you look at the orbit project keeping Carbon aside, it can be considered as a third party project, completely independent from Carbon and Graphite projects. The purpose of the orbit project is to produce OSGi bundles out of third party legacy jars. So the orbit project is not related to Carbon or Graphite by any means. And also changes to these orbit projects is rare, unless we created them in a sloppy manner. Ideally we can upload orbit projects and then developers do not need to build them at all. But, over the time we've missed used the orbit concept. e.g. we have orbit projects corresponding the dependencies projects. These orbits change frequently, since the corresponding dependencies change. By considering all these aspects, we came up with the following structure *orbit* (Consists of all the orbit projects which are used by both Carbon and Graphite projects.) *carbon* *|--* *dependencies* *|-- orbit* (These orbit projects produce bundles out of the Carbon level dependencies.) *graphite* *|-- dependencies* *|-- orbit* (These orbit projects produce bundles out of the Graphite level dependencies.) Please let us know your views on this. Thanks, Sameera. On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez az...@wso2.com wrote: In this model,. what happens to dependencies orbits that are common to both Carbon Graphite? On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, We have plans commit Pradeep's change in a hackathon mode. His changes is again platform wide change. We can get help from the AS and Jaggery team as well. Lets plan this during the todays meeting. Thanks, Sameera. On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.comwrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *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 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* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *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 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* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
On Mon, Feb 13, 2012 at 9:28 AM, Sameera Jayasoma same...@wso2.com wrote: Hi Azeez, Let me explain the rationale behind this orbit level change. If you look at the orbit project keeping Carbon aside, it can be considered as a third party project, completely independent from Carbon and Graphite projects. The purpose of the orbit project is to produce OSGi bundles out of third party legacy jars. So the orbit project is not related to Carbon or Graphite by any means. And also changes to these orbit projects is rare, unless we created them in a sloppy manner. Ideally we can upload orbit projects and then developers do not need to build them at all. But, over the time we've missed used the orbit concept. e.g. we have orbit projects corresponding the dependencies projects. These orbits change frequently, since the corresponding dependencies change. By considering all these aspects, we came up with the following structure *orbit* (Consists of all the orbit projects which are used by both Carbon and Graphite projects.) *carbon* *|--* *dependencies* *|-- orbit* (These orbit projects produce bundles out of the Carbon level dependencies.) *graphite* *|-- dependencies* *|-- orbit* (These orbit projects produce bundles out of the Graphite level dependencies.) Please let us know your views on this. +1 thanks, Thanks, Sameera. On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez az...@wso2.com wrote: In this model,. what happens to dependencies orbits that are common to both Carbon Graphite? On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Samisa, We have plans commit Pradeep's change in a hackathon mode. His changes is again platform wide change. We can get help from the AS and Jaggery team as well. Lets plan this during the todays meeting. Thanks, Sameera. On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.comwrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.comwrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *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 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* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
