My vote is 2.6.0-SNAPSHOT and 2.6.0-rc1, in case we need a bug fix release... Being consistent with snapshot versions lets maven users update to the new nightly without any config file changes. On Nov 6, 2013 6:51 PM, "Matthew Dempsky" <[email protected]> wrote:
> Hm, actually I could use some guidance here from external people who might > be affected by this: > > Should the release be "2.6-rc1", "2.6.0-rc1", "2.6.0-RC1", ...? > > Should snapshots be pushed as "2.6-SNAPSHOT", "2.6.0-SNAPSHOT", both, ...? > > It looks like Maven parses "2.6" and "2.6.0" identically for version > comparisons, but perhaps it still makes a difference for locating > dependencies in Maven Central? > > > On Wed, Nov 6, 2013 at 4:31 PM, Matthew Dempsky <[email protected]>wrote: > >> PEBKAC; I tried deploying to the production repo without GPG signatures. >> I've deployed again to the snapshot repo using your script, and it looks >> better? FYI, I pushed this snapshot as "2.6-SNAPSHOT", based on reading >> that Maven doesn't care about the difference. >> >> Please give that a try, and then I'll push as 2.6-rc1 to the production >> repo. >> >> >> On Wed, Nov 6, 2013 at 4:00 PM, Matthew Dempsky <[email protected]>wrote: >> >>> Hm, I just tried pushing another 2.6.0-SNAPSHOT, this time using your >>> patched scripts, but I got a Maven error: >>> >>> /usr/bin/mvn >>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file >>> -Dfile=./poms/gwt/pom.xml -Durl= >>> https://oss.sonatype.org/service/local/staging/deploy/maven2/-DrepositoryId=sonatype >>> -DpomFile=./poms/gwt/pom.xml -DuniqueVersion=false >>> [INFO] Scanning for projects... >>> [INFO] >>> >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Building Maven Stub Project (No POM) 1 >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] >>> [INFO] --- maven-deploy-plugin:2.7:deploy-file (default-cli) @ >>> standalone-pom --- >>> Downloading: >>> https://oss.sonatype.org/service/local/staging/deploy/maven2/com/google/gwt/gwt/2.6.0-SNAPSHOT/maven-metadata.xml >>> Nov 06, 2013 3:47:50 PM >>> org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme >>> INFO: basic authentication scheme selected >>> [WARNING] Could not transfer metadata >>> com.google.gwt:gwt:2.6.0-SNAPSHOT/maven-metadata.xml from/to sonatype ( >>> https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed >>> to transfer file: >>> https://oss.sonatype.org/service/local/staging/deploy/maven2//com/google/gwt/gwt/2.6.0-SNAPSHOT/maven-metadata.xml. >>> Return code is: 400 >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] BUILD FAILURE >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Total time: 4.519s >>> [INFO] Finished at: Wed Nov 06 15:47:50 PST 2013 >>> [INFO] Final Memory: 9M/79M >>> [INFO] >>> ------------------------------------------------------------------------ >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default-cli) >>> on project standalone-pom: Failed to retrieve remote metadata >>> com.google.gwt:gwt:2.6.0-SNAPSHOT/maven-metadata.xml: Could not transfer >>> metadata com.google.gwt:gwt:2.6.0-SNAPSHOT/maven-metadata.xml from/to >>> sonatype (https://oss.sonatype.org/service/local/staging/deploy/maven2/): >>> Failed to transfer file: >>> https://oss.sonatype.org/service/local/staging/deploy/maven2//com/google/gwt/gwt/2.6.0-SNAPSHOT/maven-metadata.xml. >>> Return code is: 400 -> [Help 1] >>> [ERROR] >>> [ERROR] To see the full stack trace of the errors, re-run Maven with the >>> -e switch. >>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>> [ERROR] >>> [ERROR] For more information about the errors and possible solutions, >>> please read the following articles: >>> [ERROR] [Help 1] >>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException >>> GPG passphrase not specified; will attempt to deploy files without >>> signing >>> /usr/bin/mvn >>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file >>> -Dfile=/tmp/random-dir-29784225802671812248/gwt-2.6-rc1/gwt-dev.jar -Durl= >>> https://oss.sonatype.org/service/local/staging/deploy/maven2/-DrepositoryId=sonatype >>> -DpomFile=./poms/gwt/gwt-dev/pom.xml >>> -Djavadoc=/tmp/random-dir-29784225802671812248/gwt-javadoc.jar >>> -Dsources=/tmp/tmp-jar-expand-dir-6286-dev/gwt-dev-sources.jar >>> -DuniqueVersion=false >>> [INFO] Scanning for projects... >>> [INFO] >>> >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Building Maven Stub Project (No POM) 1 >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] >>> [INFO] --- maven-deploy-plugin:2.7:deploy-file (default-cli) @ >>> standalone-pom --- >>> Downloading: >>> https://oss.sonatype.org/service/local/staging/deploy/maven2/com/google/gwt/gwt-dev/2.6.0-SNAPSHOT/maven-metadata.xml >>> Nov 06, 2013 3:47:54 PM >>> org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme >>> INFO: basic authentication scheme selected >>> [WARNING] Could not transfer metadata >>> com.google.gwt:gwt-dev:2.6.0-SNAPSHOT/maven-metadata.xml from/to sonatype ( >>> https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed >>> to transfer file: >>> https://oss.sonatype.org/service/local/staging/deploy/maven2//com/google/gwt/gwt-dev/2.6.0-SNAPSHOT/maven-metadata.xml. >>> Return code is: 400 >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] BUILD FAILURE >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Total time: 2.126s >>> [INFO] Finished at: Wed Nov 06 15:47:54 PST 2013 >>> [INFO] Final Memory: 8M/112M >>> [INFO] >>> ------------------------------------------------------------------------ >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default-cli) >>> on project standalone-pom: Failed to retrieve remote metadata >>> com.google.gwt:gwt-dev:2.6.0-SNAPSHOT/maven-metadata.xml: Could not >>> transfer metadata com.google.gwt:gwt-dev:2.6.0-SNAPSHOT/maven-metadata.xml >>> from/to sonatype ( >>> https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed >>> to transfer file: >>> https://oss.sonatype.org/service/local/staging/deploy/maven2//com/google/gwt/gwt-dev/2.6.0-SNAPSHOT/maven-metadata.xml. >>> Return code is: 400 -> [Help 1] >>> [ERROR] >>> [ERROR] To see the full stack trace of the errors, re-run Maven with the >>> -e switch. >>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>> [ERROR] >>> [ERROR] For more information about the errors and possible solutions, >>> please read the following articles: >>> [ERROR] [Help 1] >>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException >>> Error while deploying, ignore errors? (y/N): >>> >>> I'm going to root cause what's going on, but maybe you have an idea >>> what's going on? >>> >>> >>> On Wed, Nov 6, 2013 at 1:49 PM, Colin Alworth <[email protected]>wrote: >>> >>>> Just moved to eclipse to verify a possible issue with the snapshot >>>> (nope, bug was in my code), and eclipse seems to do okay with finding each >>>> artifact in its own snapshot. >>>> >>>> Can you ping the list when you push a new set of snapshots? >>>> >>>> -Colin >>>> On Nov 5, 2013 7:55 PM, "Matthew Dempsky" <[email protected]> wrote: >>>> >>>>> Thanks for testing, Colin! I'll try another push tonight using your >>>>> scripts. >>>>> >>>>> >>>>> On Tue, Nov 5, 2013 at 5:14 PM, Colin Alworth <[email protected]>wrote: >>>>> >>>>>> It looks like while I can get maven from the command line to get >>>>>> along with that repo, IntelliJ isn't having it - it is getting confused >>>>>> by >>>>>> the fact that the latest gwt-user snapshot 2.6.0-20131105.081128-3 only >>>>>> has >>>>>> a sources jar and a pom, no actual jar with compiled code in it. The -1 >>>>>> jar >>>>>> is only the compiled code, the -2 is only javadoc, and the -3 is, as >>>>>> mentioned, sources. >>>>>> >>>>>> The maven/push-gwt.sh patch I put up should resolve this - for now >>>>>> this setup is good for maven builds, but not for IDEs that expect to have >>>>>> sources and javadocs available in the 'same' snapshot. >>>>>> >>>>>> >>>>>> On Tuesday, November 5, 2013 2:18:30 AM UTC-6, Matthew Dempsky wrote: >>>>>> >>>>>>> In the mean time though, I think I successfully pushed >>>>>>> 2.6.0-SNAPSHOT to https://oss.sonatype.org/ >>>>>>> content/repositories/google-snapshots/. >>>>>>> >>>>>>> >>>>>>> On Tue, Nov 5, 2013 at 12:04 AM, Matthew Dempsky <[email protected] >>>>>>> > wrote: >>>>>>> >>>>>>>> As promised, I created the "release/2.6" branch for tracking >>>>>>>> development towards 2.6. At this point, development can continue on >>>>>>>> master >>>>>>>> towards the next release. If you think a change should be made for >>>>>>>> 2.6, >>>>>>>> please propose it against master, and then notify me to cherry pick it >>>>>>>> onto >>>>>>>> release/2.6. >>>>>>>> >>>>>>>> Setting up the 2.6 release branch took longer than expected due to >>>>>>>> some last minute changes and technical issues. I plan to finish >>>>>>>> preparing >>>>>>>> the 2.6rc1 snapshot tomorrow morning, and push them out. I'll send an >>>>>>>> announcement when that's ready. Thanks for your patience and sorry >>>>>>>> for the >>>>>>>> slight delay. >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Nov 4, 2013 at 1:58 PM, Matthew Dempsky <[email protected] >>>>>>>> > wrote: >>>>>>>> >>>>>>>>> As a reminder, I'm going to create the GWT 2.6 branch later today >>>>>>>>> and prepare a 2.6rc1 snapshot. There's still some time to propose and >>>>>>>>> submit patches, but it's down to hours remaining now. Don't fret if >>>>>>>>> you >>>>>>>>> miss the deadline: there will be more releases in the future! >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> -- >>>>>> http://groups.google.com/group/Google-Web-Toolkit-Contributors >>>>>> --- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "GWT Contributors" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to >>>>>> [email protected]. >>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>> >>>>> >>>>> -- >>>>> http://groups.google.com/group/Google-Web-Toolkit-Contributors >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "GWT Contributors" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to >>>>> [email protected]. >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>> -- >>>> http://groups.google.com/group/Google-Web-Toolkit-Contributors >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "GWT Contributors" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to >>>> [email protected]. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>> >>> >> > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > --- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
