Hi KasunG,
I tried building with the updated orbit and still I am getting build
failures .. the issue is that its pointing to the wrong parent pom ?!
<parent>
<groupId>org.wso2.carbon</groupId>
*<artifactId>orbit-parent</artifactId>*
<version>4.1.0</version>
*<relativePath>../../pom.xml</relativePath>*
</parent>
On Mon, Mar 4, 2013 at 12:58 PM, Kasun Gajasinghe <[email protected]> wrote:
>
> I have added the svn externals to orbit trunk. So, there's no need to
> build 4.1.0 orbit branch anymore. Please take an update in orbit *trunk*,
> and build it before building kernel and platform.
>
>
> On Mon, Mar 4, 2013 at 11:49 AM, Supun Malinga <[email protected]> wrote:
>
>> Hi,
>>
>> Since most folks who are starting to build trunk get confused of this we
>> will add orbit 4.1.0 bundles as externals to the orbit trunk, for the
>> moment. After orbit 4.1.0 is released, we will remove the external.
>> Also right now wadl-core is duplicated in both trunk and branch. Either
>> upgrade the trunk version or remove the trunk wadl-core and add an external
>> from the branch.
>>
>> thanks,
>>
>>
>> On Sun, Mar 3, 2013 at 6:12 PM, Kasun Gajasinghe <[email protected]> wrote:
>>
>>> Hi Eranda,
>>>
>>>
>>>
>>>
>>> On Sun, Mar 3, 2013 at 6:00 PM, Eranda Sooriyabandara
>>> <[email protected]>wrote:
>>>
>>>> Hi all,
>>>> What you guys suggest was a workaround and it is fundamentally wrong.
>>>> Isn't it? One who checking out and build the trunk also need to checkout
>>>> the 4.1.0 branch and build. Anyway since we don't have people who work with
>>>> trunk, no trouble.
>>>>
>>>>
>>> There will be a little annoyance until we do the 4.1.0 release which is
>>> due in less than two weeks. When it's released, we will be hosting the
>>> orbit bundles in wso2 nexus maven repo. After that, you do not have to
>>> build the 4.1.0 orbit branch.
>>>
>>> We have only maintained 4.1.0 orbit branch, and haven't worked on orbit
>>> trunk. This isn't really a workaround rather an annoyance until the
>>> release. Hope you understand.
>>>
>>>
>>>> thanks
>>>> Eranda
>>>>
>>>>
>>>> On Sun, Mar 3, 2013 at 4:09 PM, Supun Malinga <[email protected]> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> First of all, there is no orbit trunk as for the moment. There is a
>>>>> svn dir. but that pretty much outdated. Since we need some orbit bundles
>>>>> for the 4.1.0 release, we decided to directly create orbit 4.1.0 branch
>>>>> instead of orbit trunk. So if you are building trunk, please keep in mind
>>>>> there is no orbit trunk at the moment, and the trunk is dependent on the
>>>>> 4.1.0 orbit branch. Guess that'a fair enough. And if this still concerns,
>>>>> we shld be able to release the orbit 4.1.0 now.
>>>>>
>>>>> thanks,
>>>>>
>>>>>
>>>>> On Sun, Mar 3, 2013 at 3:52 PM, Sagara Gunathunga <[email protected]>wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Mar 3, 2013 at 2:50 PM, Dileepa Jayakody <[email protected]>wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Mar 3, 2013 at 11:00 AM, Eranda Sooriyabandara <
>>>>>>> [email protected]> wrote:
>>>>>>>
>>>>>>>> Hi Dileepa,
>>>>>>>>
>>>>>>>>
>>>>>>>> Yes, the tomcat 7.0.34.wso2v1 bundle is not added to trunk. it's in
>>>>>>>>> 4.1.0 branch, and we haven't released it yet. So for the moment we'll
>>>>>>>>> have
>>>>>>>>> to build (only) orbit 4.1.0 branch before building trunk.
>>>>>>>>>
>>>>>>>>>
>>>>>>>> Normally we branch from trunk. What I have felt here is on the
>>>>>>>> other way around. When creating the 4.1.0 branch the code what you
>>>>>>>> mentioned missing should be there in the orbit trunk. Isn't it what
>>>>>>>> should
>>>>>>>> be?
>>>>>>>>
>>>>>>>
>>>>>>> Yes, I think the reason is orbit 4.1.0 branch has being created
>>>>>>> separately without merging from orbit trunk, hence the new tomcat orbit
>>>>>>> version is not there in trunk. Perhaps we should
>>>>>>> merge the 4.1.0 orbits to trunk.
>>>>>>>
>>>>>>
>>>>>> Yes, That was the reason.
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> @Kishanthan,
>>>>>>> was there any specific reason to add the new tomcat bundles to 4.1.0
>>>>>>> branch and not trunk?maybe we can commit them to trunk to avoid build
>>>>>>> failures?
>>>>>>>
>>>>>>
>>>>>> There is no specific reason, please go ahead and merge to the trunk.
>>>>>>
>>>>>> Thanks !
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Dileepa
>>>>>>>
>>>>>>>
>>>>>>>> thanks
>>>>>>>> Eranda
>>>>>>>>
>>>>>>>> *
>>>>>>>> *
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Dileepa Jayakody,
>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>> Lean . Enterprise . Middleware
>>>>>>>
>>>>>>> Mobile : +94777-857616
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Dev mailing list
>>>>>>> [email protected]
>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sagara Gunathunga
>>>>>>
>>>>>> Technical Lead; WSO2, Inc.; http://wso2.com
>>>>>> V.P Apache Web Services ; http://ws.apache.org/
>>>>>> Blog ; http://ssagara.blogspot.com
>>>>>>
>>>>>> _______________________________________________
>>>>>> Dev mailing list
>>>>>> [email protected]
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Supun Malinga,
>>>>>
>>>>> Software Engineer,
>>>>> WSO2 Inc.
>>>>> http://wso2.com
>>>>> http://wso2.org
>>>>> email - [email protected] <[email protected]>
>>>>> mobile - 071 56 91 321
>>>>>
>>>>> _______________________________________________
>>>>> Dev mailing list
>>>>> [email protected]
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Eranda Sooriyabandara
>>>> *Software Engineer;
>>>> Integration Technologies Team;
>>>> WSO2 Inc.; http://wso2.com
>>>>
>>>> *
>>>> *
>>>>
>>>> _______________________________________________
>>>> Dev mailing list
>>>> [email protected]
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *Kasun Gajasinghe*
>>> Software Engineer;
>>> Development Technologies Team, WSO2 Inc.; http://wso2.com ,
>>> *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe*
>>> *
>>> *blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org>*
>>> twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>*
>>> *
>>>
>>>
>>> On Sun, Mar 3, 2013 at 6:00 PM, Eranda Sooriyabandara
>>> <[email protected]>wrote:
>>>
>>>> Hi all,
>>>> What you guys suggest was a workaround and it is fundamentally wrong.
>>>> Isn't it? One who checking out and build the trunk also need to checkout
>>>> the 4.1.0 branch and build. Anyway since we don't have people who work with
>>>> trunk, no trouble.
>>>>
>>>> thanks
>>>> Eranda
>>>>
>>>>
>>>> On Sun, Mar 3, 2013 at 4:09 PM, Supun Malinga <[email protected]> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> First of all, there is no orbit trunk as for the moment. There is a
>>>>> svn dir. but that pretty much outdated. Since we need some orbit bundles
>>>>> for the 4.1.0 release, we decided to directly create orbit 4.1.0 branch
>>>>> instead of orbit trunk. So if you are building trunk, please keep in mind
>>>>> there is no orbit trunk at the moment, and the trunk is dependent on the
>>>>> 4.1.0 orbit branch. Guess that'a fair enough. And if this still concerns,
>>>>> we shld be able to release the orbit 4.1.0 now.
>>>>>
>>>>> thanks,
>>>>>
>>>>>
>>>>> On Sun, Mar 3, 2013 at 3:52 PM, Sagara Gunathunga <[email protected]>wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Mar 3, 2013 at 2:50 PM, Dileepa Jayakody <[email protected]>wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Mar 3, 2013 at 11:00 AM, Eranda Sooriyabandara <
>>>>>>> [email protected]> wrote:
>>>>>>>
>>>>>>>> Hi Dileepa,
>>>>>>>>
>>>>>>>>
>>>>>>>> Yes, the tomcat 7.0.34.wso2v1 bundle is not added to trunk. it's in
>>>>>>>>> 4.1.0 branch, and we haven't released it yet. So for the moment we'll
>>>>>>>>> have
>>>>>>>>> to build (only) orbit 4.1.0 branch before building trunk.
>>>>>>>>>
>>>>>>>>>
>>>>>>>> Normally we branch from trunk. What I have felt here is on the
>>>>>>>> other way around. When creating the 4.1.0 branch the code what you
>>>>>>>> mentioned missing should be there in the orbit trunk. Isn't it what
>>>>>>>> should
>>>>>>>> be?
>>>>>>>>
>>>>>>>
>>>>>>> Yes, I think the reason is orbit 4.1.0 branch has being created
>>>>>>> separately without merging from orbit trunk, hence the new tomcat orbit
>>>>>>> version is not there in trunk. Perhaps we should
>>>>>>> merge the 4.1.0 orbits to trunk.
>>>>>>>
>>>>>>
>>>>>> Yes, That was the reason.
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> @Kishanthan,
>>>>>>> was there any specific reason to add the new tomcat bundles to 4.1.0
>>>>>>> branch and not trunk?maybe we can commit them to trunk to avoid build
>>>>>>> failures?
>>>>>>>
>>>>>>
>>>>>> There is no specific reason, please go ahead and merge to the trunk.
>>>>>>
>>>>>> Thanks !
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Dileepa
>>>>>>>
>>>>>>>
>>>>>>>> thanks
>>>>>>>> Eranda
>>>>>>>>
>>>>>>>> *
>>>>>>>> *
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Dileepa Jayakody,
>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>> Lean . Enterprise . Middleware
>>>>>>>
>>>>>>> Mobile : +94777-857616
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Dev mailing list
>>>>>>> [email protected]
>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sagara Gunathunga
>>>>>>
>>>>>> Technical Lead; WSO2, Inc.; http://wso2.com
>>>>>> V.P Apache Web Services ; http://ws.apache.org/
>>>>>> Blog ; http://ssagara.blogspot.com
>>>>>>
>>>>>> _______________________________________________
>>>>>> Dev mailing list
>>>>>> [email protected]
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Supun Malinga,
>>>>>
>>>>> Software Engineer,
>>>>> WSO2 Inc.
>>>>> http://wso2.com
>>>>> http://wso2.org
>>>>> email - [email protected] <[email protected]>
>>>>> mobile - 071 56 91 321
>>>>>
>>>>> _______________________________________________
>>>>> Dev mailing list
>>>>> [email protected]
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Eranda Sooriyabandara
>>>> *Software Engineer;
>>>> Integration Technologies Team;
>>>> WSO2 Inc.; http://wso2.com
>>>>
>>>> *
>>>> *
>>>>
>>>> _______________________________________________
>>>> Dev mailing list
>>>> [email protected]
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *Kasun Gajasinghe*
>>> Software Engineer;
>>> Development Technologies Team, WSO2 Inc.; http://wso2.com ,
>>> *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe*
>>> *
>>> *blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org>*
>>> twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>*
>>> *
>>>
>>
>>
>>
>> --
>> Supun Malinga,
>>
>> Software Engineer,
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>> email - [email protected] <[email protected]>
>> mobile - 071 56 91 321
>>
>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> Development Technologies Team, WSO2 Inc.; http://wso2.com ,
> *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe*
> *
> *blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org>*
> twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>*
> *
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Thanks,
Shariq.
Phone: +94 777 202 225
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
