cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Min Chen (JIRA)" <>
Subject [jira] [Resolved] (CLOUDSTACK-936) ASF master nonoss build failed
Date Thu, 10 Jan 2013 06:54:12 GMT


Min Chen resolved CLOUDSTACK-936.

    Resolution: Fixed

Fixed by commit dcbb0ecef53644373ea9345959e754cdeb7526a7
> ASF master nonoss build failed
> ------------------------------
>                 Key: CLOUDSTACK-936
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.1.0
>            Reporter: Pradeep Soundararajan
>            Assignee: Min Chen
>            Priority: Critical
>         Attachments: RE  ASF master nonoss build failed.msg
> From today I am unable to build nonoss build from ASF master.
> I am assigning this defect as per Rohit comments:
> >>
> Hi Pradeep,
> That is part of the response change. ClusterVSMMapVO does not have a uuid column and
the addProxyObject with args definition (java.lang.String,long,java.lang.String) was removed
and replaced with (java.lang.String).
> I don't know the best way to fix this, I can re-add the deleted/old method and keep both
of the methods; a lot of exception classes have addProxyObject with the definition that accepts
tablename, id and column, I'm not sure if we want the old methods or have them replaces by
new one (uuid one will help us escape manually putting table name for all exceptions).
> Pl. open a jira issue and assign to Min, she would be able to suggest the best way to
fix it, also because there are a lot of cmd classes and managerimpls (service layer) where
this pattern can be seen.
> Git commit in which the old method was removed:
> commit a88ce6bb7f495dddeb954d1fc7826176646b3590
> Author: Min Chen <>
> Date:   Wed Dec 19 23:49:44 2012 -0800
>     Remove IdentityProxy from CloudException and ExceptionResponse.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message