Gin import to GitHub

[Grzegorz Nowak]

Hi

I took some time and refreshed Gin project at GitHub: google-gin

 I used google-code-export/google-gin as a base and did following things:

 - restructured to follow maven SDL

 - removed lib directory with jars and added proper dependencies (also for sources)

 - removed javadoc from master and published a fresh copy using GitHub Pages

 - upgraded to Java 8, Guice 4.2

 - fixed issues with GWT 2.8.2 (library is still built with GWT 2.7.0 due to issues with tests but samples are already built with 2.8.2)

 - configured Travis build (compile, unit tests, integration tests)

 - generated maven site and published it on gh-pages

 - refreshed both sample projects to use Thomas Broyer's GWT plugin and using them as tests during build, they are also published on gh-pages

 - installed mvn wrapper

 - fixed wiki pages and published on GitHub Wiki

Currently I don't have access to any Gin based projects so if any of you have, enjoy.

Regards

Greg

[David Nouls]

Nice work. What maven dependencies do I need to add to my project for this ? I can test this on my current project that is still using GIN. I had to fall back to guice 3.0 to make it work with gin.

--
You received this message because you are subscribed to the Google Groups "google-gin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-gin+...@googlegroups.com.
To post to this group, send email to googl...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-gin.
For more options, visit https://groups.google.com/d/optout.

[Grzegorz Nowak]

I didn't publish any snapshots or releases yet so you will have to build it locally (should be quick and easy with maven wrapper) - version = 2.1.3-SNAPSHOT.

I think that the main problem with Guice 4.x was related to it's dependencies. Old Gin was built with Ant build.xml which had manual dependency management. After moving to maven both Guice and GWT upgrade went smooth at least for sample Gin projects.

When it comes to releasing I will have to talk with somebody responsible for previous releases (or release under different groupId).

[David]

I can't test this if there is no release pushed to maven. I don't have github access at work.

[Grzegorz Nowak]

I deployed a snapshot (with javadoc and sources) to https://oss.sonatype.org/content/repositories/snapshots/

GroupId changed so the coordinates are as follows: io.github.gwtplus.gin:gin:2.1.3-SNAPSHOT

You can also use this url https://oss.sonatype.org/content/groups/public/ instead as a mvn repo location (both public releases and snapshots land there)

[Stefano Ciccarelli]

We have upgraded GIN and Guice to 4.2.0. The first tests are positive.

Great job!

[David Nouls]

I checked with our internal project and it worked flawlessly. I finally managed to move to Guice 4.2.

Great work!

Kind regards,

David Nouls

Nouls Consulting BVBA