>
> Here is my first attempt, but I am afraid this may be API breaking:
> https://github.com/apache/jclouds/pull/102
> Let me know what you think.
>
Unfortunately this first step is not even compiling and I don't see how to
make it work, so I declined the pull request for now.
Having looked
Le dim. 21 mars 2021 à 22:16, Jean-Noël Rouvignac (ForgeRock) <
jean-noel.rouvig...@forgerock.com> a écrit :
> Le dim. 21 mars 2021 à 08:13, Andrew Gaul a écrit :
>
>> On Thu, Mar 18, 2021 at 10:39:05AM +0100, Jean-Noėl Rouvignac (ForgeRock)
>> wrote:
>> > I have started looking at
Le dim. 21 mars 2021 à 08:13, Andrew Gaul a écrit :
> On Thu, Mar 18, 2021 at 10:39:05AM +0100, Jean-Noėl Rouvignac (ForgeRock)
> wrote:
> > I have started looking at ListenableFuture.
> > TBH I don't know where to start! A lot of things are public, so I don't
> > think I can change them
On Thu, Mar 18, 2021 at 10:39:05AM +0100, Jean-Noël Rouvignac (ForgeRock) wrote:
> I have started looking at ListenableFuture.
> TBH I don't know where to start! A lot of things are public, so I don't
> think I can change them straight from ListenableFuture to CompletableFuture?
> They are also
On 18.03.21 21:01, Ignasi Barrera wrote:
Glad to see it still works! :)
Mind sharing in the jclouds user list as well, to close the discussion? (You
replied just to me, probably by mistake :D)
On Thu, Mar 18, 2021, 20:54 Fritz Elfert mailto:fr...@fritz-elfert.de>> wrote:
On 18.03.21
> But in general you are right of course. For me in particular, the problem
is: I cannot shade transient dependencies, because all the imports in
jclouds have to be
changed accordingly. Therefore, doing the shading in jclouds ist the only
intermediate way to get the new jclouds into my jenkins
On 18.03.21 09:16, Jean-Noël Rouvignac (ForgeRock) wrote:
The experience with shading in my company is mixed at best.
Yes you go past the classpath issue, but then it becomes a maintenance
nightmare if any vulnerability is detected on the shaded version (true story).
Another problem may be
I have started looking at ListenableFuture.
TBH I don't know where to start! A lot of things are public, so I don't
think I can change them straight from ListenableFuture to CompletableFuture?
They are also often used in conjunction with ListeningExecutorService which
makes the problem worse.
I
On Thu, Mar 18, 2021 at 09:38:19AM +0100, Jean-Noël Rouvignac (ForgeRock) wrote:
> Thanks for highlighting ListenableFuture for a start. Given the size of
> jclouds (about 400kLOC of production code with a stupid wc -l) and my
> inexperience of its codebase, I need help to know where to start. :)
Great!
Thanks for highlighting ListenableFuture for a start. Given the size of
jclouds (about 400kLOC of production code with a stupid wc -l) and my
inexperience of its codebase, I need help to know where to start. :)
I'll see what I can do about it. Do you want to create an issue that
describes
On Thu, Mar 18, 2021 at 09:16:51AM +0100, Jean-Noël Rouvignac (ForgeRock) wrote:
> Side note: I am interested in helping reduce the reliance on guava (as I
> did with xmlbuilder).
> I am not even contemplating getting rid of it given how deeply it is used.
> But we need to start somewhere. Less
On Thu, Mar 18, 2021 at 08:57:19AM +0100, Fritz Elfert wrote:
> Thanks for the link. However, at a first glance, this looks more
> like a tool for warning about undesired class usage. The jenkins
> parent pom already uses the maven-enforcer-plugin which does something
> similar (and more) but at
The experience with shading in my company is mixed at best.
Yes you go past the classpath issue, but then it becomes a maintenance
nightmare if any vulnerability is detected on the shaded version (true
story). Another problem may be that vulnerability scanners may not detect
shaded library and
On 18.03.21 01:21, Andrew Gaul wrote
[...]> Guava versioning is a perennial source of frustration to users and
maintainers. Unfortunately jclouds (and specifically me) made poor
choices by using Guava types in public interfaces. I created some
tooling to address this but did not make much
On Wed, Mar 17, 2021 at 10:39:34PM +0100, Fritz Elfert wrote:
> Nice to see some progress. BUT:
>
> As the maintainer of the jclouds jenkins-plugin, unfortunately I'm now
> facing a problem which I can't solve by myself: The move to newer guice/guava
> breaks compatibility with jenkins (which
Nice to see some progress. BUT:
As the maintainer of the jclouds jenkins-plugin, unfortunately I'm now
facing a problem which I can't solve by myself: The move to newer guice/guava
breaks compatibility with jenkins (which uses guice-4.0/guava-11.0.1).
I tried shading guice and guava in the
The Apache jclouds team is pleased to announce the release of jclouds
2.3.0.
Apache jclouds is an open source multi-cloud toolkit for the Java
platform that gives you the freedom to create applications that are
portable across clouds while giving you full control to use
cloud-specific features.
17 matches
Mail list logo
