Thanks Rafael for sharing and sending the PR, I think that should fix the
problem.
Regards.
From: Rafael Weingärtner
Sent: Wednesday, November 15, 2017 8:33:08 PM
To: dev@cloudstack.apache.org
Subject: Re: jetty simulator problem
Now travis started presenting
t,address=8787,server=y,suspend=n"
>>
>>
>> Rafael - you may review the Travis build/run scripts in `tools/travis`.
>>
>>
>> Regards.
>>
>>
>> From: Daan Hoogland
>> Sent: Wednesday, November 15, 2017 12:
fael - you may review the Travis build/run scripts in `tools/travis`.
>
>
> Regards.
>
> ____
> From: Daan Hoogland
> Sent: Wednesday, November 15, 2017 12:50:29 PM
> To: dev
> Subject: Re: jetty simulator problem
>
> @Rohit, all of this is with -Dsi
s/travis`.
Regards.
From: Daan Hoogland
Sent: Wednesday, November 15, 2017 12:50:29 PM
To: dev
Subject: Re: jetty simulator problem
@Rohit, all of this is with -Dsimulator. It is probably due to one of my
many bad habits but I have this on fedora 26, macos 10.13 and macos 10.11
On
ave not caught
> any issues ib Travis or Trillian yet. Keep me posted if you still face the
> issues.
>
> Regards.
>
> From: Rafael Weingärtner
> Sent: Tuesday, November 14, 2017 5:56:03 PM
> To: dev@cloudstack.apache.org
> Subject:
nt: Tuesday, November 14, 2017 5:56:03 PM
> To: dev@cloudstack.apache.org
> Subject: Re: jetty simulator problem
>
> It works without removing annotation because they are not being processed
> (@component). That is why when you deleted the beans declaration in the XML
> Spring started complaining abou
: Re: jetty simulator problem
It works without removing annotation because they are not being processed
(@component). That is why when you deleted the beans declaration in the XML
Spring started complaining about those beans. So, if they are not being
used, we can simply remove them.
On Tue, Nov
It works without removing annotation because they are not being processed
(@component). That is why when you deleted the beans declaration in the XML
Spring started complaining about those beans. So, if they are not being
used, we can simply remove them.
On Tue, Nov 14, 2017 at 10:09 AM, Daan Hoog
On Tue, Nov 14, 2017 at 12:00 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:
> That depends-on configuration is not needed when attributes are annotated
> with @inject or @Autowired, spring builds automatically de dependency
> hierarchy. Even though the removal of them did not seem t
That depends-on configuration is not needed when attributes are annotated
with @inject or @Autowired, spring builds automatically de dependency
hierarchy. Even though the removal of them did not seem to be necessary,
their use is also not necessary. The issue seems to be related to
application cont
it actually already works with only the depends-on attributes in the xml
removed but it all makes sense.
On Tue, Nov 14, 2017 at 1:59 AM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:
> I removed some spring configurations that were not making sense to me.
> After that, everything star
I removed some spring configurations that were not making sense to me.
After that, everything started working. I committed these changes at
https://github.com/rafaelweingartner/cloudstack/tree/daanTestSimulator
Could you test it? If it works I can open a PR.
On Mon, Nov 13, 2017 at 5:33 PM, Daan
trying with only the depends-on lines removed now
On Mon, Nov 13, 2017 at 8:30 PM, Daan Hoogland
wrote:
> from maven:
> mvn -pl client jetty:run -Dsimulator
>
> On Mon, Nov 13, 2017 at 8:16 PM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
>> The error changed! That is good... It
from maven:
mvn -pl client jetty:run -Dsimulator
On Mon, Nov 13, 2017 at 8:16 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:
> The error changed! That is good... It is a misconfiguration with
> dependencies between modules.
> How are you running the simulator?
>
> On Mon, Nov 13, 20
The error changed! That is good... It is a misconfiguration with
dependencies between modules.
How are you running the simulator?
On Mon, Nov 13, 2017 at 5:13 PM, Daan Hoogland
wrote:
> didn't work:( trying with only some parts removed now
>
> Caused by: org.springframework.beans.factory.
> NoSu
didn't work:( trying with only some parts removed now
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException:
No qualifying bean of type
'org.apache.cloudstack.engine.subsystem.api.storage.SnapshotService'
available: expected at least 1 bean which qualifies as autowire candidat
These beans declarations do not make much sense. They are declared twice,
once in the XML (spring-engine-storage-snapshot-core-context.xml), and the
second declaration is executed through the use of annotations (@Component)
in those classes. This exception is happening because there is a
configurat
17 matches
Mail list logo
