Re: [Bigdata-developers] (no subject)

[Bryan T. <br...@sy...>]

Brian,

I've linked the maven notes page [1] from the main wiki page [2].

Could either you or Sean accept the issue [3] so people know that it is in progress and update the issue weekly so other people can track what is happening in the branch?

Thanks,
Bryan 

[1] https://sourceforge.net/apps/mediawiki/bigdata/index.php?title=Main_Page
[2] https://sourceforge.net/apps/mediawiki/bigdata/index.php?title=MavenNotes
[3] https://sourceforge.net/apps/trac/bigdata/ticket/168

> -----Original Message-----
> From: Brian Levine 
> Sent: Saturday, September 25, 2010 12:13 PM
> To: Bryan Thompson
> Subject: Re: [Bigdata-developers] (no subject)
> 
> Hi,
> 
> I've created a page here:
> 
> https://sourceforge.net/apps/mediawiki/bigdata/index.php?title
> =MavenNotes
> 
> I didn't know whether you wanted to link to this page from 
> another page, so I left that to you.
> 
> Thanks.
> 
> -b
> 
> 
> On 09/24/2010 06:06 PM, Bryan Thompson wrote:
> > Brian,
> >
> > Thanks for posting this information.  Would you consider 
> creating a wiki page for the maven integration to capture 
> this information?
> >
> > Thanks,
> > Bryan
> > ________________________________________
> > From: Brian Levine
> > Sent: Friday, September 24, 2010 3:56 PM
> > To: big...@li...
> > Subject: [Bigdata-developers] (no subject)
> >
> > Hi all,
> >
> > Here are a few notes on the new bigdata-integ test module I 
> recently checked in to the maven_scaleout branch.
> >
> > Overview
> >
> > The main goal of the bigdata-integ module is to separate 
> "heavy-weight" tests from the standard unit tests that a 
> developer would run during a typical development cycle. Also 
> included are tests that require some external infrastructure 
> to be set up (e.g. a lookup service) prior to running the 
> tests. So the term "integration tests" is not particularly 
> accurate and is really a catch-all for anything that we don't 
> want to be part of the lighter-weight unit tests.  As the 
> componentization of bigdata proceeds, we will see some of 
> these integration tests move back into their respective 
> components but still be separated from the light-weight unit 
> tests. Maven's separation of unit and integration tests into 
> separate phases of the build lifecycle makes this pretty 
> straightforward.
> >
> > We've only moved about 30-ish tests so far and we'll tackle 
> more  going forward.
> >
> > How to run the integration tests
> >
> > The bigdata-integ module is now referenced in the bigdata 
> parent POM. If you run a build from the parent project, 
> you'll build bigdata-core, generate its artifacts including 
> the deployment tarball, and run the integration tests. Note 
> that the unit tests are currently not being run during the 
> build, but this should change soon.
> >
> > mvn clean install
> >
> > If you've already built bigdata-core and just want to run 
> the integration tests, you can run this from the 
> bigdata-integ directory:
> >
> > cd bigdata-integ
> > mvn clean integration-test (mvn clean install will also work)
> >
> > How to not run the integration tests
> >
> > If you don't want to run the integration tests, it's easy.  You can:
> >
> >
> > -       Run the build from the bigdata-core project rather 
> than the parent project.
> >
> > -       OR from the parent project, add the -DskipITs 
> argument on the command-line (this skips integration tests 
> just as -DskipTests skips unit tests)
> >
> > -       OR from the parent project, run mvn clean package 
> instead of mvn clean install. Since the integration-test 
> build phase comes after the package build phase, the 
> integration tests won't be executed.
> >
> > Thanks.
> >
> > -brian
> >    
>