On 29/03/13 12:45 AM, "Chiradeep Vittal"
wrote:
>For optional dependencies, JSR330 injection requires using setter
>injection.
>You should write
>
>@Inject void setGslbProvider(GslbProvider provider) {
> this._gslbProvider = provider;
>}
Thanks Chiradeep for suggestion. But due to Spring defaul
For optional dependencies, JSR330 injection requires using setter
injection.
You should write
@Inject void setGslbProvider(GslbProvider provider) {
this._gslbProvider = provider;
}
On 3/27/13 8:36 PM, "Murali Reddy" wrote:
>On 28/03/13 9:00 AM, "Rajesh Battala" wrote:
>
>>Jetty is failing
Yang
Cc: cloudstack-...@incubator.apache.org
Subject: RE: Jetty Failing on latest master due to class UCS manager not Found
Thanks a lot Murali
> -Original Message-
> From: Murali Reddy [mailto:murali.re...@citrix.com]
> Sent: Thursday, March 28, 2013 9:07 AM
Thanks a lot Murali
> -Original Message-
> From: Murali Reddy [mailto:murali.re...@citrix.com]
> Sent: Thursday, March 28, 2013 9:07 AM
> To: dev@cloudstack.apache.org; Chip Childers; Kelven Yang
> Cc: cloudstack-...@incubator.apache.org
> Subject: Re: Jetty Failing on
On 28/03/13 9:00 AM, "Rajesh Battala" wrote:
>Jetty is failing to start on latest master building oss.
>Am on the latest master, building oss and starting jetty is failing with
>below error.
>
>Error creating bean with name 'globalLoadBalancingRulesServiceImpl':
>Injection of autowired dependenc
On 28/03/13 9:00 AM, "Kelven Yang" wrote:
>>
>>I was running Non-oss builds, so could not hit this issue. My apologies
>>for the breaking OSS build.
>>
>>Kelven,
>>
>>I am not sure how to fix this issue. If there is no implementing class,
>>why should inject fail? I was under impression it will be
; From: Murali Reddy [mailto:murali.re...@citrix.com]
>> Sent: Thursday, March 28, 2013 8:24 AM
>> To: Chip Childers; Kelven Yang
>> Cc: dev@cloudstack.apache.org; cloudstack-...@incubator.apache.org
>> Subject: Re: Jetty Failing on latest master due to class UCS manager
&g
On 3/27/13 7:53 PM, "Murali Reddy" wrote:
>On 28/03/13 7:42 AM, "Chip Childers" wrote:
>
>>On Wed, Mar 27, 2013 at 04:31:05PM -0700, Kelven Yang wrote:
>>> For UCS issue, I've put a fix in.
>>>
>>> For GSLB, a work around is to run non-OSS build, hopefully this can
>>>unlock
>>> developers te
gt; From: Murali Reddy [mailto:murali.re...@citrix.com]
> Sent: Thursday, March 28, 2013 8:24 AM
> To: Chip Childers; Kelven Yang
> Cc: dev@cloudstack.apache.org; cloudstack-...@incubator.apache.org
> Subject: Re: Jetty Failing on latest master due to class UCS manager not Found
>
> O
On 28/03/13 7:42 AM, "Chip Childers" wrote:
>On Wed, Mar 27, 2013 at 04:31:05PM -0700, Kelven Yang wrote:
>> For UCS issue, I've put a fix in.
>>
>> For GSLB, a work around is to run non-OSS build, hopefully this can
>>unlock
>> developers temporarily on master branch
>
>Good work-around for now
On Wed, Mar 27, 2013 at 04:31:05PM -0700, Kelven Yang wrote:
> For UCS issue, I've put a fix in.
>
> For GSLB, a work around is to run non-OSS build, hopefully this can unlock
> developers temporarily on master branch
Good work-around for now.
Murali - This appears to be something that we *all*
On Wed, Mar 27, 2013 at 04:09:24PM -0700, Kelven Yang wrote:
> 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, i
For UCS issue, I've put a fix in.
For GSLB, a work around is to run non-OSS build, hopefully this can unlock
developers temporarily on master branch
Kelven
On 3/27/13 3:03 PM, "David Nalley" wrote:
>On Wed, Mar 27, 2013 at 5:16 PM, Pranav Saxena
>wrote:
>> Reverting these two commits makes j
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 r
On Wed, Mar 27, 2013 at 5:16 PM, Pranav Saxena 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
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 (
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 ( U
17 matches
Mail list logo
