From crazyboblee on March 12, 2007 08:12:02

Any volunteers? :)

From gk5885 on March 16, 2007 02:19:23

actually, sure.  i think that i ought to have some time this weekend to get it
done.  i'll attach a pom within the next couple of days for you guys to look at.

i noticed that the original groupId that you guys had listed was com.google.inject.
is that still the preferred groupId?

From crazyboblee on March 16, 2007 08:29:49

We have a POM in issue #60 .

From jens.lyn on March 17, 2007 18:33:09

I have created some POM's for the project but I have also modified the project
structure a little (to better match the Maven project structure). Please see the
attached zip file.

You can create your IDEA project files by typing:

mvn idea:clean install idea:idea

in the root of guice-maven. Let me know what you think.

Binary attachments: guice-maven.zip

From gk5885 on March 17, 2007 22:52:16

as promised, here's my crack at the poms.  i've looked at all (i think) of the other attempts and i'll briefly
describe what makes mine a bit different.

- there is one pom per artifact  ( i didn't do guice-strtus2-plugin because i don't know much about struts or
what that artifact would depend on. )  this differs from Alan Cabrera's approach.

- the metadata is as complete as i could possibly make it.  there's some developer information that still needs
to be populated, but all the project-related stuff is there.  i noticed that i had some different values from
some of the previous attempts for a few things, but i'm reasonably sure that i have correct information

- i made no attempt at the build or reporting portions of pom.  since that information is only used if maven is
the build tool, i saw no need to fill things like the parameters for the javadoc plugin.  it's even been mentioned
that in order for any of that to really make sense, there would need to be some re-org for the project
structure.  i'd be glad to help with that too if somebody decides to move towards a maven build, but until
then, it's wasted effort.

- correct dependency information.  some people used older versions of cglib because the newest one wasn't
in the main repo.  obviously, that's not actually an option.  i just pull the artifact from maven2-
repository.dev.java.net

anyway, like i said, these are strictly for deploying guice 1.0 as-is.  i'm not trying to overhaul the build
process.  the only thing that I would say about actually deploying it is that the artifact that goes in the
repository should probably not have the jarjar stuff, just because it goes against the whole maven philosophy.
luckily, since the versions in the pom are enclosed in brackets, we can be assured that maven will build with
the specified versions of cglib and asm.

Binary attachments: guice.zip

From bileblog on March 21, 2007 17:25:20

This is fixed now: http://repo1.maven.org/maven2/com/google/code/guice/guice/1.0/

From gk5885 on March 21, 2007 21:28:22

Hani, there's an issue with the artifact that was submitted to Maven.  In the zip file I provided there are several
poms; one for each artifact.  So, guice.jar has a pom, guice-servlet has a pom, etc.  Additionally, there is a POM
that contains metadata common to each project.  What was submitted to maven was the common metadata +
guice.jar.  This will break.  We'd actually need a submission for the common data and one for the artifact (and
one for each of the other jars as well).

From gk5885 on April 12, 2007 12:48:19

This is still wrong in the repository.  Can anyone get this fixed?

From gk5885 on April 15, 2007 12:42:25

I've now deployed guice properly to http://kickstyle.net/maven/ .  I also fixed an
error in the pom for guice (the jar not the parent), but that never got deployed to
the central repository anyway... :-)  This was the layout that I'd originally intended.

From pkozelka on April 20, 2007 01:21:02

I thought this might be interresting for Maven users:
I just added "mavenized" flavor of guice under the project google-apis-mavenized ( https://code.google.com/p/google-apis-mavenized/ ).
Using the tricks like subversion external and filesystem softlinks, it reuses the
original codebase but within the default Maven layout. Just do svn checkout from https://google-apis-mavenized.googlecode.com/svn/trunk/guice-mavenized , then apply the patch as described in README.txt, and the mavenized Guice is ready.
Please let me know here or in that project's issue tracking what you think about it...

From pkozelka on April 20, 2007 08:02:30

I just discovered that the mavenized guice was not compilable out of the box, and
fixed it right now - sorry for that.
Also, as kevinb9n has just optimized the imports, it's currently enough to just
checkout from https://google-apis-mavenized.googlecode.com/svn/trunk/guice-mavenized and then "mvn clean install" will work :)

From limpbizkit on May 30, 2008 00:43:57

We should provide a proper Maven release with 2.0. I think we'll keep Ant for internal use, since that's what our
tools work with.

Labels: Milestone-Release2.0

From limpbizkit on May 30, 2008 14:24:22

See also issue 91 , which has another pom attached.

From limpbizkit on May 30, 2008 14:26:28

Issue 194 notes that for each release we should include all extensions in our Maven 2 distribution.

From aquatopia on June 18, 2008 12:18:09

limpbizkit: Since you're using Ant internally, I suggest that you take a look at the
approach that pkozelka suggests in his comments. I tried checking it out and after
updating deps and adding the new extensions (assistedinject, commands, etc), it works
like a charm.

The only downside I see is that it ignores the jarjar targets, but I understand that
it should work with Maven.

If you like this approach, then I'm willing to help him maintain it.

From limpbizkit on June 29, 2008 16:17:52

For v2 we're going to attempt a best-of-both-worlds approach: publish a Maven pom file, but keep ant as
our build tool internally. Our motivation is that we'd like to continue to have Guice buildable by as wide a
variety of tools possible. Currently Ant is the most widely deployed Java build tool.

The lack of jarjar support is also somewhat annoying. We don't want to feel pressure to keep our internal
libraries up-to-date if they work just fine as-is for us! On the flipside, forcing our clients to have an extra
copy of a dependency that they're already using is somewhat rude of us.

Greg Kick (gk5885) will take care of exporting Guice 2.0 to Maven users. The other support is much
appreciated -once Greg's submitted the poms, please keep us informed whether they work (either way!)

Status: Started
Owner: gk5885

From sven.linstaedt on August 13, 2008 03:17:20

Because I need an up to date Guice v2.0 lib for one of my own projects (and of course
to keep up with the new features), I have set up a CI with self provided pom
( http://www.kamalook.de:8080/hudson/job/Guice/ws/trunk/pom.xml ) under http://www.kamalook.de:8080/hudson/job/Guice/ .

The regulary deployed Snapshots of Guice 2.0 with it's dependencies are available in
a maven repository at http://maven.kamalook.de/ .

If you need a nightly snapshot have look at http://www.kamalook.de:8080/hudson/job/Guice/com.google.inject$guice/lastSuccessfulBuild/artifact/ .

From johannes@familieschneider.info on September 13, 2008 08:08:23

Thanks sven. Your work saved me a bunch of time.
I really don't understand why there are still projects out there not using maven...

From yulenice on March 09, 2009 00:14:01

awesome...thanks a lot

From themuleman on May 25, 2009 07:51:23

FWIW we have the Guice 2.0 final jars hosted in the Mule project dependency repo on
codehaus: http://dist.codehaus.org/mule/dependencies/maven2/guice/

From gk5885 on May 25, 2009 20:39:35

Guice 1.0 has been deployed to the Google repository and will be replicated to central soon.  I have a bit of work
to do on the 2.0 poms, but they'll be coming soon...

From gpampara on June 02, 2009 01:17:52

So, which location should I reference for the maven artifacts then?

From gk5885+personal@kickstyle.net on June 02, 2009 10:07:55

https://code.google.com/p/google-maven-repository/

From brennanspies on June 04, 2009 10:39:35

I use the guice-maven project, which has Guice 2.0 release in the repository: http://guice-maven.googlecode.com/svn/trunk . But it would be nice to see this in a
more standard place.

From bens%fastcastmedia.com@gtempaccount.com on June 07, 2009 23:38:04

Who would have added Guice 1.0 originally?

From lindner+unused1@inuus.com on June 08, 2009 15:09:09

still waiting on this?  anything we can do to help?

From gk5885+personal@kickstyle.net on June 08, 2009 15:34:12

this will happen this week.  sorry for the delay.

From gk5885+personal@kickstyle.net on June 15, 2009 10:09:54

I got held up last week, but I'll be working on this today.

From gpampara on June 17, 2009 01:44:01

Please let us know when you are ready. I'm sure there are a few people eagerly
awaiting for the maven repo containing the guice jars.

Thanks.

From gk5885+personal@kickstyle.net on June 17, 2009 11:30:53

Of course.  I got about half-way through and hope to finish it up today.

From gk5885+personal@kickstyle.net on July 14, 2009 20:05:57

the new metatdata is checked in.  the final alterations will be made and it'll be checked in this week.  the 80%
work has been taking about 120% lately…

From GuiSim on July 21, 2009 12:35:37

It's been a week, is there any news ?

From gk5885+personal@kickstyle.net on July 21, 2009 13:29:42

Jesse was prodding me about this too.  As soon as I have a free moment, this is the first
TODO on the list.  Sorry about the delay.

From GuiSim on July 31, 2009 11:48:26

Sorry posting here again but..
I'd like to use Guice with Maven :)

I know you're all very busy so I understand the delays. I just want to keep this on the
todo list ;)

From gk5885+personal@kickstyle.net on July 31, 2009 11:53:38

yep.  this should go out today

From lindner+unused1@inuus.com on July 31, 2009 11:54:54

this should work for now, no?

    <repository>
      <id>guice</id>
      <url> http://guice-maven.googlecode.com/svn/trunk/ </repository>

From GuiSim on July 31, 2009 11:56:51

Awesome, thanks a lot gk5885

From gk5885 on July 31, 2009 16:01:08

Guice 2.0 has been submitted to the google-maven-repository.  It will sync with central shortly.

Status: Fixed

From jfpoilpret on August 01, 2009 08:26:08

Well, I find it disappointing not to have guice extension libs in this maven repo as
well (assistedinject, multimap...)
In addition, the provided pom.xml is minimalistic as it does not include guice
dependencies (aopalliance)
For the time being, I still can't use this repo and must fall back to http://maven.jdkcn.com/ which contains all artifacts (but also has the missing
dependencies problem, but that is not a blocker).

From gk5885+personal@kickstyle.net on August 01, 2009 09:32:21

@jfpoilpret  I'm not sure what you're talking about.  All artifacts have been uploaded.  See https://code.google.com/p/google-maven-repository/source/browse/#svn/repository/com/google/inject

From jfpoilpret on August 01, 2009 09:57:05

Oops, you're right. My bad, there are now so many different maven repos with Guice
that I went to the wrong link:-(
Everything looks fine, forget my previous stupid comment;-)

From dom.happygiraffe.net on August 03, 2009 08:02:50

I'm afraid that there are still no -sources jars in the maven repository ( issue 382 ).
 Any chance of these making it in?  Thanks!

From padcom on September 22, 2009 09:28:48

Still no sources in either maven repository. Is this going to happen any time soon?

From gk5885+personal@kickstyle.net on September 22, 2009 11:04:33

thanks for the reminder.  i'll try to do that today.

From tomas.prochazka on October 05, 2009 11:29:48

Still no source code and javadoc in repository :-(

From gk5885+personal@kickstyle.net on October 05, 2009 11:34:05

Yep.  Working with the Maven team to fix this up.  There's an issue with the md5 hashes
as well, and we're going to try to fix that all up in one massive fixit.

From py.ricau on October 23, 2009 08:10:00

Any chance to have Guice "non aop" in Maven repositories as well ? That'd be great to
build Android apps that use Guice (though Android jars are not available yet in Maven...)

From gk5885+personal@kickstyle.net on October 23, 2009 08:40:12

sure thing.  I need to send an email to the maven guys to get the status of the source
and javadoc jars and the hash issues, so i'll just add that to the list of things to work on.

From mburton on April 21, 2010 16:18:50

Great, glad to hear it!  Looking forward to getting guice no aop up on maven soon

From mosabua on April 28, 2010 11:01:58

Could we have an update if the no_aop artifact is going to make it anytime soon? We would like to depend on it
for roboguice.

From jdpatterson on June 26, 2010 05:59:05

Need the non AOP version in the repo

From zeezinj on October 09, 2010 22:33:21

I agree.  I do not have the time to deal with maven, when it's supposed to be saving me time!  Please let me know asap when it's available! Thanks.

From robert.taylor426 on December 25, 2010 11:17:55

Also looking forward to getting guice no aop up in maven...'soon'

From fabiodasoghe on March 11, 2011 04:15:30

To anyone interested: Guice no-aop is on central here: http://mvnrepository.com/artifact/com.google.inject/guice/2.0-no_aop (it seems they changed the group id since 1.0)

From zeezinj on March 11, 2011 05:34:38

Yes, before or if you want to run a custom guice release, you can just deploy it to your own repository (after building from source) OR you can take a jar and "manually" add it to your repository, OR you can specify the file in your xml/config file.  This is not clear from this thread, but at the time I posted this, maven was a nightmare to me, now it's a godsend.  Good luck!