On Apr 9, 5:31 pm, Kevin Bourrillion <kev...@google.com> wrote:
> Maven users -- we'll have you covered later today if all goes well.
Quick update: while we haven't deployed this to central (yet), we
should be doing so in the next day or so, and I've checked in some
pom.xmls so people can build with maven or use m2eclipse to import
into a maven-aware eclipse instance.
Because we don't have the packages split into sub-projects, I've made
a side-directory where I've created a parent maven project and some
child projects and symbolically linked them in, so guava can be built
as sub-modules (base, io, collections, concurrency, etc.), but there's
another pom which also builds the "complete" jar, which is in the root
of the project. It's a bit backwards, layout-wise, but this is to
allow Kevin et. al. to keep updating from our google code-base the way
he has, so this maven stuff can be entirely parallel and not force any
changes on the core devs' processes.
As I said, I'll be working to get our stuff pushed to central in the
next few days. In the mean-time, you can build it yourself. Just
"mvn clean install" from the /maven folder and it'll build
everything. Once the tests are imported, I'll add some "mvn site"
reports in case people want to go browsing.
cheers,
Christian
Christian Gruber @ Google.
com.google.guava:guava:r03 (for the complete package)
and the same, but with "guava-base", "guava-annotations," etc. for
each of the smaller parts. The sub-modules all have their inter-
dependencies specified in the maven poms, so just build it all and
depend on what you need.
Christian.
Christian Gruber @ Google
On Apr 12, 12:31 am, Christian Gruber <cgru...@google.com> wrote:
> So,
>
> On Apr 9, 5:31 pm, Kevin Bourrillion <kev...@google.com> wrote:
>
> >Mavenusers -- we'll have you covered later today if all goes well.
>
> Quick update: while we haven't deployed this to central (yet), we
> should be doing so in the next day or so, and I've checked in some
> pom.xmls so people can build withmavenor use m2eclipse to import
> into amaven-aware eclipse instance.
>
> Because we don't have the packages split into sub-projects, I've made
> a side-directory where I've created a parentmavenproject and some
> child projects and symbolically linked them in, so guava can be built
> as sub-modules (base, io, collections, concurrency, etc.), but there's
> another pom which also builds the "complete" jar, which is in the root
> of the project. It's a bit backwards, layout-wise, but this is to
> allow Kevin et. al. to keep updating from our google code-base the way
> he has, so thismavenstuff can be entirely parallel and not force any
> changes on the core devs' processes.
>
> As I said, I'll be working to get our stuff pushed to central in the
> next few days. In the mean-time, you can build it yourself. Just
> "mvn clean install" from the /mavenfolder and it'll build
use m2eclipse
--
guava-...@googlegroups.com.
http://groups.google.com/group/guava-discuss?hl=en
unsubscribe: guava-discus...@googlegroups.com
This list is for discussion; for help, post to Stack Overflow instead:
http://stackoverflow.com/questions/ask
Use the tag "guava".