On 22 October 2010 03:05, Sam Berlin <[email protected]> wrote: > Wow, I'm real glad that I didn't have to figure out those POMs.. > That's some complicated stuff.
to be fair, most of the complexity is due to the munging and jarjar'ing :) > I have a few questions about some of > them, much of which stems from my complete ignorance of Maven... > > core/pom.xml: > - There's a dependency on org.sonatype.sisu.inject (v2.2.1) ... why > not the actual cglib? I vaguely recall we had a custom patch.. did > that never go upstream? Does the sisu.inject use the cglib in our > lib? > the Ant build currently uses a local snapshot build of cglib - I couldn't tell if this was the same as cglib trunk because the jar under lib/build has no source (which is a pain when it comes to doing an audit) as a temporary measure I used our build of cglib trunk, which has source and javadoc - if we want consistency, we could always switch to use the local copy of cglib in the guice build tree - but it would be great if the source could be added alongside it as well, so in the future people can know what went into the final jar and if the cglib project makes a new release that would be even better because we can then all use the same official binary jar :) > - The list of files excluded for NO_AOP munging is listed in the pom > & the ant file. Is there any way both can read from a shared property > file instead of duplicating it? > yes, I believe so > persist/pom.xml: > - Why the exclusion of DynamicFinderTest? > only because it's currently excluded from the guice-persist AllTests trunk/pom.xml > - Why version 5 in the parent element? > it's the latest parent pom according to Maven central > - What's the dependencyManagement section for? Why does it only > list some of the dependencies? (And why does it need to duplicate > some things listed in the other poms? And why is there no scope?) > dependencyManagement is a way to list the versions of external artifacts used throughout the project in one place without forcing all child modules to use these dependencies ( http://maven.apache.org/pom.html#Dependency_Management) - makes it easier to see what a project uses and bump up the versions as necessary but yes, the current poms aren't ideal in this regard (mainly because I wanted to check in the working poms first and clean up the dependency sections later) - Is there any way for the javadoc to be generated using doclava > instead of javadoc? > yes, we just need to add it as a doclet - again because there's no official release it might be easier to use the local binary (ie. as a system dependency) > Also, some general questions: > - Are the dependency jars the poms are requiring the same as the jars in > SVN? > I've tried to match them where possible, some of the test dependencies might be different > - (And, just for completeness, even though you already said you're > still going to verify this... are the output jars the same as produced > from the ant build?) > they were before the recent change to the jarjar process ;) but it won't be long before they're back in sync > Thanks again for doing all of this, Stuart! > np > sam > > On 10/21/10, Stuart McCulloch <[email protected]> wrote: > > On 21 October 2010 22:18, Sam Berlin <[email protected]> wrote: > > > >> Thanks, Stuart! > > > > > > OK, buildable poms are committed and are now building on our CI machine: > > > > https://grid.sonatype.org/ci/job/Google-Guice/ > > > > the resulting 3.0-SNAPSHOTs can be found here: > > > > > https://repository.sonatype.org/content/groups/forge/com/google/inject/ > > > > just one outstanding issue relating to running the OSGi container test in > > Maven > > (must setup a few system properties before it runs) which I'll address > > tomorrow > > > > I also need to verify consistency of Maven-produced binaries with the Ant > > build > > > > Enjoy! > > > > sam > >> > >> On Thu, Oct 21, 2010 at 4:23 PM, Stuart McCulloch > >> <[email protected]>wrote: > >> > >>> On 21 October 2010 20:52, Sam Berlin <[email protected]> wrote: > >>> > >>>> Ahh, well, given that we're already moving the source to make it > easier > >>>> for Maven, I say just do it now instead of later. If people are going > >>>> to > >>>> have moving pains, let's give it to them only once. > >>> > >>> > >>> now that core is moved I'm going to try the new poms with the plain src > >>> and test folders > >>> - as long as that all builds ok and works in IDEs then I think that's > a > >>> good compromise > >>> > >>> so no major structural changes planned, and I'll give people a heads-up > >>> if > >>> that changes > >>> > >>> > >>>> sam > >>>> > >>>> > >>>> On Thu, Oct 21, 2010 at 3:40 PM, Colin Decker <[email protected] > >wrote: > >>>> > >>>>> I think step 2 would be moving the src and test directories under > each > >>>>> module to src/main/java and src/test/java. > >>>>> > >>>>> Colin > >>>>> > >>>>> > >>>>> On Thu, Oct 21, 2010 at 3:37 PM, Sam Berlin <[email protected]> > wrote: > >>>>> > >>>>>> > >>>>>> > >>>>>> On Thu, Oct 21, 2010 at 2:15 PM, Stuart McCulloch > >>>>>> <[email protected]>wrote: > >>>>>> > >>>>>>> On 21 October 2010 18:36, Sam Berlin <[email protected]> wrote: > >>>>>>> > >>>>>>>> It would be nice to keep the main source instead of a fork. > Stuart, > >>>>>>>> I think we're all OK with the patch to re-arrange the sources for > >>>>>>>> easier > >>>>>>>> maven support. Would you be able to apply your patch? > >>>>>>> > >>>>>>> > >>>>>>> sure, I can do that - I can also fix other build issues at the same > >>>>>>> time (like > http://code.google.com/p/google-guice/issues/detail?id=555 > >>>>>>> ) > >>>>>>> > >>>>>> > >>>>>> SGTM -- I think we do want persist to be a first-class extension, so > >>>>>> that would be great. What is step 2 (presumably more > controversial).. > >>>>>> adding POMs that can built Guice? I think, as Jesse may have > >>>>>> mentioned > >>>>>> earlier, that so long as the output of the Maven build & Ant build > are > >>>>>> identical binaries (with the exception of maybe META-INF & whatnot), > >>>>>> that > >>>>>> we're good with POMs that can build. > >>>>>> > >>>>>> sam > >>>>>> > >>>>>> > >>>>>>> > >>>>>>> Thanks! > >>>>>>>> > >>>>>>>> sam > >>>>>>>> > >>>>>>>> > >>>>>>>> On Thu, Oct 21, 2010 at 11:37 AM, Andrei Pozolotin < > >>>>>>>> [email protected]> wrote: > >>>>>>>> > >>>>>>>>> Stuart, hello: > >>>>>>>>> > >>>>>>>>> On Oct 18, 3:54 pm, Stuart McCulloch <[email protected]> wrote: > >>>>>>>>> > On 18 October 2010 19:25, Brian Pontarelli < > [email protected]> > >>>>>>>>> wrote: > >>>>>>>>> > >>>>>>>>> can you please clarify, what's the bottom line now? > >>>>>>>>> > >>>>>>>>> should we just treat sisu-guice as "the real brand" of guice? :-) > >>>>>>>>> > >>>>>>>>> thanks > >>>>>>>>> > >>>>>>>>> Andrei > >>>>>>>>> > >>>>>>>>> -- > >>>>>>>>> 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]<google-guice%[email protected]> > <google-guice%[email protected]<google-guice%[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]<google-guice%[email protected]> > <google-guice%[email protected]<google-guice%[email protected]> > > > >>>>>>>> . > >>>>>>>> For more options, visit this group at > >>>>>>>> http://groups.google.com/group/google-guice?hl=en. > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> -- > >>>>>>> Cheers, Stuart > >>>>>>> > >>>>>>> -- > >>>>>>> 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]<google-guice%[email protected]> > <google-guice%[email protected]<google-guice%[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]<google-guice%[email protected]> > <google-guice%[email protected]<google-guice%[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]<google-guice%[email protected]> > <google-guice%[email protected]<google-guice%[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]<google-guice%[email protected]> > <google-guice%[email protected]<google-guice%[email protected]> > > > >>>> . > >>>> For more options, visit this group at > >>>> http://groups.google.com/group/google-guice?hl=en. > >>>> > >>> > >>> > >>> > >>> -- > >>> Cheers, Stuart > >>> > >>> -- > >>> 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]<google-guice%[email protected]> > <google-guice%[email protected]<google-guice%[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]<google-guice%[email protected]> > <google-guice%[email protected]<google-guice%[email protected]> > > > >> . > >> For more options, visit this group at > >> http://groups.google.com/group/google-guice?hl=en. > >> > > > > > > > > -- > > Cheers, Stuart > > > > -- > > 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]<google-guice%[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]<google-guice%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-guice?hl=en. > > -- Cheers, Stuart -- 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.
