I've just staged the 1.5 Gin release at
https://oss.sonatype.org/content/repositories/comgooglecodegwtinject-220/
Some notes:
1. Due to lack of time, this is completely untested. Please verify it
, as I will not promote it to central without verifications.
2. This is the 'post-2.2' version of the artifact. The build process
is tuned for one jar deliverable, but I'm willing to update it if
someone comes up with a patch (
http://github.com/rombert/google-gin-pom ) and include the 'pre-2.2'
one as well.
3. Is the developer list still up-to-date ? Please let me know if I
should add someone ( see
https://oss.sonatype.org/content/repositories/comgooglecodegwtinject-220/com/googlecode/gwt/inject/gin/1.5/gin-1.5.pom
, developers section )
As I've said, this is completely untested so please give it a spin.
Robert
--
Sent from my (old) computer
Hi,I've just staged the 1.5 Gin release at
https://oss.sonatype.org/content/repositories/comgooglecodegwtinject-220/
Some notes:
1. Due to lack of time, this is completely untested. Please verify it
, as I will not promote it to central without verifications.
2. This is the 'post-2.2' version of the artifact. The build process
is tuned for one jar deliverable, but I'm willing to update it if
someone comes up with a patch (
http://github.com/rombert/google-gin-pom ) and include the 'pre-2.2'
one as well.
3. Is the developer list still up-to-date ? Please let me know if I
should add someone ( see
https://oss.sonatype.org/content/repositories/comgooglecodegwtinject-220/com/googlecode/gwt/inject/gin/1.5/gin-1.5.pom
, developers section )As I've said, this is completely untested so please give it a spin.
Hi,
The deployment groupId need to be altered since it would fit in with
the 'com.google' deployment profile, which I am not a member of. I've
discussed this with Juven Xu from Sonatype - please see
OSSRH-203: GIN (GWT INjection)
https://issues.sonatype.org/browse/OSSRH-203
, especially the last comments:
>
> Re: Developer list. From the commit log of gin there are a couple new
> contributors on that release:
> fazal.asim
> dburrows
> scottb
> awiner
> philippe.beaudoin (myself ;))
Will update, thanks.
Robert
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "google-gin" group.
> To post to this group, send email to googl...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-gin+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-gin?hl=en.
Noted, thanks. Is this the one I should depend on -
http://mavencentral.sonatype.com/#artifactdetails%7Ccom.google.inject.extensions%7Cguice-assisted-inject%7C2.0
?
> same remark as Philippe: GIN 1.0 is com.google.gwt.inject:gin:1.0, not
> com.googlecode.…
Please see my previous reply.
> I don't understand why the connection (and particularly the
> developerConnection) points to the tag in the SVN (that was already the case
> for GIN 1.0)
It should point to the source control location which was used to build
the artifact. Usually this is done by tagging, but for - SNAPSHOT it
usually is trunk. It is also similar to what the maven-release-plugin
does.
> is the parent org.sonatype.oss:oss-parent:6 only for the staging version? it
> wasn't there for GIN 1.0, what does it change?
The parent is used to inherit some basic settings, following the
instructions at
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7a.1.POMandsettingsconfig
. Currently it does the following:
- declares the Sonatype snapshot and staging repositories;
- verifies that the Maven version used is one which we know produced
valid GPG checksums;
- configures some proper defaults when releasing ( sources, javadoc,
gpg ) - but that only affects Maven-based deployments, and I'm using
Ant.
>
>
>>
>> 2. This is the 'post-2.2' version of the artifact. The build process
>> is tuned for one jar deliverable, but I'm willing to update it if
>> someone comes up with a patch (
>> http://github.com/rombert/google-gin-pom ) and include the 'pre-2.2'
>> one as well.
>
> I deployed GIN as com.google.gwt.inject:gin:1.5-post-gwt-2.2 in our internal
> repo; is there something wrong with this kind of version number in Maven?
> (it looks OK to me according
> to http://sonatype.com/books/maven-book/reference/pom-relationships-sect-pom-syntax.html )
I would prefer building with a qualifier, similar to what TestNG does
( or rather did ):
com.google.gwt.inject:gin:1.5:post-gwt-2.2
com.google.gwt.inject:gin:1.5:pre-gwt-2.2
But I have not gotten around to updating the build to do so.
>
>>
>> 3. Is the developer list still up-to-date ? Please let me know if I
>> should add someone ( see
>>
>> https://oss.sonatype.org/content/repositories/comgooglecodegwtinject-220/com/googlecode/gwt/inject/gin/1.5/gin-1.5.pom
>> , developers section )
>>
>> As I've said, this is completely untested so please give it a spin.
>
>
> Is this a recompiled version or the "official" JAR?
No, I have used the files from the Google Code project downloads section.
Robert
>
> --
> You received this message because you are subscribed to the Google Groups
> "google-gin" group.
> To post to this group, send email to googl...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-gin+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-gin?hl=en.
>
--
If the 'final' 1.5 jar will be compiled with Java 1.5 that is the one
I will pick up.
Robert
On Wed, Feb 23, 2011 at 3:13 AM, Thomas Broyer <t.br...@gmail.com> wrote:
>
> On Wednesday, February 23, 2011 12:17:31 AM UTC+1, Robert Munteanu wrote:
>>
>> Hi,
>>
>> I've just staged the 1.5 Gin release at
>>
>> https://oss.sonatype.org/content/repositories/comgooglecodegwtinject-220/
>>
>> Some notes:
>>
>> 1. Due to lack of time, this is completely untested. Please verify it
>> , as I will not promote it to central without verifications.
>
> GIN 1.5 now has a dependency on guice-assistedinject too.Noted, thanks. Is this the one I should depend on -
http://mavencentral.sonatype.com/#artifactdetails%7Ccom.google.inject.extensions%7Cguice-assisted-inject%7C2.0
?
> same remark as Philippe: GIN 1.0 is com.google.gwt.inject:gin:1.0, not
> com.googlecode.…Please see my previous reply.
>> 2. This is the 'post-2.2' version of the artifact. The build process
>> is tuned for one jar deliverable, but I'm willing to update it if
>> someone comes up with a patch (
>> http://github.com/rombert/google-gin-pom ) and include the 'pre-2.2'
>> one as well.
>
> I deployed GIN as com.google.gwt.inject:gin:1.5-post-gwt-2.2 in our internal
> repo; is there something wrong with this kind of version number in Maven?
> (it looks OK to me according
> to http://sonatype.com/books/maven-book/reference/pom-relationships-sect-pom-syntax.html )I would prefer building with a qualifier, similar to what TestNG does
( or rather did ):com.google.gwt.inject:gin:1.5:post-gwt-2.2
com.google.gwt.inject:gin:1.5:pre-gwt-2.2
Thanks, updated.
>
>>
>> > same remark as Philippe: GIN 1.0 is com.google.gwt.inject:gin:1.0, not
>> > com.googlecode.…
>>
>> Please see my previous reply.
>
> Too bad!
> Cannot someone from Google publish GIN then? (maybe ask on the Guice list?)
That's unfortunately out of my court. Perhaps someone at Google
already working on Gin can short-circuit the process. Last time I
checked, I could not find the one who deployed it. But, of course, the
scripts can be easily reused by someone who can deploy in the
com.google profile ( see https://github.com/rombert/google-gin-pom ).
>>
>> >> 2. This is the 'post-2.2' version of the artifact. The build process
>> >> is tuned for one jar deliverable, but I'm willing to update it if
>> >> someone comes up with a patch (
>> >> http://github.com/rombert/google-gin-pom ) and include the 'pre-2.2'
>> >> one as well.
>> >
>> > I deployed GIN as com.google.gwt.inject:gin:1.5-post-gwt-2.2 in our
>> > internal
>> > repo; is there something wrong with this kind of version number in
>> > Maven?
>> > (it looks OK to me according
>> >
>> > to http://sonatype.com/books/maven-book/reference/pom-relationships-sect-pom-syntax.html )
>>
>> I would prefer building with a qualifier, similar to what TestNG does
>> ( or rather did ):
>>
>> com.google.gwt.inject:gin:1.5:post-gwt-2.2
>> com.google.gwt.inject:gin:1.5:pre-gwt-2.2
>
> You mean a classifier? (like testng's jdk14 and jdk15?)
> but then there would be a single gin-1.5.pom, right? and they do not have
> the same GWT dependencies!
That's correct, I've updated the script to deploy two different
versions. One question though, what is the minimum GWT version
required for the pre-2.2 artifact?
Robert
On Wed, Feb 23, 2011 at 1:57 AM, Philippe Beaudoin
<philippe...@gmail.com> wrote:
> Re: Developer list. From the commit log of gin there are a couple new
> contributors on that release:
> fazal.asim
> dburrows
> scottb
> awiner
> philippe.beaudoin (myself ;))
--
--
Find out who is responsible for deploying on Maven central for the
com.google profile and ask them to deploy the artifacts. He/she can
use my github project as a starting point.
Robert
Please find them at
https://oss.sonatype.org/content/repositories/comgooglecodegwtinject-026/
As for the groupId discussion, I'll just wait for a decision from the
devs. From the central repo statistics I can see that there have been
11k downloads of GIN 1.0, so this version is indeed in use. If the
decision is to deploy with the com.google groupId, I will not promote
this one to staging.
Cheers,
Robert
What are the chances of getting GIN to build with maven so deployment
will be that much easier? I did a quick test by moving src and test
into src/main/java, src/test/java and adding the compiler plugin with
1.6. I get a boatload of TypeLiteral errs like
OK, fixed.
>
> What are the chances of getting GIN to build with maven so deployment
> will be that much easier? I did a quick test by moving src and test
> into src/main/java, src/test/java and adding the compiler plugin with
> 1.6. I get a boatload of TypeLiteral errs like
It might work, I'm not aware of any limitations.
>
> [ERROR] /home/drfibonacci/code/gin/src/main/java/com/google/gwt/inject/
> rebind/util/SourceWriteUtil.java:[254,35] cannot find symbol
> symbol : method getRawType()
> location: class com.google.inject.TypeLiteral<capture#456 of ?>
>
I'll have to try myself...
Robert
As long as Gin will create two artifacts per release, with different
versions, I think Maven will be a rough fit. It might be more
worthwhile for me to come up with a patch to the build process which
includes deployment to the Sonatype repository ( snapshots and
releases ).
Robert
Robert
Hi all,I pushed the gin 1.5 release (post-gwt-2.2) to staging under com.google.gwt.inject: https://oss.sonatype.org/content/repositories/central_bundles-142/
The release has been pushed and is available in maven central now: http://repo2.maven.org/maven2/com/google/gwt/inject/gin/1.5.0Enjoy!Peter
Did you set up a deployment mechanism or would you still be interested
in my submitting a patch for automating the deployment?