Maven for Build?

[Brandon Goodin <br...@gmail.com>]

Hey Guys,

I wanted to throw a bone out to everyone and ask the question "Should we use
Maven for our build?". I put together a POM today that makes use of the
current iBATIS SQL Map structures. It is pretty darn simple and required
very little effort. The largest amount of my time was spent refactoring the
TestCL (Test Classloader) to use the current thread classloader as a parent
due to some incompatibilities with how Maven runs it's test. That aside, I
was surprised at how little effort it took to get the iBATIS SQLMap jar
built. Plus, Because of the dependency management of Maven I was able to
avoid having to use the oscache devsrc for oscache and avoid using the
devlib jars. I only used Maven to build the Data Mapper/SQL Map. I wasn't
familiar enough with Abator's build process to wire in Maven for it.

Benefits:

* I thought it would be good to aid in reducing the complexity of our
current build/deploy. If we want to provide our jars to the Maven crowd we
would be tasking the deploying member with taking the final jar built from
ant and running deploy:deploy-file for it. I have to say that I looked
through our release process and I really wouldn't want to add yet another
step. Seems like maven can consolidate this for us.
* We can run ant from within Maven if we so desire to continue performing
tasks that maven doesn't provide for.

Additional benefits, thoughts, or concerns?

Thanks,
Brandon

Re: Maven for Build?

[Clinton Begin <cl...@gmail.com>]

> Ouch, yeah, I hate it. :-D

What changes would you make to it?  I'm totally open to ideas.  I've
just never had a problem with it, so I never changed it.  :-)

One think I would do is ditch the build.properties file...nothing ever
changes in it, so it doesn't need to be external.  I'd also change
some of the property names.  (we did both when we cloned the build for
the new project)

Clinton

On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
> On 2/13/07, Clinton Begin <cl...@gmail.com> wrote:
> > Really?  I think our build is great.  We just cloned it for a project
> > we're working on.
>
> Ouch, yeah, I hate it. :-D
>
> After working with maven for a few months, it seems really overcomplicated.
>
> > No external dependencies or extra steps, and preferrably no
> > downloading.....argh.  I hate maven.
>
> But we *do* have external dependencies already. We just jump through
> some extra hoops to pretend that we don't (devsrc).
>
> > And I'm a -10000 for Maven generated website.
> > Remember, we have .NET and Ruby projects too.
>
> Heh, yeah, OK, I can't argue that, even w/o .net and ruby...maven
> generated sites are, well, hideous.
>
> > Cheers,
> > Grumpy Clinton
> >
> > On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
> > > I like the idea - it makes the checkout faster, and "mvn idea:idea" is
> > > worth it's weight in gold, and our current build.xml is a bugger, I
> > > hate it.
> > >
> > > So, I wonder if we can skin the generated site to make it not look
> > > like crap^H^H^H^H every other maven generated site. :-)
> > >
> > > Larry
> > >
> > >
> > > On 2/12/07, Brandon Goodin <br...@gmail.com> wrote:
> > > > Hey Guys,
> > > >
> > > > I wanted to throw a bone out to everyone and ask the question "Should we use
> > > > Maven for our build?". I put together a POM today that makes use of the
> > > > current iBATIS SQL Map structures. It is pretty darn simple and required
> > > > very little effort. The largest amount of my time was spent refactoring the
> > > > TestCL (Test Classloader) to use the current thread classloader as a parent
> > > > due to some incompatibilities with how Maven runs it's test. That aside, I
> > > > was surprised at how little effort it took to get the iBATIS SQLMap jar
> > > > built. Plus, Because of the dependency management of Maven I was able to
> > > > avoid having to use the oscache devsrc for oscache and avoid using the
> > > > devlib jars. I only used Maven to build the Data Mapper/SQL Map. I wasn't
> > > > familiar enough with Abator's build process to wire in Maven for it.
> > > >
> > > > Benefits:
> > > >
> > > > * I thought it would be good to aid in reducing the complexity of our
> > > > current build/deploy. If we want to provide our jars to the Maven crowd we
> > > > would be tasking the deploying member with taking the final jar built from
> > > > ant and running deploy:deploy-file for it. I have to say that I looked
> > > > through our release process and I really wouldn't want to add yet another
> > > > step. Seems like maven can consolidate this for us.
> > > > * We can run ant from within Maven if we so desire to continue performing
> > > > tasks that maven doesn't provide for.
> > > >
> > > > Additional benefits, thoughts, or concerns?
> > > >
> > > > Thanks,
> > > > Brandon
> > > >
> > >
> >
>

Re: Maven for Build?

[Larry Meadors <lm...@apache.org>]

On 2/13/07, Clinton Begin <cl...@gmail.com> wrote:
> Really?  I think our build is great.  We just cloned it for a project
> we're working on.

Ouch, yeah, I hate it. :-D

After working with maven for a few months, it seems really overcomplicated.

> No external dependencies or extra steps, and preferrably no
> downloading.....argh.  I hate maven.

But we *do* have external dependencies already. We just jump through
some extra hoops to pretend that we don't (devsrc).

> And I'm a -10000 for Maven generated website.
> Remember, we have .NET and Ruby projects too.

Heh, yeah, OK, I can't argue that, even w/o .net and ruby...maven
generated sites are, well, hideous.

> Cheers,
> Grumpy Clinton
>
> On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
> > I like the idea - it makes the checkout faster, and "mvn idea:idea" is
> > worth it's weight in gold, and our current build.xml is a bugger, I
> > hate it.
> >
> > So, I wonder if we can skin the generated site to make it not look
> > like crap^H^H^H^H every other maven generated site. :-)
> >
> > Larry
> >
> >
> > On 2/12/07, Brandon Goodin <br...@gmail.com> wrote:
> > > Hey Guys,
> > >
> > > I wanted to throw a bone out to everyone and ask the question "Should we use
> > > Maven for our build?". I put together a POM today that makes use of the
> > > current iBATIS SQL Map structures. It is pretty darn simple and required
> > > very little effort. The largest amount of my time was spent refactoring the
> > > TestCL (Test Classloader) to use the current thread classloader as a parent
> > > due to some incompatibilities with how Maven runs it's test. That aside, I
> > > was surprised at how little effort it took to get the iBATIS SQLMap jar
> > > built. Plus, Because of the dependency management of Maven I was able to
> > > avoid having to use the oscache devsrc for oscache and avoid using the
> > > devlib jars. I only used Maven to build the Data Mapper/SQL Map. I wasn't
> > > familiar enough with Abator's build process to wire in Maven for it.
> > >
> > > Benefits:
> > >
> > > * I thought it would be good to aid in reducing the complexity of our
> > > current build/deploy. If we want to provide our jars to the Maven crowd we
> > > would be tasking the deploying member with taking the final jar built from
> > > ant and running deploy:deploy-file for it. I have to say that I looked
> > > through our release process and I really wouldn't want to add yet another
> > > step. Seems like maven can consolidate this for us.
> > > * We can run ant from within Maven if we so desire to continue performing
> > > tasks that maven doesn't provide for.
> > >
> > > Additional benefits, thoughts, or concerns?
> > >
> > > Thanks,
> > > Brandon
> > >
> >
>

Re: Maven for Build?

[Clinton Begin <cl...@gmail.com>]

Really?  I think our build is great.  We just cloned it for a project
we're working on.

I'm a -1 for Maven for primary build.  Ant works fine and I'm pissed
that we need to do all of this to get a frigging pom file and a majic
jar full of Maven meta-bs?  Jeeez.  If someone else is willing to do
all the work to get us there, I'm cool with that.  But it MUST still
be a one-click build.  No external dependencies or extra steps, and
preferrably no downloading.....argh.  I hate maven.

And I'm a -10000 for Maven generated website.

Remember, we have .NET and Ruby projects too.

Cheers,
Grumpy Clinton

On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
> I like the idea - it makes the checkout faster, and "mvn idea:idea" is
> worth it's weight in gold, and our current build.xml is a bugger, I
> hate it.
>
> So, I wonder if we can skin the generated site to make it not look
> like crap^H^H^H^H every other maven generated site. :-)
>
> Larry
>
>
> On 2/12/07, Brandon Goodin <br...@gmail.com> wrote:
> > Hey Guys,
> >
> > I wanted to throw a bone out to everyone and ask the question "Should we use
> > Maven for our build?". I put together a POM today that makes use of the
> > current iBATIS SQL Map structures. It is pretty darn simple and required
> > very little effort. The largest amount of my time was spent refactoring the
> > TestCL (Test Classloader) to use the current thread classloader as a parent
> > due to some incompatibilities with how Maven runs it's test. That aside, I
> > was surprised at how little effort it took to get the iBATIS SQLMap jar
> > built. Plus, Because of the dependency management of Maven I was able to
> > avoid having to use the oscache devsrc for oscache and avoid using the
> > devlib jars. I only used Maven to build the Data Mapper/SQL Map. I wasn't
> > familiar enough with Abator's build process to wire in Maven for it.
> >
> > Benefits:
> >
> > * I thought it would be good to aid in reducing the complexity of our
> > current build/deploy. If we want to provide our jars to the Maven crowd we
> > would be tasking the deploying member with taking the final jar built from
> > ant and running deploy:deploy-file for it. I have to say that I looked
> > through our release process and I really wouldn't want to add yet another
> > step. Seems like maven can consolidate this for us.
> > * We can run ant from within Maven if we so desire to continue performing
> > tasks that maven doesn't provide for.
> >
> > Additional benefits, thoughts, or concerns?
> >
> > Thanks,
> > Brandon
> >
>

Re: Maven for Build?

[Ted Husted <hu...@apache.org>]

On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
> I like the idea - it makes the checkout faster, and "mvn idea:idea" is
> worth it's weight in gold,

Not to mention mvn eclipse:eclipse.

We use Maven for the Struts builds. We're often on the leading edge of
what Maven (or Ant or Ivy) can do, and that's been painful sometimes.
But, it definitely works for us, and it does make it very easy for new
coders to get started.

-Ted.

Re: Maven for Build?

[Clinton Begin <cl...@gmail.com>]

I'm willing to try Maven.

There would be no harm in Brandon creating the full Maven build that
does everything the existing build does (tests, coverage, reports,
versioning, manifest, deployable ZIP, release.txt update etc).
There's nothing in the current build that isn't used, so Maven would
have to do exactly the same thing or something equivalent or better
for it to be a suitable replacement.  At that point we could cut over
to Maven.

If Maven can do everything easier, faster, cleaner better, or for some
benefit....I would be willing to be completely wrong.  I'll post my
wrong-ness to this list publicly and send Brandon a cake.  :-)

Clinton


On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
> HATE COMMENTS?!? Goodin, I'll kick your fat butt! :-D
>
> On 2/13/07, Clinton Begin <cl...@gmail.com> wrote:
> > >>I think there is a bit of hostility here.
> >
> > I don't sense any hostility...just strong opinions.
>
> Agreed, I'll make no more butt-kicking comments...today. Except via
> IM. Unless provoked.
>
>  :-)
>
> >
> > >>  If you don't have an internet connection then you are in a sad sad sad state
> >
> > Except for those who like to work with or on our framework while on an
> > airplane...or a bus or a train....laptops are great things.
> > Unfortunately wireless networks are not yet ubiquitous.  Not everyone
> > works from home.  :-)
>
> That really only applies if they have never built the project (or
> other projects that share our dependencies) - if they have, they
> already have all the dependencies, and "mvn -o" makes life good again.
>
> > >> I believe that self contained build are overrated as well.
> >
> > Completely disagree.  When I can't build it with one click, I generally toss it.
> >
>
> Dang, you are lazy. ;-)
>
> I agree with Brandon on this - maven is a 1M download, I don't think
> it's too much to ask. I guess we could bundle it with iBATIS like we
> bundle ant, but IMO, that is messier, because maven is a bit more
> involved than ant is.
>
> > >> all the unnecessary anger
> >
> > There's no anger man.  Just constructive debate.  I hope we never
> > start to sound like those chipmunks on the Bugs Bunny show...."No no
> > no...you're the wonderful one."  :-)
>
> Group hug? Nah, I still wanna kick Brandon. Doh! I take that back.
>
> Larry
>

Re: Maven for Build?

[Larry Meadors <lm...@apache.org>]

HATE COMMENTS?!? Goodin, I'll kick your fat butt! :-D

On 2/13/07, Clinton Begin <cl...@gmail.com> wrote:
> >>I think there is a bit of hostility here.
>
> I don't sense any hostility...just strong opinions.

Agreed, I'll make no more butt-kicking comments...today. Except via
IM. Unless provoked.

 :-)

>
> >>  If you don't have an internet connection then you are in a sad sad sad state
>
> Except for those who like to work with or on our framework while on an
> airplane...or a bus or a train....laptops are great things.
> Unfortunately wireless networks are not yet ubiquitous.  Not everyone
> works from home.  :-)

That really only applies if they have never built the project (or
other projects that share our dependencies) - if they have, they
already have all the dependencies, and "mvn -o" makes life good again.

> >> I believe that self contained build are overrated as well.
>
> Completely disagree.  When I can't build it with one click, I generally toss it.
>

Dang, you are lazy. ;-)

I agree with Brandon on this - maven is a 1M download, I don't think
it's too much to ask. I guess we could bundle it with iBATIS like we
bundle ant, but IMO, that is messier, because maven is a bit more
involved than ant is.

> >> all the unnecessary anger
>
> There's no anger man.  Just constructive debate.  I hope we never
> start to sound like those chipmunks on the Bugs Bunny show...."No no
> no...you're the wonderful one."  :-)

Group hug? Nah, I still wanna kick Brandon. Doh! I take that back.

Larry

Re: Maven for Build?

[Brandon Goodin <br...@gmail.com>]

you CAN CAN CAN CAN CAN build offline when in a car, or on a plane, when at
your home, or on a lome, when in a humjick, or on lumberjack. It is still
possible to build offline with maven.

We install programs every day that help us be more productive. Maven is just
that. Once you install it. iBATIS like many many many other projects will
build with a click.

I'm sure there are plenty of tools that you use that aren't one-click. You
are exaggerating. If you cared that much about it you wouldn't be on
Windows. ;-)

Brandon

On 2/13/07, Clinton Begin <cl...@gmail.com> wrote:
>
> >>I think there is a bit of hostility here.
>
> I don't sense any hostility...just strong opinions.
>
> >>  If you don't have an internet connection then you are in a sad sad sad
> state
>
> Except for those who like to work with or on our framework while on an
> airplane...or a bus or a train....laptops are great things.
> Unfortunately wireless networks are not yet ubiquitous.  Not everyone
> works from home.  :-)
>
> >> I believe that self contained build are overrated as well.
>
> Completely disagree.  When I can't build it with one click, I generally
> toss it.
>
> >> all the unnecessary anger
>
> There's no anger man.  Just constructive debate.  I hope we never
> start to sound like those chipmunks on the Bugs Bunny show...."No no
> no...you're the wonderful one."  :-)
>
> Clinton
>
>
>
> On 2/13/07, Brandon Goodin <br...@gmail.com> wrote:
> > Thanks all for the feedback,
> >
> > I think there is a bit of hostility here. It was probably flamed by
> Larry's
> > hate comments earlier. We can all forgive each other can't we and keep
> > loving?
> >
> > To address some of the points:
> >
> > RE: internet connectivity...
> > If you don't have an internet connection then you are in a sad sad sad
> state
> > and i'd like to know how you got ahold of ibatis in the first place.
> >
> > RE: self contained build
> > I believe that self contained build are overrated as well. As long as
> you
> > have the jars (which maven will download for you). Then you are golden.
> It's
> > really quite simple.
> >
> > RE: site generation
> > I'm fine with our current site. Are we using ant in our build to create
> it?
> > If not, then it's a non-issue cuz i'm not advocating maven being site
> > generator.
> >
> > Anyway, let me suggest that you guys let me write the pom and we'll see
> if
> > all the unnecessary anger and hype is really worth the raise in blood
> > pressure.
> >
> > Brandon Goodin
> >
> >
> >  On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
> > > No, you can do off-line builds with maven.
> > >
> > > mvn -o install
> > >
> > > Larry
> > >
> > >
> > > On 2/13/07, Slava Imeshev <vi...@viewtier.com> wrote:
> > > > My preference for a build to be self-contained and not to require
> > > > to go out to run.
> > > >
> > > >
> > > > Using Maven will prevent those having no Internet connection
> > > > from building iBATIS.
> > > >
> > > > Regards,
> > > >
> > > > Slava Imeshev
> > > > www.viewtier.com
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: "Brandon Goodin" <br...@gmail.com>
> > > > To: < dev@ibatis.apache.org>
> > > > Cc: <lm...@apache.org>
> > > > Sent: Tuesday, February 13, 2007 9:16 AM
> > > > Subject: Re: Maven for Build?
> > > >
> > > >
> > > > > I can finish the pom that i have right now so that it mirrors the
> > > > > functionality of the current ant script. It won't hurt anything to
> > have the
> > > > > pom in the repo.
> > > > >
> > > > > Brandon
> > > > >
> > > > > On 2/13/07, Jeff Butler < jeffgbutler@gmail.com> wrote:
> > > > > >
> > > > > > I'm open to maven for the iBATIS build.  It would help a certain
> > group of
> > > > > > our users to get iBATIS into the Maven repository.  Also - I
> don't
> > think you
> > > > > > have to generate the site with maven, we could just use it for
> the
> > build.
> > > > > >
> > > > > > I've looked at it for Abator.  Abator doesn't have much of a
> > dependancy
> > > > > > issue for the build (just needs a JRE and Ant), but the test
> phase
> > is a
> > > > > > different story.  Abator testing is difficult because the tests
> are
> > not so
> > > > > > much an Abator itself, but on the code that Abator
> generates.  So
> > the build
> > > > > > looks like this:
> > > > > >
> > > > > > 1. Build the JAR
> > > > > > 2. Run a few tests (only three or four right now)
> > > > > > 3. Build a test DB
> > > > > > 4. Generate code against the DB
> > > > > > 5. Compile the generated code and also a set of tests against
> the
> > > > > > generated code
> > > > > > 6. Run the tests on the generated code (several hundred)
> > > > > >
> > > > > > The Abater build also behaves differently if you're running wuth
> JSE
> > 5 or
> > > > > > not - there are more tests if you are using a Java 5 JDK.
> > > > > >
> > > > > > The build.xml for Abator is more complex than I'd like because
> of
> > all this
> > > > > > - so if Maven could help, then I'd be open to using for Abator
> too.
> > > > > >
> > > > > > Jeff Butler
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
> > > > > > >
> > > > > > > I like the idea - it makes the checkout faster, and "mvn
> > idea:idea" is
> > > > > > > worth it's weight in gold, and our current build.xml is a
> bugger,
> > I
> > > > > > > hate it.
> > > > > > >
> > > > > > > So, I wonder if we can skin the generated site to make it not
> look
> > > > > > > like crap^H^H^H^H every other maven generated site. :-)
> > > > > > >
> > > > > > > Larry
> > > > > > >
> > > > > > >
> > > > > > > On 2/12/07, Brandon Goodin < brandon.goodin@gmail.com > wrote:
> > > > > > > > Hey Guys,
> > > > > > > >
> > > > > > > > I wanted to throw a bone out to everyone and ask the
> question
> > "Should
> > > > > > > we use
> > > > > > > > Maven for our build?". I put together a POM today that makes
> use
> > of
> > > > > > > the
> > > > > > > > current iBATIS SQL Map structures. It is pretty darn simple
> and
> > > > > > > required
> > > > > > > > very little effort. The largest amount of my time was spent
> > > > > > > refactoring the
> > > > > > > > TestCL (Test Classloader) to use the current thread
> classloader
> > as a
> > > > > > > parent
> > > > > > > > due to some incompatibilities with how Maven runs it's test.
> > That
> > > > > > > aside, I
> > > > > > > > was surprised at how little effort it took to get the iBATIS
> > SQLMap
> > > > > > > jar
> > > > > > > > built. Plus, Because of the dependency management of Maven I
> was
> > able
> > > > > > > to
> > > > > > > > avoid having to use the oscache devsrc for oscache and avoid
> > using the
> > > > > > > > devlib jars. I only used Maven to build the Data Mapper/SQL
> Map.
> > I
> > > > > > > wasn't
> > > > > > > > familiar enough with Abator's build process to wire in Maven
> for
> > it.
> > > > > > > >
> > > > > > > > Benefits:
> > > > > > > >
> > > > > > > > * I thought it would be good to aid in reducing the
> complexity
> > of our
> > > > > > > > current build/deploy. If we want to provide our jars to the
> > Maven
> > > > > > > crowd we
> > > > > > > > would be tasking the deploying member with taking the final
> jar
> > built
> > > > > > > from
> > > > > > > > ant and running deploy:deploy-file for it. I have to say
> that I
> > looked
> > > > > > > > through our release process and I really wouldn't want to
> add
> > yet
> > > > > > > another
> > > > > > > > step. Seems like maven can consolidate this for us.
> > > > > > > > * We can run ant from within Maven if we so desire to
> continue
> > > > > > > performing
> > > > > > > > tasks that maven doesn't provide for.
> > > > > > > >
> > > > > > > > Additional benefits, thoughts, or concerns?
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Brandon
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
>

Re: Maven for Build?

[Clinton Begin <cl...@gmail.com>]

>>I think there is a bit of hostility here.

I don't sense any hostility...just strong opinions.

>>  If you don't have an internet connection then you are in a sad sad sad state

Except for those who like to work with or on our framework while on an
airplane...or a bus or a train....laptops are great things.
Unfortunately wireless networks are not yet ubiquitous.  Not everyone
works from home.  :-)

>> I believe that self contained build are overrated as well.

Completely disagree.  When I can't build it with one click, I generally toss it.

>> all the unnecessary anger

There's no anger man.  Just constructive debate.  I hope we never
start to sound like those chipmunks on the Bugs Bunny show...."No no
no...you're the wonderful one."  :-)

Clinton



On 2/13/07, Brandon Goodin <br...@gmail.com> wrote:
> Thanks all for the feedback,
>
> I think there is a bit of hostility here. It was probably flamed by Larry's
> hate comments earlier. We can all forgive each other can't we and keep
> loving?
>
> To address some of the points:
>
> RE: internet connectivity...
> If you don't have an internet connection then you are in a sad sad sad state
> and i'd like to know how you got ahold of ibatis in the first place.
>
> RE: self contained build
> I believe that self contained build are overrated as well. As long as you
> have the jars (which maven will download for you). Then you are golden. It's
> really quite simple.
>
> RE: site generation
> I'm fine with our current site. Are we using ant in our build to create it?
> If not, then it's a non-issue cuz i'm not advocating maven being site
> generator.
>
> Anyway, let me suggest that you guys let me write the pom and we'll see if
> all the unnecessary anger and hype is really worth the raise in blood
> pressure.
>
> Brandon Goodin
>
>
>  On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
> > No, you can do off-line builds with maven.
> >
> > mvn -o install
> >
> > Larry
> >
> >
> > On 2/13/07, Slava Imeshev <vi...@viewtier.com> wrote:
> > > My preference for a build to be self-contained and not to require
> > > to go out to run.
> > >
> > >
> > > Using Maven will prevent those having no Internet connection
> > > from building iBATIS.
> > >
> > > Regards,
> > >
> > > Slava Imeshev
> > > www.viewtier.com
> > >
> > >
> > > ----- Original Message -----
> > > From: "Brandon Goodin" <br...@gmail.com>
> > > To: < dev@ibatis.apache.org>
> > > Cc: <lm...@apache.org>
> > > Sent: Tuesday, February 13, 2007 9:16 AM
> > > Subject: Re: Maven for Build?
> > >
> > >
> > > > I can finish the pom that i have right now so that it mirrors the
> > > > functionality of the current ant script. It won't hurt anything to
> have the
> > > > pom in the repo.
> > > >
> > > > Brandon
> > > >
> > > > On 2/13/07, Jeff Butler < jeffgbutler@gmail.com> wrote:
> > > > >
> > > > > I'm open to maven for the iBATIS build.  It would help a certain
> group of
> > > > > our users to get iBATIS into the Maven repository.  Also - I don't
> think you
> > > > > have to generate the site with maven, we could just use it for the
> build.
> > > > >
> > > > > I've looked at it for Abator.  Abator doesn't have much of a
> dependancy
> > > > > issue for the build (just needs a JRE and Ant), but the test phase
> is a
> > > > > different story.  Abator testing is difficult because the tests are
> not so
> > > > > much an Abator itself, but on the code that Abator generates.  So
> the build
> > > > > looks like this:
> > > > >
> > > > > 1. Build the JAR
> > > > > 2. Run a few tests (only three or four right now)
> > > > > 3. Build a test DB
> > > > > 4. Generate code against the DB
> > > > > 5. Compile the generated code and also a set of tests against the
> > > > > generated code
> > > > > 6. Run the tests on the generated code (several hundred)
> > > > >
> > > > > The Abater build also behaves differently if you're running wuth JSE
> 5 or
> > > > > not - there are more tests if you are using a Java 5 JDK.
> > > > >
> > > > > The build.xml for Abator is more complex than I'd like because of
> all this
> > > > > - so if Maven could help, then I'd be open to using for Abator too.
> > > > >
> > > > > Jeff Butler
> > > > >
> > > > >
> > > > >
> > > > > On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
> > > > > >
> > > > > > I like the idea - it makes the checkout faster, and "mvn
> idea:idea" is
> > > > > > worth it's weight in gold, and our current build.xml is a bugger,
> I
> > > > > > hate it.
> > > > > >
> > > > > > So, I wonder if we can skin the generated site to make it not look
> > > > > > like crap^H^H^H^H every other maven generated site. :-)
> > > > > >
> > > > > > Larry
> > > > > >
> > > > > >
> > > > > > On 2/12/07, Brandon Goodin < brandon.goodin@gmail.com > wrote:
> > > > > > > Hey Guys,
> > > > > > >
> > > > > > > I wanted to throw a bone out to everyone and ask the question
> "Should
> > > > > > we use
> > > > > > > Maven for our build?". I put together a POM today that makes use
> of
> > > > > > the
> > > > > > > current iBATIS SQL Map structures. It is pretty darn simple and
> > > > > > required
> > > > > > > very little effort. The largest amount of my time was spent
> > > > > > refactoring the
> > > > > > > TestCL (Test Classloader) to use the current thread classloader
> as a
> > > > > > parent
> > > > > > > due to some incompatibilities with how Maven runs it's test.
> That
> > > > > > aside, I
> > > > > > > was surprised at how little effort it took to get the iBATIS
> SQLMap
> > > > > > jar
> > > > > > > built. Plus, Because of the dependency management of Maven I was
> able
> > > > > > to
> > > > > > > avoid having to use the oscache devsrc for oscache and avoid
> using the
> > > > > > > devlib jars. I only used Maven to build the Data Mapper/SQL Map.
> I
> > > > > > wasn't
> > > > > > > familiar enough with Abator's build process to wire in Maven for
> it.
> > > > > > >
> > > > > > > Benefits:
> > > > > > >
> > > > > > > * I thought it would be good to aid in reducing the complexity
> of our
> > > > > > > current build/deploy. If we want to provide our jars to the
> Maven
> > > > > > crowd we
> > > > > > > would be tasking the deploying member with taking the final jar
> built
> > > > > > from
> > > > > > > ant and running deploy:deploy-file for it. I have to say that I
> looked
> > > > > > > through our release process and I really wouldn't want to add
> yet
> > > > > > another
> > > > > > > step. Seems like maven can consolidate this for us.
> > > > > > > * We can run ant from within Maven if we so desire to continue
> > > > > > performing
> > > > > > > tasks that maven doesn't provide for.
> > > > > > >
> > > > > > > Additional benefits, thoughts, or concerns?
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Brandon
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
>

Re: Maven for Build?

[Larry Meadors <lm...@apache.org>]

DUDE IM GONNA KCIK YER BUTT!!

Larry


PS: It's fun to be silly in the middle of the week - unlike those
struts stiffs who can only giggle on Fridays. ;-)


On 2/13/07, Clinton Begin <cl...@gmail.com> wrote:
> > It only affects people who build iBATIS from source,
>
> So it will only make the developers' lives a living hell.
>
> KIDDING!!!! (does that count as provocation?)
>
> > With the Struts releases, we also include all the JARs needed to build
> > the product, which people can install locally.
>
> That would be perfect!
>
> Clinton
>
> On 2/13/07, Ted Husted <hu...@apache.org> wrote:
> > On 2/13/07, Slava Imeshev <vi...@viewtier.com> wrote:
> > >
> > > > RE: internet connectivity...
> > > > If you don't have an internet connection then you are in a sad sad state
> > > > and i'd like to know how you got ahold of ibatis in the first place.
> > >
> > >  Not allowing people using iBATIS will slow its adoption.
> >
> > This has very little to do with iBATIS adoption. It only affects
> > people who build iBATIS from source, instead of using the prebuilt
> > JARs. The vast majority of people adopting iBATIS only use the
> > prebuilt GA JARs.
> >
> > With the Struts releases, we also include all the JARs needed to build
> > the product, which people can install locally.
> >
> > -Ted.
> >
>

Re: Maven for Build?

[Paul Benedict <pb...@apache.org>]

I can offer some assistance if necessary.

Ted Husted wrote:
> On 2/13/07, Clinton Begin <cl...@gmail.com> wrote:
>> > With the Struts releases, we also include all the JARs needed to build
>> > the product, which people can install locally.
>>
>> That would be perfect!
> 
> Feel free to steal from what Wendy setup for us. It's mostly a
> blackbox to me. I know where to put the release versions, list the
> dependencies, how to run "mvn install", but that's nearly the extent
> of my Maven knowledge -- and I've been the release manager of late :)
> 
> -Ted.
> 

Re: Maven for Build?

[Brandon Goodin <br...@gmail.com>]

Thanks for the info Ted.

Brandon

On 2/13/07, Ted Husted <hu...@apache.org> wrote:
>
> On 2/13/07, Clinton Begin <cl...@gmail.com> wrote:
> > > With the Struts releases, we also include all the JARs needed to build
> > > the product, which people can install locally.
> >
> > That would be perfect!
>
> Feel free to steal from what Wendy setup for us. It's mostly a
> blackbox to me. I know where to put the release versions, list the
> dependencies, how to run "mvn install", but that's nearly the extent
> of my Maven knowledge -- and I've been the release manager of late :)
>
> -Ted.
>

Re: Maven for Build?

[Ted Husted <hu...@apache.org>]

On 2/13/07, Clinton Begin <cl...@gmail.com> wrote:
> > With the Struts releases, we also include all the JARs needed to build
> > the product, which people can install locally.
>
> That would be perfect!

Feel free to steal from what Wendy setup for us. It's mostly a
blackbox to me. I know where to put the release versions, list the
dependencies, how to run "mvn install", but that's nearly the extent
of my Maven knowledge -- and I've been the release manager of late :)

-Ted.

Re: Maven for Build?

[Clinton Begin <cl...@gmail.com>]

> It only affects people who build iBATIS from source,

So it will only make the developers' lives a living hell.

KIDDING!!!! (does that count as provocation?)

> With the Struts releases, we also include all the JARs needed to build
> the product, which people can install locally.

That would be perfect!

Clinton

On 2/13/07, Ted Husted <hu...@apache.org> wrote:
> On 2/13/07, Slava Imeshev <vi...@viewtier.com> wrote:
> >
> > > RE: internet connectivity...
> > > If you don't have an internet connection then you are in a sad sad state
> > > and i'd like to know how you got ahold of ibatis in the first place.
> >
> >  Not allowing people using iBATIS will slow its adoption.
>
> This has very little to do with iBATIS adoption. It only affects
> people who build iBATIS from source, instead of using the prebuilt
> JARs. The vast majority of people adopting iBATIS only use the
> prebuilt GA JARs.
>
> With the Struts releases, we also include all the JARs needed to build
> the product, which people can install locally.
>
> -Ted.
>

Re: Maven for Build?

[Ted Husted <hu...@apache.org>]

On 2/13/07, Slava Imeshev <vi...@viewtier.com> wrote:
>
> > RE: internet connectivity...
> > If you don't have an internet connection then you are in a sad sad state
> > and i'd like to know how you got ahold of ibatis in the first place.
>
>  Not allowing people using iBATIS will slow its adoption.

This has very little to do with iBATIS adoption. It only affects
people who build iBATIS from source, instead of using the prebuilt
JARs. The vast majority of people adopting iBATIS only use the
prebuilt GA JARs.

With the Struts releases, we also include all the JARs needed to build
the product, which people can install locally.

-Ted.

Re: Maven for Build?

[Brandon Goodin <br...@gmail.com>]

I just have to ask if any of you have actually used maven or is this just a
"fear somethign different debate"? If you have questions about whether Maven
can do something then ask a question rather than plant assertions that are
not accurate.

Brandon

On 2/13/07, Slava Imeshev <vi...@viewtier.com> wrote:
>
>
> > RE: internet connectivity...
> > If you don't have an internet connection then you are in a sad sad state
> > and i'd like to know how you got ahold of ibatis in the first place.
>
> Not allowing people using iBATIS will slow its adoption.
>
> You may work in a strict security environment that prohibits
> certain connections. Fetching something from outside may
> be disastrous in such environments.
>
> > RE: self contained build
> > I believe that self contained build are overrated as well. As long as
> you
> > have the jars (which maven will download for you). Then you are golden.
>
> Actually, no. Basic change management requires knowing what
> makes your product.
>
>
> > Anyway, let me suggest that you guys let me write the pom and we'll see
> if
> > all the unnecessary anger and hype is really worth the raise in blood
> > pressure.
>
> Boredom shouldn't drive technology decisions, common sense should.
>
> In any case, Viewtier will continue running Continuous Integration
> for iBATIS. Just let me know if there are changes:
>
> http://parabuild.viewtier.com:8080/parabuild/index.htm?displaygroupid=7
>
>
> Regards,
>
> Slava Imeshev
> www.viewtier.com
>
>

Re: Maven for Build?

[Slava Imeshev <vi...@viewtier.com>]

> RE: internet connectivity...
> If you don't have an internet connection then you are in a sad sad state
> and i'd like to know how you got ahold of ibatis in the first place.

 Not allowing people using iBATIS will slow its adoption.

You may work in a strict security environment that prohibits 
certain connections. Fetching something from outside may 
be disastrous in such environments.

> RE: self contained build
> I believe that self contained build are overrated as well. As long as you
> have the jars (which maven will download for you). Then you are golden. 

Actually, no. Basic change management requires knowing what 
makes your product.


> Anyway, let me suggest that you guys let me write the pom and we'll see if
> all the unnecessary anger and hype is really worth the raise in blood
> pressure.

Boredom shouldn't drive technology decisions, common sense should.

In any case, Viewtier will continue running Continuous Integration
for iBATIS. Just let me know if there are changes:

http://parabuild.viewtier.com:8080/parabuild/index.htm?displaygroupid=7


Regards,

Slava Imeshev
www.viewtier.com

Re: Maven for Build?

[Brandon Goodin <br...@gmail.com>]

Thanks all for the feedback,

I think there is a bit of hostility here. It was probably flamed by Larry's
hate comments earlier. We can all forgive each other can't we and keep
loving?

To address some of the points:

RE: internet connectivity...
If you don't have an internet connection then you are in a sad sad sad state
and i'd like to know how you got ahold of ibatis in the first place.

RE: self contained build
I believe that self contained build are overrated as well. As long as you
have the jars (which maven will download for you). Then you are golden. It's
really quite simple.

RE: site generation
I'm fine with our current site. Are we using ant in our build to create it?
If not, then it's a non-issue cuz i'm not advocating maven being site
generator.

Anyway, let me suggest that you guys let me write the pom and we'll see if
all the unnecessary anger and hype is really worth the raise in blood
pressure.

Brandon Goodin

On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
>
> No, you can do off-line builds with maven.
>
> mvn -o install
>
> Larry
>
>
> On 2/13/07, Slava Imeshev <vi...@viewtier.com> wrote:
> > My preference for a build to be self-contained and not to require
> > to go out to run.
> >
> >
> > Using Maven will prevent those having no Internet connection
> > from building iBATIS.
> >
> > Regards,
> >
> > Slava Imeshev
> > www.viewtier.com
> >
> >
> > ----- Original Message -----
> > From: "Brandon Goodin" <br...@gmail.com>
> > To: <de...@ibatis.apache.org>
> > Cc: <lm...@apache.org>
> > Sent: Tuesday, February 13, 2007 9:16 AM
> > Subject: Re: Maven for Build?
> >
> >
> > > I can finish the pom that i have right now so that it mirrors the
> > > functionality of the current ant script. It won't hurt anything to
> have the
> > > pom in the repo.
> > >
> > > Brandon
> > >
> > > On 2/13/07, Jeff Butler <je...@gmail.com> wrote:
> > > >
> > > > I'm open to maven for the iBATIS build.  It would help a certain
> group of
> > > > our users to get iBATIS into the Maven repository.  Also - I don't
> think you
> > > > have to generate the site with maven, we could just use it for the
> build.
> > > >
> > > > I've looked at it for Abator.  Abator doesn't have much of a
> dependancy
> > > > issue for the build (just needs a JRE and Ant), but the test phase
> is a
> > > > different story.  Abator testing is difficult because the tests are
> not so
> > > > much an Abator itself, but on the code that Abator generates.  So
> the build
> > > > looks like this:
> > > >
> > > > 1. Build the JAR
> > > > 2. Run a few tests (only three or four right now)
> > > > 3. Build a test DB
> > > > 4. Generate code against the DB
> > > > 5. Compile the generated code and also a set of tests against the
> > > > generated code
> > > > 6. Run the tests on the generated code (several hundred)
> > > >
> > > > The Abater build also behaves differently if you're running wuth JSE
> 5 or
> > > > not - there are more tests if you are using a Java 5 JDK.
> > > >
> > > > The build.xml for Abator is more complex than I'd like because of
> all this
> > > > - so if Maven could help, then I'd be open to using for Abator too.
> > > >
> > > > Jeff Butler
> > > >
> > > >
> > > >
> > > > On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
> > > > >
> > > > > I like the idea - it makes the checkout faster, and "mvn
> idea:idea" is
> > > > > worth it's weight in gold, and our current build.xml is a bugger,
> I
> > > > > hate it.
> > > > >
> > > > > So, I wonder if we can skin the generated site to make it not look
> > > > > like crap^H^H^H^H every other maven generated site. :-)
> > > > >
> > > > > Larry
> > > > >
> > > > >
> > > > > On 2/12/07, Brandon Goodin < brandon.goodin@gmail.com> wrote:
> > > > > > Hey Guys,
> > > > > >
> > > > > > I wanted to throw a bone out to everyone and ask the question
> "Should
> > > > > we use
> > > > > > Maven for our build?". I put together a POM today that makes use
> of
> > > > > the
> > > > > > current iBATIS SQL Map structures. It is pretty darn simple and
> > > > > required
> > > > > > very little effort. The largest amount of my time was spent
> > > > > refactoring the
> > > > > > TestCL (Test Classloader) to use the current thread classloader
> as a
> > > > > parent
> > > > > > due to some incompatibilities with how Maven runs it's test.
> That
> > > > > aside, I
> > > > > > was surprised at how little effort it took to get the iBATIS
> SQLMap
> > > > > jar
> > > > > > built. Plus, Because of the dependency management of Maven I was
> able
> > > > > to
> > > > > > avoid having to use the oscache devsrc for oscache and avoid
> using the
> > > > > > devlib jars. I only used Maven to build the Data Mapper/SQL Map.
> I
> > > > > wasn't
> > > > > > familiar enough with Abator's build process to wire in Maven for
> it.
> > > > > >
> > > > > > Benefits:
> > > > > >
> > > > > > * I thought it would be good to aid in reducing the complexity
> of our
> > > > > > current build/deploy. If we want to provide our jars to the
> Maven
> > > > > crowd we
> > > > > > would be tasking the deploying member with taking the final jar
> built
> > > > > from
> > > > > > ant and running deploy:deploy-file for it. I have to say that I
> looked
> > > > > > through our release process and I really wouldn't want to add
> yet
> > > > > another
> > > > > > step. Seems like maven can consolidate this for us.
> > > > > > * We can run ant from within Maven if we so desire to continue
> > > > > performing
> > > > > > tasks that maven doesn't provide for.
> > > > > >
> > > > > > Additional benefits, thoughts, or concerns?
> > > > > >
> > > > > > Thanks,
> > > > > > Brandon
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
>

Re: Maven for Build?

[Larry Meadors <lm...@apache.org>]

No, you can do off-line builds with maven.

mvn -o install

Larry


On 2/13/07, Slava Imeshev <vi...@viewtier.com> wrote:
> My preference for a build to be self-contained and not to require
> to go out to run.
>
>
> Using Maven will prevent those having no Internet connection
> from building iBATIS.
>
> Regards,
>
> Slava Imeshev
> www.viewtier.com
>
>
> ----- Original Message -----
> From: "Brandon Goodin" <br...@gmail.com>
> To: <de...@ibatis.apache.org>
> Cc: <lm...@apache.org>
> Sent: Tuesday, February 13, 2007 9:16 AM
> Subject: Re: Maven for Build?
>
>
> > I can finish the pom that i have right now so that it mirrors the
> > functionality of the current ant script. It won't hurt anything to have the
> > pom in the repo.
> >
> > Brandon
> >
> > On 2/13/07, Jeff Butler <je...@gmail.com> wrote:
> > >
> > > I'm open to maven for the iBATIS build.  It would help a certain group of
> > > our users to get iBATIS into the Maven repository.  Also - I don't think you
> > > have to generate the site with maven, we could just use it for the build.
> > >
> > > I've looked at it for Abator.  Abator doesn't have much of a dependancy
> > > issue for the build (just needs a JRE and Ant), but the test phase is a
> > > different story.  Abator testing is difficult because the tests are not so
> > > much an Abator itself, but on the code that Abator generates.  So the build
> > > looks like this:
> > >
> > > 1. Build the JAR
> > > 2. Run a few tests (only three or four right now)
> > > 3. Build a test DB
> > > 4. Generate code against the DB
> > > 5. Compile the generated code and also a set of tests against the
> > > generated code
> > > 6. Run the tests on the generated code (several hundred)
> > >
> > > The Abater build also behaves differently if you're running wuth JSE 5 or
> > > not - there are more tests if you are using a Java 5 JDK.
> > >
> > > The build.xml for Abator is more complex than I'd like because of all this
> > > - so if Maven could help, then I'd be open to using for Abator too.
> > >
> > > Jeff Butler
> > >
> > >
> > >
> > > On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
> > > >
> > > > I like the idea - it makes the checkout faster, and "mvn idea:idea" is
> > > > worth it's weight in gold, and our current build.xml is a bugger, I
> > > > hate it.
> > > >
> > > > So, I wonder if we can skin the generated site to make it not look
> > > > like crap^H^H^H^H every other maven generated site. :-)
> > > >
> > > > Larry
> > > >
> > > >
> > > > On 2/12/07, Brandon Goodin < brandon.goodin@gmail.com> wrote:
> > > > > Hey Guys,
> > > > >
> > > > > I wanted to throw a bone out to everyone and ask the question "Should
> > > > we use
> > > > > Maven for our build?". I put together a POM today that makes use of
> > > > the
> > > > > current iBATIS SQL Map structures. It is pretty darn simple and
> > > > required
> > > > > very little effort. The largest amount of my time was spent
> > > > refactoring the
> > > > > TestCL (Test Classloader) to use the current thread classloader as a
> > > > parent
> > > > > due to some incompatibilities with how Maven runs it's test. That
> > > > aside, I
> > > > > was surprised at how little effort it took to get the iBATIS SQLMap
> > > > jar
> > > > > built. Plus, Because of the dependency management of Maven I was able
> > > > to
> > > > > avoid having to use the oscache devsrc for oscache and avoid using the
> > > > > devlib jars. I only used Maven to build the Data Mapper/SQL Map. I
> > > > wasn't
> > > > > familiar enough with Abator's build process to wire in Maven for it.
> > > > >
> > > > > Benefits:
> > > > >
> > > > > * I thought it would be good to aid in reducing the complexity of our
> > > > > current build/deploy. If we want to provide our jars to the Maven
> > > > crowd we
> > > > > would be tasking the deploying member with taking the final jar built
> > > > from
> > > > > ant and running deploy:deploy-file for it. I have to say that I looked
> > > > > through our release process and I really wouldn't want to add yet
> > > > another
> > > > > step. Seems like maven can consolidate this for us.
> > > > > * We can run ant from within Maven if we so desire to continue
> > > > performing
> > > > > tasks that maven doesn't provide for.
> > > > >
> > > > > Additional benefits, thoughts, or concerns?
> > > > >
> > > > > Thanks,
> > > > > Brandon
> > > > >
> > > >
> > >
> > >
> >
>

Re: Maven for Build?

[Larry Meadors <lm...@apache.org>]

Apologies in advance: I don't mean to sound like an ass.

This argument just seems like we are saying "Let's hack together
something even more convoluted to do do something simple so we don't
have to use something new."

Other than "it's different", "ant works fine" and "I hate maven", I
have heard nothing that resembles a reason to not use maven.

Larry


On 2/13/07, Slava Imeshev <vi...@viewtier.com> wrote:
>
> ----- Original Message -----
> From: "Jeff Butler" <je...@gmail.com>
> To: <de...@ibatis.apache.org>
> Sent: Tuesday, February 13, 2007 9:28 AM
> Subject: Re: Maven for Build?
>
>
> > +1 for Ant as the primary build.
> >
> > But could we get iBATIS into the Maven repository somehow so we could stop
> > all the whining from Maven mavens?  :-)
>
> Exactly.
>
> ant send-to-maven-repository
>
> Regards,
>
> Slava Imeshev
>
>

Re: Maven for Build?

[Slava Imeshev <vi...@viewtier.com>]

----- Original Message ----- 
From: "Jeff Butler" <je...@gmail.com>
To: <de...@ibatis.apache.org>
Sent: Tuesday, February 13, 2007 9:28 AM
Subject: Re: Maven for Build?


> +1 for Ant as the primary build.
> 
> But could we get iBATIS into the Maven repository somehow so we could stop
> all the whining from Maven mavens?  :-)

Exactly.

ant send-to-maven-repository

Regards,

Slava Imeshev

Re: Maven for Build?

[Jeff Butler <je...@gmail.com>]

+1 for Ant as the primary build.

But could we get iBATIS into the Maven repository somehow so we could stop
all the whining from Maven mavens?  :-)

Jeff Butler


On 2/13/07, Clinton Begin <cl...@gmail.com> wrote:
>
> +1 for Slava...oh wait, you all know my opinion already.   Do I only get
> one?
>
> On 2/13/07, Slava Imeshev <vi...@viewtier.com> wrote:
> > My preference for a build to be self-contained and not to require
> > to go out to run.
> >
> >
> > Using Maven will prevent those having no Internet connection
> > from building iBATIS.
> >
> > Regards,
> >
> > Slava Imeshev
> > www.viewtier.com
> >
> >
> > ----- Original Message -----
> > From: "Brandon Goodin" <br...@gmail.com>
> > To: <de...@ibatis.apache.org>
> > Cc: <lm...@apache.org>
> > Sent: Tuesday, February 13, 2007 9:16 AM
> > Subject: Re: Maven for Build?
> >
> >
> > > I can finish the pom that i have right now so that it mirrors the
> > > functionality of the current ant script. It won't hurt anything to
> have the
> > > pom in the repo.
> > >
> > > Brandon
> > >
> > > On 2/13/07, Jeff Butler <je...@gmail.com> wrote:
> > > >
> > > > I'm open to maven for the iBATIS build.  It would help a certain
> group of
> > > > our users to get iBATIS into the Maven repository.  Also - I don't
> think you
> > > > have to generate the site with maven, we could just use it for the
> build.
> > > >
> > > > I've looked at it for Abator.  Abator doesn't have much of a
> dependancy
> > > > issue for the build (just needs a JRE and Ant), but the test phase
> is a
> > > > different story.  Abator testing is difficult because the tests are
> not so
> > > > much an Abator itself, but on the code that Abator generates.  So
> the build
> > > > looks like this:
> > > >
> > > > 1. Build the JAR
> > > > 2. Run a few tests (only three or four right now)
> > > > 3. Build a test DB
> > > > 4. Generate code against the DB
> > > > 5. Compile the generated code and also a set of tests against the
> > > > generated code
> > > > 6. Run the tests on the generated code (several hundred)
> > > >
> > > > The Abater build also behaves differently if you're running wuth JSE
> 5 or
> > > > not - there are more tests if you are using a Java 5 JDK.
> > > >
> > > > The build.xml for Abator is more complex than I'd like because of
> all this
> > > > - so if Maven could help, then I'd be open to using for Abator too.
> > > >
> > > > Jeff Butler
> > > >
> > > >
> > > >
> > > > On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
> > > > >
> > > > > I like the idea - it makes the checkout faster, and "mvn
> idea:idea" is
> > > > > worth it's weight in gold, and our current build.xml is a bugger,
> I
> > > > > hate it.
> > > > >
> > > > > So, I wonder if we can skin the generated site to make it not look
> > > > > like crap^H^H^H^H every other maven generated site. :-)
> > > > >
> > > > > Larry
> > > > >
> > > > >
> > > > > On 2/12/07, Brandon Goodin < brandon.goodin@gmail.com> wrote:
> > > > > > Hey Guys,
> > > > > >
> > > > > > I wanted to throw a bone out to everyone and ask the question
> "Should
> > > > > we use
> > > > > > Maven for our build?". I put together a POM today that makes use
> of
> > > > > the
> > > > > > current iBATIS SQL Map structures. It is pretty darn simple and
> > > > > required
> > > > > > very little effort. The largest amount of my time was spent
> > > > > refactoring the
> > > > > > TestCL (Test Classloader) to use the current thread classloader
> as a
> > > > > parent
> > > > > > due to some incompatibilities with how Maven runs it's test.
> That
> > > > > aside, I
> > > > > > was surprised at how little effort it took to get the iBATIS
> SQLMap
> > > > > jar
> > > > > > built. Plus, Because of the dependency management of Maven I was
> able
> > > > > to
> > > > > > avoid having to use the oscache devsrc for oscache and avoid
> using the
> > > > > > devlib jars. I only used Maven to build the Data Mapper/SQL Map.
> I
> > > > > wasn't
> > > > > > familiar enough with Abator's build process to wire in Maven for
> it.
> > > > > >
> > > > > > Benefits:
> > > > > >
> > > > > > * I thought it would be good to aid in reducing the complexity
> of our
> > > > > > current build/deploy. If we want to provide our jars to the
> Maven
> > > > > crowd we
> > > > > > would be tasking the deploying member with taking the final jar
> built
> > > > > from
> > > > > > ant and running deploy:deploy-file for it. I have to say that I
> looked
> > > > > > through our release process and I really wouldn't want to add
> yet
> > > > > another
> > > > > > step. Seems like maven can consolidate this for us.
> > > > > > * We can run ant from within Maven if we so desire to continue
> > > > > performing
> > > > > > tasks that maven doesn't provide for.
> > > > > >
> > > > > > Additional benefits, thoughts, or concerns?
> > > > > >
> > > > > > Thanks,
> > > > > > Brandon
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
>

Re: Maven for Build?

[Clinton Begin <cl...@gmail.com>]

+1 for Slava...oh wait, you all know my opinion already.   Do I only get one?

On 2/13/07, Slava Imeshev <vi...@viewtier.com> wrote:
> My preference for a build to be self-contained and not to require
> to go out to run.
>
>
> Using Maven will prevent those having no Internet connection
> from building iBATIS.
>
> Regards,
>
> Slava Imeshev
> www.viewtier.com
>
>
> ----- Original Message -----
> From: "Brandon Goodin" <br...@gmail.com>
> To: <de...@ibatis.apache.org>
> Cc: <lm...@apache.org>
> Sent: Tuesday, February 13, 2007 9:16 AM
> Subject: Re: Maven for Build?
>
>
> > I can finish the pom that i have right now so that it mirrors the
> > functionality of the current ant script. It won't hurt anything to have the
> > pom in the repo.
> >
> > Brandon
> >
> > On 2/13/07, Jeff Butler <je...@gmail.com> wrote:
> > >
> > > I'm open to maven for the iBATIS build.  It would help a certain group of
> > > our users to get iBATIS into the Maven repository.  Also - I don't think you
> > > have to generate the site with maven, we could just use it for the build.
> > >
> > > I've looked at it for Abator.  Abator doesn't have much of a dependancy
> > > issue for the build (just needs a JRE and Ant), but the test phase is a
> > > different story.  Abator testing is difficult because the tests are not so
> > > much an Abator itself, but on the code that Abator generates.  So the build
> > > looks like this:
> > >
> > > 1. Build the JAR
> > > 2. Run a few tests (only three or four right now)
> > > 3. Build a test DB
> > > 4. Generate code against the DB
> > > 5. Compile the generated code and also a set of tests against the
> > > generated code
> > > 6. Run the tests on the generated code (several hundred)
> > >
> > > The Abater build also behaves differently if you're running wuth JSE 5 or
> > > not - there are more tests if you are using a Java 5 JDK.
> > >
> > > The build.xml for Abator is more complex than I'd like because of all this
> > > - so if Maven could help, then I'd be open to using for Abator too.
> > >
> > > Jeff Butler
> > >
> > >
> > >
> > > On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
> > > >
> > > > I like the idea - it makes the checkout faster, and "mvn idea:idea" is
> > > > worth it's weight in gold, and our current build.xml is a bugger, I
> > > > hate it.
> > > >
> > > > So, I wonder if we can skin the generated site to make it not look
> > > > like crap^H^H^H^H every other maven generated site. :-)
> > > >
> > > > Larry
> > > >
> > > >
> > > > On 2/12/07, Brandon Goodin < brandon.goodin@gmail.com> wrote:
> > > > > Hey Guys,
> > > > >
> > > > > I wanted to throw a bone out to everyone and ask the question "Should
> > > > we use
> > > > > Maven for our build?". I put together a POM today that makes use of
> > > > the
> > > > > current iBATIS SQL Map structures. It is pretty darn simple and
> > > > required
> > > > > very little effort. The largest amount of my time was spent
> > > > refactoring the
> > > > > TestCL (Test Classloader) to use the current thread classloader as a
> > > > parent
> > > > > due to some incompatibilities with how Maven runs it's test. That
> > > > aside, I
> > > > > was surprised at how little effort it took to get the iBATIS SQLMap
> > > > jar
> > > > > built. Plus, Because of the dependency management of Maven I was able
> > > > to
> > > > > avoid having to use the oscache devsrc for oscache and avoid using the
> > > > > devlib jars. I only used Maven to build the Data Mapper/SQL Map. I
> > > > wasn't
> > > > > familiar enough with Abator's build process to wire in Maven for it.
> > > > >
> > > > > Benefits:
> > > > >
> > > > > * I thought it would be good to aid in reducing the complexity of our
> > > > > current build/deploy. If we want to provide our jars to the Maven
> > > > crowd we
> > > > > would be tasking the deploying member with taking the final jar built
> > > > from
> > > > > ant and running deploy:deploy-file for it. I have to say that I looked
> > > > > through our release process and I really wouldn't want to add yet
> > > > another
> > > > > step. Seems like maven can consolidate this for us.
> > > > > * We can run ant from within Maven if we so desire to continue
> > > > performing
> > > > > tasks that maven doesn't provide for.
> > > > >
> > > > > Additional benefits, thoughts, or concerns?
> > > > >
> > > > > Thanks,
> > > > > Brandon
> > > > >
> > > >
> > >
> > >
> >
>

Re: Maven for Build?

[Slava Imeshev <vi...@viewtier.com>]

My preference for a build to be self-contained and not to require 
to go out to run.


Using Maven will prevent those having no Internet connection 
from building iBATIS. 

Regards,

Slava Imeshev
www.viewtier.com


----- Original Message ----- 
From: "Brandon Goodin" <br...@gmail.com>
To: <de...@ibatis.apache.org>
Cc: <lm...@apache.org>
Sent: Tuesday, February 13, 2007 9:16 AM
Subject: Re: Maven for Build?


> I can finish the pom that i have right now so that it mirrors the
> functionality of the current ant script. It won't hurt anything to have the
> pom in the repo.
> 
> Brandon
> 
> On 2/13/07, Jeff Butler <je...@gmail.com> wrote:
> >
> > I'm open to maven for the iBATIS build.  It would help a certain group of
> > our users to get iBATIS into the Maven repository.  Also - I don't think you
> > have to generate the site with maven, we could just use it for the build.
> >
> > I've looked at it for Abator.  Abator doesn't have much of a dependancy
> > issue for the build (just needs a JRE and Ant), but the test phase is a
> > different story.  Abator testing is difficult because the tests are not so
> > much an Abator itself, but on the code that Abator generates.  So the build
> > looks like this:
> >
> > 1. Build the JAR
> > 2. Run a few tests (only three or four right now)
> > 3. Build a test DB
> > 4. Generate code against the DB
> > 5. Compile the generated code and also a set of tests against the
> > generated code
> > 6. Run the tests on the generated code (several hundred)
> >
> > The Abater build also behaves differently if you're running wuth JSE 5 or
> > not - there are more tests if you are using a Java 5 JDK.
> >
> > The build.xml for Abator is more complex than I'd like because of all this
> > - so if Maven could help, then I'd be open to using for Abator too.
> >
> > Jeff Butler
> >
> >
> >
> > On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
> > >
> > > I like the idea - it makes the checkout faster, and "mvn idea:idea" is
> > > worth it's weight in gold, and our current build.xml is a bugger, I
> > > hate it.
> > >
> > > So, I wonder if we can skin the generated site to make it not look
> > > like crap^H^H^H^H every other maven generated site. :-)
> > >
> > > Larry
> > >
> > >
> > > On 2/12/07, Brandon Goodin < brandon.goodin@gmail.com> wrote:
> > > > Hey Guys,
> > > >
> > > > I wanted to throw a bone out to everyone and ask the question "Should
> > > we use
> > > > Maven for our build?". I put together a POM today that makes use of
> > > the
> > > > current iBATIS SQL Map structures. It is pretty darn simple and
> > > required
> > > > very little effort. The largest amount of my time was spent
> > > refactoring the
> > > > TestCL (Test Classloader) to use the current thread classloader as a
> > > parent
> > > > due to some incompatibilities with how Maven runs it's test. That
> > > aside, I
> > > > was surprised at how little effort it took to get the iBATIS SQLMap
> > > jar
> > > > built. Plus, Because of the dependency management of Maven I was able
> > > to
> > > > avoid having to use the oscache devsrc for oscache and avoid using the
> > > > devlib jars. I only used Maven to build the Data Mapper/SQL Map. I
> > > wasn't
> > > > familiar enough with Abator's build process to wire in Maven for it.
> > > >
> > > > Benefits:
> > > >
> > > > * I thought it would be good to aid in reducing the complexity of our
> > > > current build/deploy. If we want to provide our jars to the Maven
> > > crowd we
> > > > would be tasking the deploying member with taking the final jar built
> > > from
> > > > ant and running deploy:deploy-file for it. I have to say that I looked
> > > > through our release process and I really wouldn't want to add yet
> > > another
> > > > step. Seems like maven can consolidate this for us.
> > > > * We can run ant from within Maven if we so desire to continue
> > > performing
> > > > tasks that maven doesn't provide for.
> > > >
> > > > Additional benefits, thoughts, or concerns?
> > > >
> > > > Thanks,
> > > > Brandon
> > > >
> > >
> >
> >
> 

Re: Maven for Build?

[Brandon Goodin <br...@gmail.com>]

I can finish the pom that i have right now so that it mirrors the
functionality of the current ant script. It won't hurt anything to have the
pom in the repo.

Brandon

On 2/13/07, Jeff Butler <je...@gmail.com> wrote:
>
> I'm open to maven for the iBATIS build.  It would help a certain group of
> our users to get iBATIS into the Maven repository.  Also - I don't think you
> have to generate the site with maven, we could just use it for the build.
>
> I've looked at it for Abator.  Abator doesn't have much of a dependancy
> issue for the build (just needs a JRE and Ant), but the test phase is a
> different story.  Abator testing is difficult because the tests are not so
> much an Abator itself, but on the code that Abator generates.  So the build
> looks like this:
>
> 1. Build the JAR
> 2. Run a few tests (only three or four right now)
> 3. Build a test DB
> 4. Generate code against the DB
> 5. Compile the generated code and also a set of tests against the
> generated code
> 6. Run the tests on the generated code (several hundred)
>
> The Abater build also behaves differently if you're running wuth JSE 5 or
> not - there are more tests if you are using a Java 5 JDK.
>
> The build.xml for Abator is more complex than I'd like because of all this
> - so if Maven could help, then I'd be open to using for Abator too.
>
> Jeff Butler
>
>
>
> On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
> >
> > I like the idea - it makes the checkout faster, and "mvn idea:idea" is
> > worth it's weight in gold, and our current build.xml is a bugger, I
> > hate it.
> >
> > So, I wonder if we can skin the generated site to make it not look
> > like crap^H^H^H^H every other maven generated site. :-)
> >
> > Larry
> >
> >
> > On 2/12/07, Brandon Goodin < brandon.goodin@gmail.com> wrote:
> > > Hey Guys,
> > >
> > > I wanted to throw a bone out to everyone and ask the question "Should
> > we use
> > > Maven for our build?". I put together a POM today that makes use of
> > the
> > > current iBATIS SQL Map structures. It is pretty darn simple and
> > required
> > > very little effort. The largest amount of my time was spent
> > refactoring the
> > > TestCL (Test Classloader) to use the current thread classloader as a
> > parent
> > > due to some incompatibilities with how Maven runs it's test. That
> > aside, I
> > > was surprised at how little effort it took to get the iBATIS SQLMap
> > jar
> > > built. Plus, Because of the dependency management of Maven I was able
> > to
> > > avoid having to use the oscache devsrc for oscache and avoid using the
> > > devlib jars. I only used Maven to build the Data Mapper/SQL Map. I
> > wasn't
> > > familiar enough with Abator's build process to wire in Maven for it.
> > >
> > > Benefits:
> > >
> > > * I thought it would be good to aid in reducing the complexity of our
> > > current build/deploy. If we want to provide our jars to the Maven
> > crowd we
> > > would be tasking the deploying member with taking the final jar built
> > from
> > > ant and running deploy:deploy-file for it. I have to say that I looked
> > > through our release process and I really wouldn't want to add yet
> > another
> > > step. Seems like maven can consolidate this for us.
> > > * We can run ant from within Maven if we so desire to continue
> > performing
> > > tasks that maven doesn't provide for.
> > >
> > > Additional benefits, thoughts, or concerns?
> > >
> > > Thanks,
> > > Brandon
> > >
> >
>
>

Re: Maven for Build?

[Jeff Butler <je...@gmail.com>]

I'm open to maven for the iBATIS build.  It would help a certain group of
our users to get iBATIS into the Maven repository.  Also - I don't think you
have to generate the site with maven, we could just use it for the build.

I've looked at it for Abator.  Abator doesn't have much of a dependancy
issue for the build (just needs a JRE and Ant), but the test phase is a
different story.  Abator testing is difficult because the tests are not so
much an Abator itself, but on the code that Abator generates.  So the build
looks like this:

1. Build the JAR
2. Run a few tests (only three or four right now)
3. Build a test DB
4. Generate code against the DB
5. Compile the generated code and also a set of tests against the generated
code
6. Run the tests on the generated code (several hundred)

The Abater build also behaves differently if you're running wuth JSE 5 or
not - there are more tests if you are using a Java 5 JDK.

The build.xml for Abator is more complex than I'd like because of all this -
so if Maven could help, then I'd be open to using for Abator too.

Jeff Butler



On 2/13/07, Larry Meadors <lm...@apache.org> wrote:
>
> I like the idea - it makes the checkout faster, and "mvn idea:idea" is
> worth it's weight in gold, and our current build.xml is a bugger, I
> hate it.
>
> So, I wonder if we can skin the generated site to make it not look
> like crap^H^H^H^H every other maven generated site. :-)
>
> Larry
>
>
> On 2/12/07, Brandon Goodin <br...@gmail.com> wrote:
> > Hey Guys,
> >
> > I wanted to throw a bone out to everyone and ask the question "Should we
> use
> > Maven for our build?". I put together a POM today that makes use of the
> > current iBATIS SQL Map structures. It is pretty darn simple and required
> > very little effort. The largest amount of my time was spent refactoring
> the
> > TestCL (Test Classloader) to use the current thread classloader as a
> parent
> > due to some incompatibilities with how Maven runs it's test. That aside,
> I
> > was surprised at how little effort it took to get the iBATIS SQLMap jar
> > built. Plus, Because of the dependency management of Maven I was able to
> > avoid having to use the oscache devsrc for oscache and avoid using the
> > devlib jars. I only used Maven to build the Data Mapper/SQL Map. I
> wasn't
> > familiar enough with Abator's build process to wire in Maven for it.
> >
> > Benefits:
> >
> > * I thought it would be good to aid in reducing the complexity of our
> > current build/deploy. If we want to provide our jars to the Maven crowd
> we
> > would be tasking the deploying member with taking the final jar built
> from
> > ant and running deploy:deploy-file for it. I have to say that I looked
> > through our release process and I really wouldn't want to add yet
> another
> > step. Seems like maven can consolidate this for us.
> > * We can run ant from within Maven if we so desire to continue
> performing
> > tasks that maven doesn't provide for.
> >
> > Additional benefits, thoughts, or concerns?
> >
> > Thanks,
> > Brandon
> >
>

Re: Maven for Build?

[Larry Meadors <lm...@apache.org>]

I like the idea - it makes the checkout faster, and "mvn idea:idea" is
worth it's weight in gold, and our current build.xml is a bugger, I
hate it.

So, I wonder if we can skin the generated site to make it not look
like crap^H^H^H^H every other maven generated site. :-)

Larry


On 2/12/07, Brandon Goodin <br...@gmail.com> wrote:
> Hey Guys,
>
> I wanted to throw a bone out to everyone and ask the question "Should we use
> Maven for our build?". I put together a POM today that makes use of the
> current iBATIS SQL Map structures. It is pretty darn simple and required
> very little effort. The largest amount of my time was spent refactoring the
> TestCL (Test Classloader) to use the current thread classloader as a parent
> due to some incompatibilities with how Maven runs it's test. That aside, I
> was surprised at how little effort it took to get the iBATIS SQLMap jar
> built. Plus, Because of the dependency management of Maven I was able to
> avoid having to use the oscache devsrc for oscache and avoid using the
> devlib jars. I only used Maven to build the Data Mapper/SQL Map. I wasn't
> familiar enough with Abator's build process to wire in Maven for it.
>
> Benefits:
>
> * I thought it would be good to aid in reducing the complexity of our
> current build/deploy. If we want to provide our jars to the Maven crowd we
> would be tasking the deploying member with taking the final jar built from
> ant and running deploy:deploy-file for it. I have to say that I looked
> through our release process and I really wouldn't want to add yet another
> step. Seems like maven can consolidate this for us.
> * We can run ant from within Maven if we so desire to continue performing
> tasks that maven doesn't provide for.
>
> Additional benefits, thoughts, or concerns?
>
> Thanks,
> Brandon
>