I'll take a look at it, but I have to get the guava libraries dealt
with and some other things more directly related to my day-job. But
I'm interested in what you've pulled together and will take a peek.
cheers,
Christian.
On Apr 16, 2010, at 10:02 AM, Jelle Herold wrote:
On 6 apr 2010, at 13:18, Max Bowsher wrote:
First steps, though: Get POMs in trunk that are sufficient for
1) representing Guice in the Maven Central repo.
2) developing Guice in an IDE.
We depend heavily on maven and guice so I've written POM files for
guice that can build and test (part) of the source but keep the
current directory structure. I pull from SVN into a mercurial
repository and maintain the "patches" there.
The repository is here http://bitbucket.org/wires/google-guice-mavenized/
In addition to building and testing, we can release maven artifacts
using the maven release plugin, we have done so for svn r1136 (to be
used internally by our projects).
I've also added OSGi and eclipse plugin meta data to the artifact.
This needs work, but might be a good way towards real maven builds
of guice?
Let me know what you think.
Regards,
Jelle.
--
You received this message because you are subscribed to the Google
Groups "google-guice" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected]
.
For more options, visit this group at http://groups.google.com/group/google-guice?hl=en
.
--
You received this message because you are subscribed to the Google Groups
"google-guice" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-guice?hl=en.
