Subject: Re: conflicting dependencies between CloudStack and Whirr
Alright, I looked into this and it will take a bit more work to
switch to Jackson.
The snag I hit was how we serialize commands for the agents. We use a
customer typeadatper in gson to produce a format like { org.MyClass
@cloudstack.apache.org
Subject: Re: conflicting dependencies between CloudStack and Whirr
Alright, I looked into this and it will take a bit more work to
switch to Jackson.
The snag I hit was how we serialize commands for the agents. We
use a
customer typeadatper in gson to produce a format like
.
--Alex
-Original Message-
From: Darren Shepherd [mailto:darren.s.sheph...@gmail.com]
Sent: Thursday, September 19, 2013 1:33 PM
To: dev@cloudstack.apache.org
Subject: Re: conflicting dependencies between CloudStack and Whirr
Alright, I looked into this and it will take a bit more
[mailto:savu.and...@gmail.com]
Sent: Wednesday, September 18, 2013 10:53 AM
To: d...@whirr.apache.org
Cc: dev@cloudstack.apache.org
Subject: Re: conflicting dependencies between CloudStack and Whirr
It's easy to usr jclouds and whirr inside an OSGi container - just
add
the
feature url
-Original Message-
From: Darren Shepherd [mailto:darren.s.sheph...@gmail.com]
Sent: Thursday, September 19, 2013 1:33 PM
To: dev@cloudstack.apache.org
Subject: Re: conflicting dependencies between CloudStack and Whirr
Alright, I looked into this and it will take a bit more work
: Thursday, September 19, 2013 1:33 PM
To: dev@cloudstack.apache.org
Subject: Re: conflicting dependencies between CloudStack and Whirr
Alright, I looked into this and it will take a bit more work to switch to
Jackson.
The snag I hit was how we serialize commands for the agents. We use
18, 2013 10:53 AM
To: d...@whirr.apache.org
Cc: dev@cloudstack.apache.org
Subject: Re: conflicting dependencies between CloudStack and Whirr
It's easy to usr jclouds and whirr inside an OSGi container - just add
the
feature url. Bonus: you can also use jclouds shell interface (part
...@gmail.com]
Sent: Thursday, September 19, 2013 1:33 PM
To: dev@cloudstack.apache.org
Subject: Re: conflicting dependencies between CloudStack and Whirr
Alright, I looked into this and it will take a bit more work to switch to
Jackson.
The snag I hit was how we serialize commands
[mailto:darren.s.sheph...@gmail.com]
Sent: Thursday, September 19, 2013 1:33 PM
To: dev@cloudstack.apache.org
Subject: Re: conflicting dependencies between CloudStack and Whirr
Alright, I looked into this and it will take a bit more work to switch to
Jackson.
The snag I hit was how we serialize
-Original Message-
From: Darren Shepherd [mailto:darren.s.sheph...@gmail.com]
Sent: Thursday, September 19, 2013 1:33 PM
To: dev@cloudstack.apache.org
Subject: Re: conflicting dependencies between CloudStack and Whirr
Alright, I looked into this and it will take a bit more work
Good question. The gson dependency in Whirr is coming from jclouds, and
jclouds is very particular about its gson dependencies. Any possibility of
using isolated classloaders in some way?
A.
On Tue, Sep 17, 2013 at 7:14 PM, Han,Meng meng...@ufl.edu wrote:
Dear all,
I am adding an API to
You know what would be really swell is to just switch to jackson. The gson
we use is antiquated. I have no idea what the impact of moving to a modern
version would be. Jackson, IMO, is a far better framework that has a lot
of momentum. Additionally it allows you to use JAXB annotations so that
Message-
From: Andrei Savu [mailto:savu.and...@gmail.com]
Sent: Wednesday, September 18, 2013 10:53 AM
To: d...@whirr.apache.org
Cc: dev@cloudstack.apache.org
Subject: Re: conflicting dependencies between CloudStack and Whirr
It's easy to usr jclouds and whirr inside an OSGi container - just
I almost faced that there is no choice but to go for it for VMware
recently, we found that VMware vSphere 5.1 SDK we are currently using has
some backwards compatibility issue with VMware vSphere 4.x systems.
Therefore it makes a valid business case that CloudStack may have to
support different
Cc: dev@cloudstack.apache.org
Subject: Re: conflicting dependencies between CloudStack and Whirr
It's easy to usr jclouds and whirr inside an OSGi container - just add
the
feature url. Bonus: you can also use jclouds shell interface (part of
jclouds cli).
Another option
15 matches
Mail list logo
