cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kelven Yang <kelven.y...@citrix.com>
Subject Re: Jetty Failing on latest master due to class UCS manager not Found
Date Wed, 27 Mar 2013 23:09:24 GMT
UCS issue is a POM dependency issue, the UCS project is not declared to be
a dependency in the master project.

GSLB autowiring is caused by that a referenced Netscalar network element
class is only available in Non-OSS build, if Netscalar element is only
available in non-OSS, we need to move its referencing classes to the right
place, or the other way around?

Can someone clarify where Netscalar element should belong to (OSS or Non
OSS)?

Kelven

On 3/27/13 3:03 PM, "David Nalley" <david@gnsa.us> wrote:

>On Wed, Mar 27, 2013 at 5:16 PM, Pranav Saxena <pranav.saxena@citrix.com>
>wrote:
>> Reverting these two commits makes jetty run successfully and the UI
>>launches and works fine but the user is already logged in as admin the
>>first time instead of the user entering the credentials himself  (may be
>>due to single sign on )  -
>>
>> 1) Commit: 99ea4011b18356d09686889205ef5df1b170b0dc ( UCS class issue)
>> 2) Commit : c5fb8349bf92b48bca6d06370112f5ec04a9d098 (GSLB feature  -
>>autowiring issues)
>>
>> @Chip - Should I go ahead and revert these two commits to get the
>>master branch up and  running ?
>>
>
>Pranav:
>
>In such matters you have as much authority as Chip. You don't need to
>ask his permission.
>
>--David


Mime
View raw message