Hi Lalaji

On Thu, Aug 15, 2013 at 8:48 PM, Lalaji Sureshika <[email protected]> wrote:

> Hi Nuwan,
>
> Yes,we have started working on 4.2.0 branch. But isn't that we need to
> commit to both trunk and branch here onwards.. ? And additionally there
> were some fixes done in trunk and which were not commit during frozen
> time.Problem we are facing is,we cannot build and verify the fixes done
>  from a trunk build pack..
>

That is correct, we will create a new jaggery trunk so that it can be
linked in carbon trunk, meantime please please work on the branch.

@Madhuka,

Can you create a new jaggery branch to link with carbon trunk. later we
will merge with jaggery master

Regards,
/Nuwan


>
> Thanks;
>
>
>
> On Thu, Aug 15, 2013 at 7:01 AM, Nuwan Bandara <[email protected]> wrote:
>
>> Hi lalaji,
>>
>> You should be working on the branch now, last night the the versions were
>> changed in the jaggery 4.2.0 branch to be compatible with carbon release
>> branch.
>>
>> Regards,
>> /Nuwan
>>
>>
>> On Thu, Aug 15, 2013 at 5:51 PM, Lalaji Sureshika <[email protected]>wrote:
>>
>>> Hi,
>>>
>>> We are getting below error[1] when building trunk/features. Note there
>>> was an error on referring trunk carbon version as 4.2.0[not
>>> 4.2.0-SNAPSHOT]  from jaggery server feature.And even we fix that issue ,we
>>> are getting below error.
>>>
>>> [1] [ERROR] Failed to execute goal on project org.jaggeryjs.server.feature:
>>> Could not resolve dependencies for project org.jaggeryjs:o
>>> rg.jaggeryjs.server.feature:pom:0.9.0-07262013: The following artifacts
>>> could not be resolved: org.wso2.carbon:org.wso2.carbon.registry.ws.c
>>> lient:jar:4.2.0, org.wso2.carbon:org.wso2.carbon.context:jar:4.2.0-SNAPSHOT,
>>> org.wso2.carbon:org.wso2.carbon.ndatasource.core:jar:4.2.0: Failure to
>>> find org.wso2.carbon:org.wso2.carbon.registry.ws.client:jar:4.2.0 in
>>> http://dist.wso2.org/maven2/ was cached in the local repository,
>>> resolution will not be reattempted until the update interval of
>>> wso2-maven2-repository has elapsed or updates are forced -> [Help 1]
>>>
>>> Thanks;
>>> --
>>> Lalaji Sureshika
>>> WSO2, Inc.;  http://wso2.com/
>>> email: [email protected]; cell: +94 71 608 6811
>>> blog: http://lalajisureshika.blogspot.com
>>>
>>>
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> [email protected]
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Thanks & Regards,
>>
>> Nuwan Bandara
>> Technical Lead; **WSO2 Inc. *
>> *lean . enterprise . middleware |  http://wso2.com *
>> *blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763
>> 9629
>> *
>> <http://www.nuwanbando.com/>
>>
>
>
>
> --
> Lalaji Sureshika
> WSO2, Inc.;  http://wso2.com/
> email: [email protected]; cell: +94 71 608 6811
> blog: http://lalajisureshika.blogspot.com
>
>
>


-- 
*Thanks & Regards,

Nuwan Bandara
Technical Lead; **WSO2 Inc. *
*lean . enterprise . middleware |  http://wso2.com *
*blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 9629
*
<http://www.nuwanbando.com/>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to