Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Guice extensions for Maven #219

Closed
gissuebot opened this issue Jul 7, 2014 · 13 comments
Closed

Support Guice extensions for Maven #219

gissuebot opened this issue Jul 7, 2014 · 13 comments

Comments

@gissuebot
Copy link

From inder123 on July 17, 2008 08:00:52

Ideally, you would get these published in the maven central repository.

But since that takes too much effort, how about just publishing it under
this project itself. See how Google Gson project does it. For it, the
repository is available at http://google-gson.googlecode.com/svn/mavenrepo/ Also see the pom.xml for the gson. We just run

mvn package
mvn source:jar
mvn javadoc:jar
mvn assembly:assembly
mvn deploy

and then cd ../mavenrepo/com/google/code/gson/gson and add new files to
subersion. This gets the new releases published under our maven2
repository. You can follow a similar process to publish these locally. Thanks.

Original issue: http://code.google.com/p/google-guice/issues/detail?id=219

@gissuebot
Copy link
Author

From antony.stubbs on August 12, 2008 17:04:58

Woah that's really cool trick with google code hosting!

btw, do you actually do
mvn -ff package source:jar javadoc:jar assembly:assembly deploy
?

@gissuebot
Copy link
Author

From plightbo on August 15, 2008 11:13:52

I'd also like to see this!

@gissuebot
Copy link
Author

From rene.gielen on August 19, 2008 05:46:05

There is even an easier way without the need to upload / commit manually, just try
the svn wagon. A working example is shown here https://code.google.com/p/jamailia/source/browse/maven/repo/org/jamailia/jamailia/1.0.0-SNAPSHOT/jamailia-1.0.0-SNAPSHOT.pom Note the <distributionManagement/> and the <build/extensions/> section.

Additionally, as the deployer, you will have to add server authentication settings to
your ~/.m2/settings.xml similar to this:

...
<servers>
    <server>
        <id>jamailia-snapshots-maven-repo</id>
        <username>foo</username>
        <password>bar</password>
    </server>
</servers>
...

@gissuebot
Copy link
Author

From rene.gielen on August 19, 2008 05:59:34

Additional notes to my last comment:

  • the actual deployment is calling mvn clean package source:jar javadoc:jar
    assembly:assembly deploy
  • automatic deployment works really fine and self-contained with a CI environment
    like Husdon etc. that way

@gissuebot
Copy link
Author

From inder123 on September 01, 2008 08:57:05

rene, I consider adding anything to ~/.m2/settings.xml as a big issue so we should
avoid that as much as possible.

Anthony: yes, it can certainly be run that way as well.

I am disappointed to not see any progress on this issue. Can someone from the Guice
team comment here why this is not being addressed? If needed, I will be happy to make
changes or submit a patch.

@gissuebot
Copy link
Author

From rene.gielen on September 01, 2008 10:30:02

inder123,

I'm with you on having to configure unneeded stuff in settings.xml is bad and should
be avoided. However there are a couple of situations where you would find it
necessary to touch this file.

settings.xml is, among others, for providing configuration that would be misplaced in
the project specific configuration, such as

  • workplace specific configuration, eg. chose gwt-linux installation on a linux
    workstation as gwt-home, gwt-windows on a windows machine
  • user specific configuration, such as user secrets / credentials

Each maven wagon (ssh, ftp etc.) with need for authentication relies on configuring
your credentials in settings.xml, it's a documented feature and the wanted behaviour.
Since there are only a couple of people having write access to the svn / being in the
role of a release manager, only they would need to configure those credentials,
simlilar to them locally having to configure svn write access in their svn
credentials store or IDE. 99,9999% of the users won't have configure anything besides
the given configuration in the pom.

Deploying in your local repository, manually identifying, copying and adding the
output to a subversion checkout and committing afterwards for each release is more
error prone, more steps to do and does not integrate well with automated nightly
build/ci, than simply doing a one time local configuration per workstation plus typing
mvn jar source:jar javadoc:jar assembly:assembly deploy
for each deployment

Just my 2 cents,
Rene

@gissuebot
Copy link
Author

From dom.happygiraffe.net on October 03, 2008 13:56:27

Just to bring this (somewhat) back on topic, is there any likelihood of seeing guice-servlet in the central maven
repo any time soon?  Or do we just wait for guice 2.0?

@gissuebot
Copy link
Author

From james.strachan on October 23, 2008 05:51:59

if its any help there's a maven repo of recent builds here... https://code.google.com/p/guiceyfruit/wiki/Maven

@gissuebot
Copy link
Author

From jpgorrono on December 06, 2008 17:19:58

No guice-spring jars in there....

Where can I find guice-spring in a m2 repo?

@gissuebot
Copy link
Author

From jpgorrono on December 06, 2008 17:22:25

Sorry misread the title 'guice-servlet and guice-struts2' too late to add
guice-spring? :)

@gissuebot
Copy link
Author

From limpbizkit on December 30, 2008 16:21:36

(No comment was entered for this change.)

Summary: Support Guice extensions for Maven
Owner: gk5885

@gissuebot
Copy link
Author

From maxb@j.maxb.eu on August 13, 2009 09:36:57

This issue appears to be fixed: http://repo1.maven.org/maven2/com/google/inject/integration/

@gissuebot
Copy link
Author

From sberlin on February 19, 2011 12:35:55

(No comment was entered for this change.)

Status: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant