[gwt-contrib] Re: Publish nighly snapshots of GWT builds to Maven

[Łukasz Jąder]

+1 all the way. 
Checking out SNAPSHOT version would be fun an could help find more issues.

W dniu czwartek, 19 września 2013 16:29:18 UTC+2 użytkownik Johannes Barop 
napisał:
>
> Hi,
>
> what do you think of publishing nightly builds of GWT to a Maven 
> repository? This would save users which want to try/work with 
> latest/unreleased features of building it on their own.
>
> A repository exists already. But I don't know who has write access to it
>
> https://oss.sonatype.org/content/repositories/google-snapshots/com/google/gwt/
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Re: Publish nighly snapshots of GWT builds to Maven

[Ray Cromwell]

Matthew,
  Is there an easy way to make Jenkins push out a snapshot after a
successful build?



On Sat, Sep 21, 2013 at 5:31 AM, Łukasz Jąder  wrote:

> +1 all the way.
> Checking out SNAPSHOT version would be fun an could help find more issues.
>
> W dniu czwartek, 19 września 2013 16:29:18 UTC+2 użytkownik Johannes Barop
> napisał:
>
>> Hi,
>>
>> what do you think of publishing nightly builds of GWT to a Maven
>> repository? This would save users which want to try/work with
>> latest/unreleased features of building it on their own.
>>
>> A repository exists already. But I don't know who has write access to it
>> https://oss.sonatype.org/**content/repositories/google-**
>> snapshots/com/google/gwt/
>>
>  --
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Re: Publish nighly snapshots of GWT builds to Maven

[Thomas Broyer]

It should be relatively easy with the existing shell scripts; the major pain 
point would be securing the credentials. I think Sonatype can do "app 
passwords".
I can have a look at the scripts if needs be, as I think they've only been 
tested for local deployment or staging, and only for releases (not snapshots)

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Re: Publish nighly snapshots of GWT builds to Maven

[Colin Alworth]

I've just put up a patch that seems to resolve a current issue in deploying 
snapshots to a maven repository: https://gwt-review.googlesource.com/5192

The basis of the problem requiring this patch is that maven (at least maven 
3, possibly not maven 2) expects unique snapshots, and that each call to 
deploy:deploy-file or sign:sign-and-deploy uploads its artifact as a 
standalone object - when we call deploy three times (jar, sources, 
javadoc), the last one in is treated as the 'newest'. This doesn't happen 
for releases, as there can only be one release, while there can be several 
snapshots for a version.

As noted, this patch does not resolve the issue locally - its my 
understanding that install:install-file would need to be used to make this 
work our locally, or else I'm just doing it wrong. The issue appears to be 
related to metadata not being updated correctly, but I didn't debug too 
extensively. I think that we can safely ignore local snapshots for the time 
being anyway - first, they didn't work before this patch, and second a user 
can either build from a snapshot server or can assign a non-snapshot 
version when installing locally and run it multiple times (pushing a 
non-snapshot version to a remote server would result in clients caching 
that result and not downloading it again).

I'd appreciate any testing of this so that we can see about starting to put 
out snapshot builds on sonatype going forward.

On Sunday, September 22, 2013 8:53:16 AM UTC-5, Thomas Broyer wrote:
>
> It should be relatively easy with the existing shell scripts; the major 
> pain point would be securing the credentials. I think Sonatype can do "app 
> passwords".
> I can have a look at the scripts if needs be, as I think they've only been 
> tested for local deployment or staging, and only for releases (not 
> snapshots)

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Re: Publish nighly snapshots of GWT builds to Maven

[Seamus McMorrow]

Hi, 

Is there any update on deploying snapshots, so the greater GWT community 
can contribute to testing newer releases more easily.
I would definitely like to checkout some of the expirimental incremental 
compiler features that are currently being landed for the next 2.7 release 
in the summer sometime.
(I am currently building from source, etc)





On Monday, 28 October 2013 05:03:07 UTC, Colin Alworth wrote:
>
> I've just put up a patch that seems to resolve a current issue in 
> deploying snapshots to a maven repository: 
> https://gwt-review.googlesource.com/5192
>
> The basis of the problem requiring this patch is that maven (at least 
> maven 3, possibly not maven 2) expects unique snapshots, and that each call 
> to deploy:deploy-file or sign:sign-and-deploy uploads its artifact as a 
> standalone object - when we call deploy three times (jar, sources, 
> javadoc), the last one in is treated as the 'newest'. This doesn't happen 
> for releases, as there can only be one release, while there can be several 
> snapshots for a version.
>
> As noted, this patch does not resolve the issue locally - its my 
> understanding that install:install-file would need to be used to make this 
> work our locally, or else I'm just doing it wrong. The issue appears to be 
> related to metadata not being updated correctly, but I didn't debug too 
> extensively. I think that we can safely ignore local snapshots for the time 
> being anyway - first, they didn't work before this patch, and second a user 
> can either build from a snapshot server or can assign a non-snapshot 
> version when installing locally and run it multiple times (pushing a 
> non-snapshot version to a remote server would result in clients caching 
> that result and not downloading it again).
>
> I'd appreciate any testing of this so that we can see about starting to 
> put out snapshot builds on sonatype going forward.
>
> On Sunday, September 22, 2013 8:53:16 AM UTC-5, Thomas Broyer wrote:
>>
>> It should be relatively easy with the existing shell scripts; the major 
>> pain point would be securing the credentials. I think Sonatype can do "app 
>> passwords".
>> I can have a look at the scripts if needs be, as I think they've only 
>> been tested for local deployment or staging, and only for releases (not 
>> snapshots)
>
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Publish nighly snapshots of GWT builds to Maven

[Salvador Diaz]

Hi Sean,

Snapshots are normally deployed to sonatype's OSS repo[1], but right now 
there seems to be a problem with the process so they're not available at 
the moment. Also, if you use the maven plugin the snashots are available at 
codehaus plugin snapshots repo [2].

[1] https://oss.sonatype.org/content/repositories/google-snapshots/
[2] http://nexus.codehaus.org/snapshots/

On Tuesday, April 22, 2014 at 11:50:14 AM UTC+2, Seamus McMorrow wrote:
>
> Hi, 
>
> Is there any update on deploying snapshots, so the greater GWT community 
> can contribute to testing newer releases more easily.
> I would definitely like to checkout some of the expirimental incremental 
> compiler features that are currently being landed for the next 2.7 release 
> in the summer sometime.
> (I am currently building from source, etc)
>
>
>
>
>
> On Monday, 28 October 2013 05:03:07 UTC, Colin Alworth wrote:
>>
>> I've just put up a patch that seems to resolve a current issue in 
>> deploying snapshots to a maven repository: 
>> https://gwt-review.googlesource.com/5192
>>
>> The basis of the problem requiring this patch is that maven (at least 
>> maven 3, possibly not maven 2) expects unique snapshots, and that each call 
>> to deploy:deploy-file or sign:sign-and-deploy uploads its artifact as a 
>> standalone object - when we call deploy three times (jar, sources, 
>> javadoc), the last one in is treated as the 'newest'. This doesn't happen 
>> for releases, as there can only be one release, while there can be several 
>> snapshots for a version.
>>
>> As noted, this patch does not resolve the issue locally - its my 
>> understanding that install:install-file would need to be used to make this 
>> work our locally, or else I'm just doing it wrong. The issue appears to be 
>> related to metadata not being updated correctly, but I didn't debug too 
>> extensively. I think that we can safely ignore local snapshots for the time 
>> being anyway - first, they didn't work before this patch, and second a user 
>> can either build from a snapshot server or can assign a non-snapshot 
>> version when installing locally and run it multiple times (pushing a 
>> non-snapshot version to a remote server would result in clients caching 
>> that result and not downloading it again).
>>
>> I'd appreciate any testing of this so that we can see about starting to 
>> put out snapshot builds on sonatype going forward.
>>
>> On Sunday, September 22, 2013 8:53:16 AM UTC-5, Thomas Broyer wrote:
>>>
>>> It should be relatively easy with the existing shell scripts; the major 
>>> pain point would be securing the credentials. I think Sonatype can do "app 
>>> passwords".
>>> I can have a look at the scripts if needs be, as I think they've only 
>>> been tested for local deployment or staging, and only for releases (not 
>>> snapshots)
>>
>>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/7916e43f-6a38-47fe-a1a2-09059460736e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.