Deprecated means: You should not use it.
Personally, I think of deprecated as you need to think about moving away
from this at some point. Hopefully, the deprecation message gives more details
about _when_ that needs to happen. But I generally do not immediately try to
move away from all
As a user of the current org.jclouds.openstack.swift.SwiftClient, I am heavily
confused by the change.
The labs.v1.SwiftApi is marked @Beta.
Deprecated means: You should not use it.
Beta means: You should not use it.
Deprecating a stable API without having a stable replacement is a no go for
I am not worried :) I am confused. In fact I plan to have a production version
of our software talking to os ceph via jclouds swift. But I don't know which
API to use. The deprecated one, or the beta one. I usually expect to find a
clear answer in code. and after beta and deprecation
@CodingFabian We're well aware that the old SwiftClient has been around for a
long time and is heavily used. I also understand it's a bit confusing. I think
the source of the confusion is that we're being very cautious (overly
cautious?) about this transition.
We're playing it cautious by
I did better Beta documentation in
https://github.com/jclouds/jclouds-labs-openstack/pull/93
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39514233
@ntolia By definition a HP custom TempURL implementation wouldn't belong in any
Swift API. It should be in the HP provider. I've contacted someone at HP to see
if they'll be able to dedicate someone to jclouds. It sounds like they are and
hopefully we'll know more next week.
---
Reply to this
Closed #237.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237
Merged to master and 1.7.x
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39514924
jclouds-pull-requests #728 SUCCESS
Checkstyle is also
[clean](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/728/)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39293399
I discovered that when you organize imports (command-O) in Eclipse, if you
reference a class by name in the JavaDocs it adds the import. I will make sure
to run Checkstyle in Eclipse before submitting PRs in the future.
@demobox Can we please get this merged and backported into the 1.7.x
[jclouds-pull-requests
#729](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/729/) UNSTABLE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39358086
[jclouds-java-7-pull-requests
#1199](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1199/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39358546
[jclouds » jclouds
#990](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/990/) SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
Can we please get this merged and backported into the 1.7.x branch?
Do you want to squash this down first, or do we want two commits here?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39381258
jclouds-pull-requests #729 UNSTABLE
Unrelated [test
failure](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/org.apache.jclouds$jclouds-compute/729/testReport/junit/org.jclouds.compute.util/ConcurrentOpenSocketFinderTest/testChecksSocketsConcurrently/),
by the way
---
Reply to this
[jclouds-java-7-pull-requests
#1200](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1200/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39388942
@jdaggett Does this need to be updated prior to the 1.7.2 release? We should
really get this into 1.7.2.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39219519
[jclouds » jclouds
#982](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/982/) SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-pull-requests
#723](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/723/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39243332
Do we know what's missing in the new implementation (in jclouds-labs-openstack)
that is present in the old implementation? In other words, what's the effort
required to have feature parity between the new implementation and the old one?
---
Reply to this email directly or view it on GitHub:
I am going to make all references state ...will be removed in jclouds 1.8.
Any objections @andrewgaul @everett-toews ?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39243863
[jclouds-java-7-pull-requests
#1193](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1193/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39244368
[minor] I might use replaced by instead of replaced with, but fine as-is.
Squash'n'rebase still to come, I guess?
Looks good to me, but I think @everett-toews or @zack-shoylev will be better
judges here.
One [Checkstyle
[jclouds-pull-requests
#726](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/726/) UNSTABLE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39277812
[jclouds-java-7-pull-requests
#1196](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1196/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39278216
jclouds-pull-requests #726 UNSTABLE
Still the same [Checkstyle
violation](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/726/org.apache.jclouds.api$swift/violations/)
---
Reply to this email directly or view it on GitHub:
[jclouds-pull-requests
#727](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/727/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39278971
[jclouds-java-7-pull-requests
#1197](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1197/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39279088
[jclouds-pull-requests
#728](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/728/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39279405
[jclouds-java-7-pull-requests
#1198](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1198/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39279900
[jclouds » jclouds
#987](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/987/) UNSTABLE
Looks like there's a problem with this pull request
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
31 matches
Mail list logo
