You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jclouds.apache.org by Andrew Gaul <ga...@apache.org> on 2021/02/28 14:40:05 UTC

[DISCUSS] Release Apache jclouds 2.3.0 RC1

This thread is for discussion of the first release candidate for
Apache jclouds 2.3.0.

Please use this thread for discussion of issues uncovered in the RC,
questions you may have about the RC, etc.

If you want to help to validate the release, you'll find a set of
scripts and the corresponding instructions here:
https://cwiki.apache.org/confluence/display/JCLOUDS/Validate+a+Release

You can also go run live tests for your preferred providers and post
the results here, or use the projects in the jclouds-examples repo,
such as the "compute-basics" to rapidly smoke test the providers you
are interested in:
https://github.com/jclouds/jclouds-examples

-- 
Andrew Gaul
http://gaul.org/

Re: [DISCUSS] Release Apache jclouds 2.3.0 RC1

Posted by Ignasi Barrera <na...@apache.org>.
I've done a small change to the javadoc publish script and uploaded the
javadocs.

@gaul, mind checking if you have the snapshot change locally already and
push it?

On Sun, Mar 7, 2021, 17:03 Ignasi Barrera <na...@apache.org> wrote:

> I'm not very familiar with the javadoc thing, but I'll try to have a look
> at it during the week.
>
> Regarding the next snapshot, the release script should have already bumped
> it and the status of the local master branch where you ran the release
> should already have those commits.
>
> On Sun, Mar 7, 2021 at 2:58 PM Andrew Gaul <ga...@apache.org> wrote:
>
>> On Sat, Mar 06, 2021 at 10:45:14PM +0900, Andrew Gaul wrote:
>> > I finished most of the release process but am having trouble deploying
>> > the Javadoc:
>> >
>> > $ ./deploy-javadoc.sh 2.3.0
>> > ...
>> > [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:aggregate (default-cli)
>> on project jclouds: An error has occurred in JavaDocs report generation:
>> > [ERROR] Exit code: 1 -
>> /home/gaul/jclouds/core/src/main/java/org/jclouds/predicates/InetSocketAddressConnect.java:27:
>> error: cannot find symbol
>> > [ERROR] import javax.annotation.Resource;
>> > [ERROR]                        ^
>> > [ERROR]   symbol:   class Resource
>> > [ERROR]   location: package javax.annotation
>> > [ERROR]
>> >
>> /home/gaul/jclouds/core/src/main/java/org/jclouds/logging/internal/Wire.java:27:
>> error: cannot find symbolo
>> >
>> > Too late in JST time zone to keep working on this.  @nacx could you look
>> > into this?
>>
>> I could not figure this out and it seems that bumping the version has
>> problems too:
>>
>> $ mvn versions:set -DnewVersion=2.4.0-SNAPSHOT
>> ...
>> [ERROR] Failed to execute goal
>> org.codehaus.mojo:versions-maven-plugin:2.7:set (default-cli) on project
>> jclouds: Project version is inherited from parent. -> [Help 1]
>>
>> Any ideas?
>>
>> --
>> Andrew Gaul
>> http://gaul.org/
>>
>

Re: [DISCUSS] Release Apache jclouds 2.3.0 RC1

Posted by Ignasi Barrera <na...@apache.org>.
I'm not very familiar with the javadoc thing, but I'll try to have a look
at it during the week.

Regarding the next snapshot, the release script should have already bumped
it and the status of the local master branch where you ran the release
should already have those commits.

On Sun, Mar 7, 2021 at 2:58 PM Andrew Gaul <ga...@apache.org> wrote:

> On Sat, Mar 06, 2021 at 10:45:14PM +0900, Andrew Gaul wrote:
> > I finished most of the release process but am having trouble deploying
> > the Javadoc:
> >
> > $ ./deploy-javadoc.sh 2.3.0
> > ...
> > [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:aggregate (default-cli)
> on project jclouds: An error has occurred in JavaDocs report generation:
> > [ERROR] Exit code: 1 -
> /home/gaul/jclouds/core/src/main/java/org/jclouds/predicates/InetSocketAddressConnect.java:27:
> error: cannot find symbol
> > [ERROR] import javax.annotation.Resource;
> > [ERROR]                        ^
> > [ERROR]   symbol:   class Resource
> > [ERROR]   location: package javax.annotation
> > [ERROR]
> >
> /home/gaul/jclouds/core/src/main/java/org/jclouds/logging/internal/Wire.java:27:
> error: cannot find symbolo
> >
> > Too late in JST time zone to keep working on this.  @nacx could you look
> > into this?
>
> I could not figure this out and it seems that bumping the version has
> problems too:
>
> $ mvn versions:set -DnewVersion=2.4.0-SNAPSHOT
> ...
> [ERROR] Failed to execute goal
> org.codehaus.mojo:versions-maven-plugin:2.7:set (default-cli) on project
> jclouds: Project version is inherited from parent. -> [Help 1]
>
> Any ideas?
>
> --
> Andrew Gaul
> http://gaul.org/
>

Re: [DISCUSS] Release Apache jclouds 2.3.0 RC1

Posted by Andrew Gaul <ga...@apache.org>.
On Sat, Mar 06, 2021 at 10:45:14PM +0900, Andrew Gaul wrote:
> I finished most of the release process but am having trouble deploying
> the Javadoc:
> 
> $ ./deploy-javadoc.sh 2.3.0
> ...
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:aggregate (default-cli) on project jclouds: An error has occurred in JavaDocs report generation: 
> [ERROR] Exit code: 1 - /home/gaul/jclouds/core/src/main/java/org/jclouds/predicates/InetSocketAddressConnect.java:27: error: cannot find symbol
> [ERROR] import javax.annotation.Resource;
> [ERROR]                        ^
> [ERROR]   symbol:   class Resource
> [ERROR]   location: package javax.annotation
> [ERROR]
> /home/gaul/jclouds/core/src/main/java/org/jclouds/logging/internal/Wire.java:27: error: cannot find symbolo
> 
> Too late in JST time zone to keep working on this.  @nacx could you look
> into this?

I could not figure this out and it seems that bumping the version has
problems too:

$ mvn versions:set -DnewVersion=2.4.0-SNAPSHOT
...
[ERROR] Failed to execute goal org.codehaus.mojo:versions-maven-plugin:2.7:set (default-cli) on project jclouds: Project version is inherited from parent. -> [Help 1]

Any ideas?

-- 
Andrew Gaul
http://gaul.org/

Re: [DISCUSS] Release Apache jclouds 2.3.0 RC1

Posted by Andrew Gaul <ga...@apache.org>.
On Sun, Feb 28, 2021 at 11:40:05PM +0900, Andrew Gaul wrote:
> This thread is for discussion of the first release candidate for
> Apache jclouds 2.3.0.
> 
> Please use this thread for discussion of issues uncovered in the RC,
> questions you may have about the RC, etc.
> 
> If you want to help to validate the release, you'll find a set of
> scripts and the corresponding instructions here:
> https://cwiki.apache.org/confluence/display/JCLOUDS/Validate+a+Release
> 
> You can also go run live tests for your preferred providers and post
> the results here, or use the projects in the jclouds-examples repo,
> such as the "compute-basics" to rapidly smoke test the providers you
> are interested in:
> https://github.com/jclouds/jclouds-examples

I finished most of the release process but am having trouble deploying
the Javadoc:

$ ./deploy-javadoc.sh 2.3.0
...
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:aggregate (default-cli) on project jclouds: An error has occurred in JavaDocs report generation: 
[ERROR] Exit code: 1 - /home/gaul/jclouds/core/src/main/java/org/jclouds/predicates/InetSocketAddressConnect.java:27: error: cannot find symbol
[ERROR] import javax.annotation.Resource;
[ERROR]                        ^
[ERROR]   symbol:   class Resource
[ERROR]   location: package javax.annotation
[ERROR]
/home/gaul/jclouds/core/src/main/java/org/jclouds/logging/internal/Wire.java:27: error: cannot find symbolo

Too late in JST time zone to keep working on this.  @nacx could you look
into this?

-- 
Andrew Gaul
http://gaul.org/

Re: [DISCUSS] Release Apache jclouds 2.3.0 RC1

Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
My bad, you are right: I thought I was PMC member for jclouds ;)

Sorry about that, it’s +1 (non binding)

Regards
JB

> Le 2 mars 2021 à 13:28, Andrew Phillips <ap...@qrmedia.com> a écrit :
> 
>> +1 (binding)
> 
> @Jean-Baptiste: as a technicality, I think yours would be a non-binding vote - my understanding was that only votes by PMC members are binding [1, 2]?
> 
> Thank you of course for taking the time to test the RC!
> 
> ap
> 
> [1] http://www.apache.org/legal/release-policy.html#:~:text=For%20a%20release%20vote%20to,by%20PMC%20members%20are%20binding.
> [2] https://projects.apache.org/committee.html?jclouds


Re: [DISCUSS] Release Apache jclouds 2.3.0 RC1

Posted by Andrew Phillips <ap...@qrmedia.com>.
> +1 (binding)

@Jean-Baptiste: as a technicality, I think yours would be a non-binding 
vote - my understanding was that only votes by PMC members are binding 
[1, 2]?

Thank you of course for taking the time to test the RC!

ap

[1] 
http://www.apache.org/legal/release-policy.html#:~:text=For%20a%20release%20vote%20to,by%20PMC%20members%20are%20binding.
[2] https://projects.apache.org/committee.html?jclouds

Re: [DISCUSS] Release Apache jclouds 2.3.0 RC1

Posted by Andrew Gaul <ga...@apache.org>.
On Sun, Feb 28, 2021 at 11:40:05PM +0900, Andrew Gaul wrote:
> This thread is for discussion of the first release candidate for
> Apache jclouds 2.3.0.
> 
> Please use this thread for discussion of issues uncovered in the RC,
> questions you may have about the RC, etc.
> 
> If you want to help to validate the release, you'll find a set of
> scripts and the corresponding instructions here:
> https://cwiki.apache.org/confluence/display/JCLOUDS/Validate+a+Release
> 
> You can also go run live tests for your preferred providers and post
> the results here, or use the projects in the jclouds-examples repo,
> such as the "compute-basics" to rapidly smoke test the providers you
> are interested in:
> https://github.com/jclouds/jclouds-examples

Successfully ran blobstore integration tests with similar failures to  
2.2.1.  Providers include aws-s3, azureblob, b2, filesystem,
google-cloud-storage, rackspace-cloudfiles-us, s3 (dreamobjects), and
transient.

-- 
Andrew Gaul
http://gaul.org/