You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by Clinton Begin <cl...@gmail.com> on 2007/02/14 17:14:14 UTC
[VOTE] Support for Maven (impacts Java version only)
Hi all,
It strikes me that there was enough discussion around the Maven build
to warrant an official vote for Maven support.
+2 => Replace our Ant build entirely with a Maven build.
+1 => Support Maven by including a Maven build alongside our Ant build.
0 => Don't care or I don't know enough about Maven to decide.
-1 => Do not support maven.
Cheers,
Clinton
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Clinton Begin <cl...@gmail.com>.
Votes never close and can be changed, so don't worry about the timing.
Clinton
On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> I think this is a bit premature. My intention was to show a working
> comparison so that this decision could be made in an informed manner.
>
> Brandon
>
> On 2/14/07, Clinton Begin <cl...@gmail.com> wrote:
> > Hi all,
> >
> > It strikes me that there was enough discussion around the Maven build
> > to warrant an official vote for Maven support.
> >
> > +2 => Replace our Ant build entirely with a Maven build.
> >
> > +1 => Support Maven by including a Maven build alongside our Ant build.
> >
> > 0 => Don't care or I don't know enough about Maven to decide.
> >
> > -1 => Do not support maven.
> >
> > Cheers,
> > Clinton
> >
>
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Brandon Goodin <br...@gmail.com>.
I think this is a bit premature. My intention was to show a working
comparison so that this decision could be made in an informed manner.
Brandon
On 2/14/07, Clinton Begin <cl...@gmail.com> wrote:
>
> Hi all,
>
> It strikes me that there was enough discussion around the Maven build
> to warrant an official vote for Maven support.
>
> +2 => Replace our Ant build entirely with a Maven build.
>
> +1 => Support Maven by including a Maven build alongside our Ant build.
>
> 0 => Don't care or I don't know enough about Maven to decide.
>
> -1 => Do not support maven.
>
> Cheers,
> Clinton
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Brandon Goodin <br...@gmail.com>.
Currently, if we want to publish the jars to the maven repo the release
manager would need to make sure the current pom.xml compiles and runs all
tests successfully with "mvn clean install". You'd run the normal ant build
as well to generate the jar we want to deploy to a maven repository. Then we
would run a "mvn deploy:deploy-file" and provide all the necessary
parameters, which would include the pom to insure our dependency information
is correct. (
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html).
This would create the needed structures/meta for the jars to function
appropriately in the maven repo.
If we are using maven for the whole build then it would require mvn
deploy:deploy .
After each of these process you would scp the results to the
people.apache.org:/x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository.
It is also possible to have both of these automatically copy to the
people.apache.org location.
Brandon
On 2/14/07, Jeff Butler <jeffgbutler@gmail.com > wrote:
>
> Yes - I should have asked that question with more subtlety. I guess the
> bottom line is that it is *possible* to get the jars to the repository
> without doing a maven build, but doing a maven build makes it much easier to
> publish to the repository. And our history shows that we are unlikely to
> get the jars to the repository with the build process we are using now.
> Right?
>
> Jeff
>
>
>
> On 2/14/07, Larry Meadors <lmeadors@apache.org > wrote:
> >
> > IMO, that is like "Can we clean a toilet with a toothbrush?"
> >
> > Yes, we can, but who wants to offer up their toothbrush? Not me! :-)
> >
> > The question to me is:
> >
> > "Can we get the iBATIS jars to the maven repository without doing a
> > maven build, and is it the right way to do it?"
> >
> > Yes we can, but no it's not.
> >
> > Larry
> >
> >
> > On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> > > "Can we get the iBATIS jars to the maven repository without doing a
> > maven
> > > build?"
> > >
> > > Yes
> > >
> > >
> > > On 2/14/07, Jeff Butler < jeffgbutler@gmail.com> wrote:
> > > >
> > > > In my own little perfect world, I'm -1. The iBATIS ant build is so
> > simple
> > > now - I hate to see it mucked up just to supply the Maven meta-bs as
> > Clinton
> > > so eloquently put it.
> > > >
> > > > However, I would like to see the iBATIS jars in the Maven repository
> > - if
> > > for no other reason than to help those who can't figure out how to set
> > a
> > > classpath without a tool. If a maven build makes that possible then I
> > guess
> > > I'd be +2, but reluctantly.
> > > >
> > > > I think that supporting both Ant and Maven is problematical - seems
> > like
> > > we should just pick one for simplicity going forward.
> > > >
> > > > So I guess I can't give a single vote. Can someone definitively
> > answer
> > > this question: Can we get the iBATIS jars to the maven repository
> > without
> > > doing a maven build? That's the key point for me.
> > > >
> > > > Jeff Butler
> > > >
> > > >
> > > >
> > > > On 2/14/07, Clinton Begin < clinton.begin@gmail.com > wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > It strikes me that there was enough discussion around the Maven
> > build
> > > > > to warrant an official vote for Maven support.
> > > > >
> > > > > +2 => Replace our Ant build entirely with a Maven build.
> > > > >
> > > > > +1 => Support Maven by including a Maven build alongside our Ant
> > build.
> > > > >
> > > > > 0 => Don't care or I don't know enough about Maven to decide.
> > > > >
> > > > > -1 => Do not support maven.
> > > > >
> > > > > Cheers,
> > > > > Clinton
> > > > >
> > > >
> > > >
> > >
> > >
> >
>
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Larry Meadors <lm...@apache.org>.
If past history is any indication of the future, that is correct.
:)
Larry
On 2/14/07, Jeff Butler <je...@gmail.com> wrote:
> Yes - I should have asked that question with more subtlety. I guess the
> bottom line is that it is *possible* to get the jars to the repository
> without doing a maven build, but doing a maven build makes it much easier to
> publish to the repository. And our history shows that we are unlikely to
> get the jars to the repository with the build process we are using now.
> Right?
>
> Jeff
>
>
>
>
> On 2/14/07, Larry Meadors <lm...@apache.org> wrote:
> > IMO, that is like "Can we clean a toilet with a toothbrush?"
> >
> > Yes, we can, but who wants to offer up their toothbrush? Not me! :-)
> >
> > The question to me is:
> >
> > "Can we get the iBATIS jars to the maven repository without doing a
> > maven build, and is it the right way to do it?"
> >
> > Yes we can, but no it's not.
> >
> > Larry
> >
> >
> > On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> > > "Can we get the iBATIS jars to the maven repository without doing a
> maven
> > > build?"
> > >
> > > Yes
> > >
> > >
> > > On 2/14/07, Jeff Butler < jeffgbutler@gmail.com> wrote:
> > > >
> > > > In my own little perfect world, I'm -1. The iBATIS ant build is so
> simple
> > > now - I hate to see it mucked up just to supply the Maven meta-bs as
> Clinton
> > > so eloquently put it.
> > > >
> > > > However, I would like to see the iBATIS jars in the Maven repository -
> if
> > > for no other reason than to help those who can't figure out how to set a
> > > classpath without a tool. If a maven build makes that possible then I
> guess
> > > I'd be +2, but reluctantly.
> > > >
> > > > I think that supporting both Ant and Maven is problematical - seems
> like
> > > we should just pick one for simplicity going forward.
> > > >
> > > > So I guess I can't give a single vote. Can someone definitively
> answer
> > > this question: Can we get the iBATIS jars to the maven repository
> without
> > > doing a maven build? That's the key point for me.
> > > >
> > > > Jeff Butler
> > > >
> > > >
> > > >
> > > > On 2/14/07, Clinton Begin < clinton.begin@gmail.com > wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > It strikes me that there was enough discussion around the Maven
> build
> > > > > to warrant an official vote for Maven support.
> > > > >
> > > > > +2 => Replace our Ant build entirely with a Maven build.
> > > > >
> > > > > +1 => Support Maven by including a Maven build alongside our Ant
> build.
> > > > >
> > > > > 0 => Don't care or I don't know enough about Maven to decide.
> > > > >
> > > > > -1 => Do not support maven.
> > > > >
> > > > > Cheers,
> > > > > Clinton
> > > > >
> > > >
> > > >
> > >
> > >
> >
>
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Brandon Goodin <br...@gmail.com>.
My original statement was that IDEA ran fine. I was just goofing something
on the Ant build.sh... not sure what. It wasn't a big deal because IDEA ran
it fine.
Brandon
On 2/15/07, Clinton Begin <cl...@gmail.com> wrote:
>
> In IDEA, right click on the Ant build file in the Ant sidebar. Choose
> Properties. Choose the Additional Classpath Tab. Select Add All In
> Directory, choose the devlib directory.
>
> For command line, just dump all the devlib jars into your ant/lib folder.
>
> That will ensure all dependencies are met for the Ant plugins (just
> JUnit, Optional, and JDK tools).
>
> Clinton
>
> On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> > "We don't require a shell script now."
> >
> > True. I used the ant script from IDEA the other day because i got tired
> of
> > fiddling around with the shell script. I didn't go too deep. But I was
> > having problems getting it running on the mac. Likely something i didn't
> > have configured right.
> >
> > The nice thing about Maven is that it handles all the runtime
> > loading/downloading of plugins that it requires to operate based upon
> the
> > pom. So, in the end we can have shell scripts to make the builds one
> click
> > builds, but we won't have to worry about setting up classpaths for it in
> the
> > scripts.
> >
> > If you want you can download the latest maven 2
> > (http://maven.apache.org/download.html). Follow the simple
> > setup at the bottom of that page. Then update to the latest ibatis and
> run
> > 'mvn clean install' from the command line of the project root. See how
> it
> > goes. That command will build the ibatis jar and run the unit tests.
> >
> > Brandon
> >
> >
> > On 2/14/07, Clinton Begin <cl...@gmail.com> wrote:
> > > We don't require a shell script now. The .bat and .sh files are
> > > optional. You're perfectly welcome to install Ant separately (like
> > > you will have to with Maven) and just call ant from within the /build
> > > directory.
> > >
> > > Clinton
> > >
> > > On 2/14/07, Nathan Maves <na...@gmail.com> wrote:
> > > > +1 and my vote counts!
> > > >
> > > > Speaking from personal experience I have wanted to move to a new
> build
> > tool
> > > > for a while. While most of you will pay though the nose for the
> latest
> > M$
> > > > Vista, I run on unix machine. The use of shell scripts for build
> > purposes
> > > > is not a good xplatform solution.
> > > >
> > > > Just from a quick glance Maven seems to make somewhat time consuming
> > tasks
> > > > in Ant easy.
> > > >
> > > > Lets do this.
> > > >
> > > > Nathan
> > > >
> > > >
> > > > On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> > > > > The broader purpose of this is not just to see if we can get jars
> into
> > > > maven but rather to see if maven can simplify our build/release
> process.
> > If
> > > > you have a one liner then that is great. I'd love to see it.
> > > > >
> > > > > Brandon
> > > > >
> > > > >
> > > > >
> > > > > On 2/14/07, Slava Imeshev < vimeshev@viewtier.com> wrote:
> > > > > > I seriously doubt that this would require switching to Maven
> > > > > > build.
> > > > > >
> > > > > > I cannot speak for a global catalog, but adding an item built
> > > > > > with Ant to a local Maven repository is a one-liner.
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Slava Imeshev
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: "Jeff Butler" <je...@gmail.com>
> > > > > > To: < dev@ibatis.apache.org>; < lmeadors@apache.org>
> > > > > > Sent: Wednesday, February 14, 2007 10:09 AM
> > > > > > Subject: Re: [VOTE] Support for Maven (impacts Java version
> only)
> > > > > >
> > > > > >
> > > > > > > Yes - I should have asked that question with more subtlety. I
> > guess
> > > > the
> > > > > > > bottom line is that it is *possible* to get the jars to the
> > repository
> > > > > > > without doing a maven build, but doing a maven build makes it
> much
> > > > easier to
> > > > > > > publish to the repository. And our history shows that we are
> > unlikely
> > > > to
> > > > > > > get the jars to the repository with the build process we are
> using
> > > > now.
> > > > > > > Right?
> > > > > > >
> > > > > > > Jeff
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 2/14/07, Larry Meadors < lmeadors@apache.org > wrote:
> > > > > > > >
> > > > > > > > IMO, that is like "Can we clean a toilet with a toothbrush?"
> > > > > > > >
> > > > > > > > Yes, we can, but who wants to offer up their toothbrush? Not
> me!
> > :-)
> > > > > > > >
> > > > > > > > The question to me is:
> > > > > > > >
> > > > > > > > "Can we get the iBATIS jars to the maven repository without
> > doing a
> > > > > > > > maven build, and is it the right way to do it?"
> > > > > > > >
> > > > > > > > Yes we can, but no it's not.
> > > > > > > >
> > > > > > > > Larry
> > > > > > > >
> > > > > > > >
> > > > > > > > On 2/14/07, Brandon Goodin <brandon.goodin@gmail.com >
> wrote:
> > > > > > > > > "Can we get the iBATIS jars to the maven repository
> without
> > doing
> > > > a
> > > > > > > > maven
> > > > > > > > > build?"
> > > > > > > > >
> > > > > > > > > Yes
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 2/14/07, Jeff Butler < jeffgbutler@gmail.com > wrote:
> > > > > > > > > >
> > > > > > > > > > In my own little perfect world, I'm -1. The iBATIS ant
> > build is
> > > > so
> > > > > > > > simple
> > > > > > > > > now - I hate to see it mucked up just to supply the Maven
> > meta-bs
> > > > as
> > > > > > > > Clinton
> > > > > > > > > so eloquently put it.
> > > > > > > > > >
> > > > > > > > > > However, I would like to see the iBATIS jars in the
> Maven
> > > > repository -
> > > > > > > > if
> > > > > > > > > for no other reason than to help those who can't figure
> out
> > how to
> > > > set a
> > > > > > > > > classpath without a tool. If a maven build makes that
> > possible
> > > > then I
> > > > > > > > guess
> > > > > > > > > I'd be +2, but reluctantly.
> > > > > > > > > >
> > > > > > > > > > I think that supporting both Ant and Maven is
> problematical
> > -
> > > > seems
> > > > > > > > like
> > > > > > > > > we should just pick one for simplicity going forward.
> > > > > > > > > >
> > > > > > > > > > So I guess I can't give a single vote. Can someone
> > definitively
> > > > > > > > answer
> > > > > > > > > this question: Can we get the iBATIS jars to the maven
> > repository
> > > > > > > > without
> > > > > > > > > doing a maven build? That's the key point for me.
> > > > > > > > > >
> > > > > > > > > > Jeff Butler
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On 2/14/07, Clinton Begin < clinton.begin@gmail.com >
> wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi all,
> > > > > > > > > > >
> > > > > > > > > > > It strikes me that there was enough discussion around
> the
> > > > Maven
> > > > > > > > build
> > > > > > > > > > > to warrant an official vote for Maven support.
> > > > > > > > > > >
> > > > > > > > > > > +2 => Replace our Ant build entirely with a Maven
> build.
> > > > > > > > > > >
> > > > > > > > > > > +1 => Support Maven by including a Maven build
> alongside
> > our
> > > > Ant
> > > > > > > > build.
> > > > > > > > > > >
> > > > > > > > > > > 0 => Don't care or I don't know enough about Maven to
> > decide.
> > > > > > > > > > >
> > > > > > > > > > > -1 => Do not support maven.
> > > > > > > > > > >
> > > > > > > > > > > Cheers,
> > > > > > > > > > > Clinton
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> >
> >
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Clinton Begin <cl...@gmail.com>.
In IDEA, right click on the Ant build file in the Ant sidebar. Choose
Properties. Choose the Additional Classpath Tab. Select Add All In
Directory, choose the devlib directory.
For command line, just dump all the devlib jars into your ant/lib folder.
That will ensure all dependencies are met for the Ant plugins (just
JUnit, Optional, and JDK tools).
Clinton
On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> "We don't require a shell script now."
>
> True. I used the ant script from IDEA the other day because i got tired of
> fiddling around with the shell script. I didn't go too deep. But I was
> having problems getting it running on the mac. Likely something i didn't
> have configured right.
>
> The nice thing about Maven is that it handles all the runtime
> loading/downloading of plugins that it requires to operate based upon the
> pom. So, in the end we can have shell scripts to make the builds one click
> builds, but we won't have to worry about setting up classpaths for it in the
> scripts.
>
> If you want you can download the latest maven 2
> (http://maven.apache.org/download.html). Follow the simple
> setup at the bottom of that page. Then update to the latest ibatis and run
> 'mvn clean install' from the command line of the project root. See how it
> goes. That command will build the ibatis jar and run the unit tests.
>
> Brandon
>
>
> On 2/14/07, Clinton Begin <cl...@gmail.com> wrote:
> > We don't require a shell script now. The .bat and .sh files are
> > optional. You're perfectly welcome to install Ant separately (like
> > you will have to with Maven) and just call ant from within the /build
> > directory.
> >
> > Clinton
> >
> > On 2/14/07, Nathan Maves <na...@gmail.com> wrote:
> > > +1 and my vote counts!
> > >
> > > Speaking from personal experience I have wanted to move to a new build
> tool
> > > for a while. While most of you will pay though the nose for the latest
> M$
> > > Vista, I run on unix machine. The use of shell scripts for build
> purposes
> > > is not a good xplatform solution.
> > >
> > > Just from a quick glance Maven seems to make somewhat time consuming
> tasks
> > > in Ant easy.
> > >
> > > Lets do this.
> > >
> > > Nathan
> > >
> > >
> > > On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> > > > The broader purpose of this is not just to see if we can get jars into
> > > maven but rather to see if maven can simplify our build/release process.
> If
> > > you have a one liner then that is great. I'd love to see it.
> > > >
> > > > Brandon
> > > >
> > > >
> > > >
> > > > On 2/14/07, Slava Imeshev < vimeshev@viewtier.com> wrote:
> > > > > I seriously doubt that this would require switching to Maven
> > > > > build.
> > > > >
> > > > > I cannot speak for a global catalog, but adding an item built
> > > > > with Ant to a local Maven repository is a one-liner.
> > > > >
> > > > > Regards,
> > > > >
> > > > > Slava Imeshev
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Jeff Butler" <je...@gmail.com>
> > > > > To: < dev@ibatis.apache.org>; < lmeadors@apache.org>
> > > > > Sent: Wednesday, February 14, 2007 10:09 AM
> > > > > Subject: Re: [VOTE] Support for Maven (impacts Java version only)
> > > > >
> > > > >
> > > > > > Yes - I should have asked that question with more subtlety. I
> guess
> > > the
> > > > > > bottom line is that it is *possible* to get the jars to the
> repository
> > > > > > without doing a maven build, but doing a maven build makes it much
> > > easier to
> > > > > > publish to the repository. And our history shows that we are
> unlikely
> > > to
> > > > > > get the jars to the repository with the build process we are using
> > > now.
> > > > > > Right?
> > > > > >
> > > > > > Jeff
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 2/14/07, Larry Meadors < lmeadors@apache.org > wrote:
> > > > > > >
> > > > > > > IMO, that is like "Can we clean a toilet with a toothbrush?"
> > > > > > >
> > > > > > > Yes, we can, but who wants to offer up their toothbrush? Not me!
> :-)
> > > > > > >
> > > > > > > The question to me is:
> > > > > > >
> > > > > > > "Can we get the iBATIS jars to the maven repository without
> doing a
> > > > > > > maven build, and is it the right way to do it?"
> > > > > > >
> > > > > > > Yes we can, but no it's not.
> > > > > > >
> > > > > > > Larry
> > > > > > >
> > > > > > >
> > > > > > > On 2/14/07, Brandon Goodin <brandon.goodin@gmail.com > wrote:
> > > > > > > > "Can we get the iBATIS jars to the maven repository without
> doing
> > > a
> > > > > > > maven
> > > > > > > > build?"
> > > > > > > >
> > > > > > > > Yes
> > > > > > > >
> > > > > > > >
> > > > > > > > On 2/14/07, Jeff Butler < jeffgbutler@gmail.com > wrote:
> > > > > > > > >
> > > > > > > > > In my own little perfect world, I'm -1. The iBATIS ant
> build is
> > > so
> > > > > > > simple
> > > > > > > > now - I hate to see it mucked up just to supply the Maven
> meta-bs
> > > as
> > > > > > > Clinton
> > > > > > > > so eloquently put it.
> > > > > > > > >
> > > > > > > > > However, I would like to see the iBATIS jars in the Maven
> > > repository -
> > > > > > > if
> > > > > > > > for no other reason than to help those who can't figure out
> how to
> > > set a
> > > > > > > > classpath without a tool. If a maven build makes that
> possible
> > > then I
> > > > > > > guess
> > > > > > > > I'd be +2, but reluctantly.
> > > > > > > > >
> > > > > > > > > I think that supporting both Ant and Maven is problematical
> -
> > > seems
> > > > > > > like
> > > > > > > > we should just pick one for simplicity going forward.
> > > > > > > > >
> > > > > > > > > So I guess I can't give a single vote. Can someone
> definitively
> > > > > > > answer
> > > > > > > > this question: Can we get the iBATIS jars to the maven
> repository
> > > > > > > without
> > > > > > > > doing a maven build? That's the key point for me.
> > > > > > > > >
> > > > > > > > > Jeff Butler
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 2/14/07, Clinton Begin < clinton.begin@gmail.com > wrote:
> > > > > > > > >
> > > > > > > > > > Hi all,
> > > > > > > > > >
> > > > > > > > > > It strikes me that there was enough discussion around the
> > > Maven
> > > > > > > build
> > > > > > > > > > to warrant an official vote for Maven support.
> > > > > > > > > >
> > > > > > > > > > +2 => Replace our Ant build entirely with a Maven build.
> > > > > > > > > >
> > > > > > > > > > +1 => Support Maven by including a Maven build alongside
> our
> > > Ant
> > > > > > > build.
> > > > > > > > > >
> > > > > > > > > > 0 => Don't care or I don't know enough about Maven to
> decide.
> > > > > > > > > >
> > > > > > > > > > -1 => Do not support maven.
> > > > > > > > > >
> > > > > > > > > > Cheers,
> > > > > > > > > > Clinton
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
>
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Brandon Goodin <br...@gmail.com>.
"We don't require a shell script now."
True. I used the ant script from IDEA the other day because i got tired of
fiddling around with the shell script. I didn't go too deep. But I was
having problems getting it running on the mac. Likely something i didn't
have configured right.
The nice thing about Maven is that it handles all the runtime
loading/downloading of plugins that it requires to operate based upon the
pom. So, in the end we can have shell scripts to make the builds one click
builds, but we won't have to worry about setting up classpaths for it in the
scripts.
If you want you can download the latest maven 2 (
http://maven.apache.org/download.html). Follow the simple setup at the
bottom of that page. Then update to the latest ibatis and run 'mvn clean
install' from the command line of the project root. See how it goes. That
command will build the ibatis jar and run the unit tests.
Brandon
On 2/14/07, Clinton Begin <cl...@gmail.com> wrote:
>
> We don't require a shell script now. The .bat and .sh files are
> optional. You're perfectly welcome to install Ant separately (like
> you will have to with Maven) and just call ant from within the /build
> directory.
>
> Clinton
>
> On 2/14/07, Nathan Maves <na...@gmail.com> wrote:
> > +1 and my vote counts!
> >
> > Speaking from personal experience I have wanted to move to a new build
> tool
> > for a while. While most of you will pay though the nose for the latest
> M$
> > Vista, I run on unix machine. The use of shell scripts for build
> purposes
> > is not a good xplatform solution.
> >
> > Just from a quick glance Maven seems to make somewhat time consuming
> tasks
> > in Ant easy.
> >
> > Lets do this.
> >
> > Nathan
> >
> >
> > On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> > > The broader purpose of this is not just to see if we can get jars into
> > maven but rather to see if maven can simplify our build/release process.
> If
> > you have a one liner then that is great. I'd love to see it.
> > >
> > > Brandon
> > >
> > >
> > >
> > > On 2/14/07, Slava Imeshev < vimeshev@viewtier.com> wrote:
> > > > I seriously doubt that this would require switching to Maven
> > > > build.
> > > >
> > > > I cannot speak for a global catalog, but adding an item built
> > > > with Ant to a local Maven repository is a one-liner.
> > > >
> > > > Regards,
> > > >
> > > > Slava Imeshev
> > > >
> > > > ----- Original Message -----
> > > > From: "Jeff Butler" <je...@gmail.com>
> > > > To: < dev@ibatis.apache.org>; < lmeadors@apache.org>
> > > > Sent: Wednesday, February 14, 2007 10:09 AM
> > > > Subject: Re: [VOTE] Support for Maven (impacts Java version only)
> > > >
> > > >
> > > > > Yes - I should have asked that question with more subtlety. I
> guess
> > the
> > > > > bottom line is that it is *possible* to get the jars to the
> repository
> > > > > without doing a maven build, but doing a maven build makes it much
> > easier to
> > > > > publish to the repository. And our history shows that we are
> unlikely
> > to
> > > > > get the jars to the repository with the build process we are using
> > now.
> > > > > Right?
> > > > >
> > > > > Jeff
> > > > >
> > > > >
> > > > >
> > > > > On 2/14/07, Larry Meadors < lmeadors@apache.org > wrote:
> > > > > >
> > > > > > IMO, that is like "Can we clean a toilet with a toothbrush?"
> > > > > >
> > > > > > Yes, we can, but who wants to offer up their toothbrush? Not me!
> :-)
> > > > > >
> > > > > > The question to me is:
> > > > > >
> > > > > > "Can we get the iBATIS jars to the maven repository without
> doing a
> > > > > > maven build, and is it the right way to do it?"
> > > > > >
> > > > > > Yes we can, but no it's not.
> > > > > >
> > > > > > Larry
> > > > > >
> > > > > >
> > > > > > On 2/14/07, Brandon Goodin <brandon.goodin@gmail.com > wrote:
> > > > > > > "Can we get the iBATIS jars to the maven repository without
> doing
> > a
> > > > > > maven
> > > > > > > build?"
> > > > > > >
> > > > > > > Yes
> > > > > > >
> > > > > > >
> > > > > > > On 2/14/07, Jeff Butler < jeffgbutler@gmail.com > wrote:
> > > > > > > >
> > > > > > > > In my own little perfect world, I'm -1. The iBATIS ant
> build is
> > so
> > > > > > simple
> > > > > > > now - I hate to see it mucked up just to supply the Maven
> meta-bs
> > as
> > > > > > Clinton
> > > > > > > so eloquently put it.
> > > > > > > >
> > > > > > > > However, I would like to see the iBATIS jars in the Maven
> > repository -
> > > > > > if
> > > > > > > for no other reason than to help those who can't figure out
> how to
> > set a
> > > > > > > classpath without a tool. If a maven build makes that
> possible
> > then I
> > > > > > guess
> > > > > > > I'd be +2, but reluctantly.
> > > > > > > >
> > > > > > > > I think that supporting both Ant and Maven is problematical
> -
> > seems
> > > > > > like
> > > > > > > we should just pick one for simplicity going forward.
> > > > > > > >
> > > > > > > > So I guess I can't give a single vote. Can someone
> definitively
> > > > > > answer
> > > > > > > this question: Can we get the iBATIS jars to the maven
> repository
> > > > > > without
> > > > > > > doing a maven build? That's the key point for me.
> > > > > > > >
> > > > > > > > Jeff Butler
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On 2/14/07, Clinton Begin < clinton.begin@gmail.com > wrote:
> > > > > > > >
> > > > > > > > > Hi all,
> > > > > > > > >
> > > > > > > > > It strikes me that there was enough discussion around the
> > Maven
> > > > > > build
> > > > > > > > > to warrant an official vote for Maven support.
> > > > > > > > >
> > > > > > > > > +2 => Replace our Ant build entirely with a Maven build.
> > > > > > > > >
> > > > > > > > > +1 => Support Maven by including a Maven build alongside
> our
> > Ant
> > > > > > build.
> > > > > > > > >
> > > > > > > > > 0 => Don't care or I don't know enough about Maven to
> decide.
> > > > > > > > >
> > > > > > > > > -1 => Do not support maven.
> > > > > > > > >
> > > > > > > > > Cheers,
> > > > > > > > > Clinton
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> >
> >
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Clinton Begin <cl...@gmail.com>.
We don't require a shell script now. The .bat and .sh files are
optional. You're perfectly welcome to install Ant separately (like
you will have to with Maven) and just call ant from within the /build
directory.
Clinton
On 2/14/07, Nathan Maves <na...@gmail.com> wrote:
> +1 and my vote counts!
>
> Speaking from personal experience I have wanted to move to a new build tool
> for a while. While most of you will pay though the nose for the latest M$
> Vista, I run on unix machine. The use of shell scripts for build purposes
> is not a good xplatform solution.
>
> Just from a quick glance Maven seems to make somewhat time consuming tasks
> in Ant easy.
>
> Lets do this.
>
> Nathan
>
>
> On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> > The broader purpose of this is not just to see if we can get jars into
> maven but rather to see if maven can simplify our build/release process. If
> you have a one liner then that is great. I'd love to see it.
> >
> > Brandon
> >
> >
> >
> > On 2/14/07, Slava Imeshev < vimeshev@viewtier.com> wrote:
> > > I seriously doubt that this would require switching to Maven
> > > build.
> > >
> > > I cannot speak for a global catalog, but adding an item built
> > > with Ant to a local Maven repository is a one-liner.
> > >
> > > Regards,
> > >
> > > Slava Imeshev
> > >
> > > ----- Original Message -----
> > > From: "Jeff Butler" <je...@gmail.com>
> > > To: < dev@ibatis.apache.org>; < lmeadors@apache.org>
> > > Sent: Wednesday, February 14, 2007 10:09 AM
> > > Subject: Re: [VOTE] Support for Maven (impacts Java version only)
> > >
> > >
> > > > Yes - I should have asked that question with more subtlety. I guess
> the
> > > > bottom line is that it is *possible* to get the jars to the repository
> > > > without doing a maven build, but doing a maven build makes it much
> easier to
> > > > publish to the repository. And our history shows that we are unlikely
> to
> > > > get the jars to the repository with the build process we are using
> now.
> > > > Right?
> > > >
> > > > Jeff
> > > >
> > > >
> > > >
> > > > On 2/14/07, Larry Meadors < lmeadors@apache.org > wrote:
> > > > >
> > > > > IMO, that is like "Can we clean a toilet with a toothbrush?"
> > > > >
> > > > > Yes, we can, but who wants to offer up their toothbrush? Not me! :-)
> > > > >
> > > > > The question to me is:
> > > > >
> > > > > "Can we get the iBATIS jars to the maven repository without doing a
> > > > > maven build, and is it the right way to do it?"
> > > > >
> > > > > Yes we can, but no it's not.
> > > > >
> > > > > Larry
> > > > >
> > > > >
> > > > > On 2/14/07, Brandon Goodin <brandon.goodin@gmail.com > wrote:
> > > > > > "Can we get the iBATIS jars to the maven repository without doing
> a
> > > > > maven
> > > > > > build?"
> > > > > >
> > > > > > Yes
> > > > > >
> > > > > >
> > > > > > On 2/14/07, Jeff Butler < jeffgbutler@gmail.com > wrote:
> > > > > > >
> > > > > > > In my own little perfect world, I'm -1. The iBATIS ant build is
> so
> > > > > simple
> > > > > > now - I hate to see it mucked up just to supply the Maven meta-bs
> as
> > > > > Clinton
> > > > > > so eloquently put it.
> > > > > > >
> > > > > > > However, I would like to see the iBATIS jars in the Maven
> repository -
> > > > > if
> > > > > > for no other reason than to help those who can't figure out how to
> set a
> > > > > > classpath without a tool. If a maven build makes that possible
> then I
> > > > > guess
> > > > > > I'd be +2, but reluctantly.
> > > > > > >
> > > > > > > I think that supporting both Ant and Maven is problematical -
> seems
> > > > > like
> > > > > > we should just pick one for simplicity going forward.
> > > > > > >
> > > > > > > So I guess I can't give a single vote. Can someone definitively
> > > > > answer
> > > > > > this question: Can we get the iBATIS jars to the maven repository
> > > > > without
> > > > > > doing a maven build? That's the key point for me.
> > > > > > >
> > > > > > > Jeff Butler
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 2/14/07, Clinton Begin < clinton.begin@gmail.com > wrote:
> > > > > > >
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > It strikes me that there was enough discussion around the
> Maven
> > > > > build
> > > > > > > > to warrant an official vote for Maven support.
> > > > > > > >
> > > > > > > > +2 => Replace our Ant build entirely with a Maven build.
> > > > > > > >
> > > > > > > > +1 => Support Maven by including a Maven build alongside our
> Ant
> > > > > build.
> > > > > > > >
> > > > > > > > 0 => Don't care or I don't know enough about Maven to decide.
> > > > > > > >
> > > > > > > > -1 => Do not support maven.
> > > > > > > >
> > > > > > > > Cheers,
> > > > > > > > Clinton
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
>
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Nathan Maves <na...@gmail.com>.
+1 and my vote counts!
Speaking from personal experience I have wanted to move to a new build tool
for a while. While most of you will pay though the nose for the latest M$
Vista, I run on unix machine. The use of shell scripts for build purposes
is not a good xplatform solution.
Just from a quick glance Maven seems to make somewhat time consuming tasks
in Ant easy.
Lets do this.
Nathan
On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
>
> The broader purpose of this is not just to see if we can get jars into
> maven but rather to see if maven can simplify our build/release process. If
> you have a one liner then that is great. I'd love to see it.
>
> Brandon
>
> On 2/14/07, Slava Imeshev <vi...@viewtier.com> wrote:
> >
> > I seriously doubt that this would require switching to Maven
> > build.
> >
> > I cannot speak for a global catalog, but adding an item built
> > with Ant to a local Maven repository is a one-liner.
> >
> > Regards,
> >
> > Slava Imeshev
> >
> > ----- Original Message -----
> > From: "Jeff Butler" <je...@gmail.com>
> > To: <de...@ibatis.apache.org>; < lmeadors@apache.org>
> > Sent: Wednesday, February 14, 2007 10:09 AM
> > Subject: Re: [VOTE] Support for Maven (impacts Java version only)
> >
> >
> > > Yes - I should have asked that question with more subtlety. I guess
> > the
> > > bottom line is that it is *possible* to get the jars to the repository
> > > without doing a maven build, but doing a maven build makes it much
> > easier to
> > > publish to the repository. And our history shows that we are unlikely
> > to
> > > get the jars to the repository with the build process we are using
> > now.
> > > Right?
> > >
> > > Jeff
> > >
> > >
> > >
> > > On 2/14/07, Larry Meadors <lmeadors@apache.org > wrote:
> > > >
> > > > IMO, that is like "Can we clean a toilet with a toothbrush?"
> > > >
> > > > Yes, we can, but who wants to offer up their toothbrush? Not me! :-)
> > > >
> > > > The question to me is:
> > > >
> > > > "Can we get the iBATIS jars to the maven repository without doing a
> > > > maven build, and is it the right way to do it?"
> > > >
> > > > Yes we can, but no it's not.
> > > >
> > > > Larry
> > > >
> > > >
> > > > On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> > > > > "Can we get the iBATIS jars to the maven repository without doing
> > a
> > > > maven
> > > > > build?"
> > > > >
> > > > > Yes
> > > > >
> > > > >
> > > > > On 2/14/07, Jeff Butler < jeffgbutler@gmail.com > wrote:
> > > > > >
> > > > > > In my own little perfect world, I'm -1. The iBATIS ant build is
> > so
> > > > simple
> > > > > now - I hate to see it mucked up just to supply the Maven meta-bs
> > as
> > > > Clinton
> > > > > so eloquently put it.
> > > > > >
> > > > > > However, I would like to see the iBATIS jars in the Maven
> > repository -
> > > > if
> > > > > for no other reason than to help those who can't figure out how to
> > set a
> > > > > classpath without a tool. If a maven build makes that possible
> > then I
> > > > guess
> > > > > I'd be +2, but reluctantly.
> > > > > >
> > > > > > I think that supporting both Ant and Maven is problematical -
> > seems
> > > > like
> > > > > we should just pick one for simplicity going forward.
> > > > > >
> > > > > > So I guess I can't give a single vote. Can someone definitively
> > > > answer
> > > > > this question: Can we get the iBATIS jars to the maven repository
> > > > without
> > > > > doing a maven build? That's the key point for me.
> > > > > >
> > > > > > Jeff Butler
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 2/14/07, Clinton Begin < clinton.begin@gmail.com > wrote:
> > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > It strikes me that there was enough discussion around the
> > Maven
> > > > build
> > > > > > > to warrant an official vote for Maven support.
> > > > > > >
> > > > > > > +2 => Replace our Ant build entirely with a Maven build.
> > > > > > >
> > > > > > > +1 => Support Maven by including a Maven build alongside our
> > Ant
> > > > build.
> > > > > > >
> > > > > > > 0 => Don't care or I don't know enough about Maven to decide.
> > > > > > >
> > > > > > > -1 => Do not support maven.
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Clinton
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Brandon Goodin <br...@gmail.com>.
I think i would echo Jeff's sentiment and hold to one or the other.
As far as integration. Both IDEA and Netbeans have excellent Maven 2
support.
IDEA has the Maven 2 Integration plugin that is installable from their
Plugins setting.
Netbeans has mevenide which allows you to open POMs as a project in the same
manner as it does ant (http://mevenide.codehaus.org/m2-site/index.html).
Altough, I'm not a fan of Netbeans (at all), I have had to use it on a
recent project and have found the Maven 2 integration works great.
Eclipse has support for Maven 2 as well (http://m2eclipse.codehaus.org/)
although i haven't used it.
Brandon
On 2/14/07, Clinton Begin <cl...@gmail.com> wrote:
>
> If that's the case, would it make sense to use Ant for build and Maven
> for deploy?
>
> One thing I'll miss with Maven is the tool integration. I imagine I
> could get a Maven plugin for IDEA and Eclipse, but Ant is ubiquitous
> and works with a lot of other tools.
>
> At least I know Continuum works with Maven! Continuum* rocks.
>
> Clinton
>
> * We're using Parabuild strictly because the company set it up for us
> and is willing to host it for us.
>
> On 2/14/07, Ted Husted <hu...@apache.org> wrote:
> > Maybe a one-liner to deploy the JAR to a local repository, but to
> > ready the JARs for public distribution, we also need to sign them and
> > such. You can do everything that's needed by hand, without Maven, but
> > it can be a lot of work.
> >
> > Even at Struts, we don't have the complete Maven build and deploy down
> > to a one-liner yet. A key bottleneck is that signing the JARs should
> > not be a fully automatic process, since its not a good idea to embed a
> > passphrase in a script. So, it's more like three steps: build, sign,
> > deploy. But, the same should be true of Ant, if we are being careful
> > about signing.
> >
> > -Ted.
> >
> > On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> > > The broader purpose of this is not just to see if we can get jars into
> maven
> > > but rather to see if maven can simplify our build/release process. If
> you
> > > have a one liner then that is great. I'd love to see it.
> > >
> > > Brandon
> > >
> > >
> > > On 2/14/07, Slava Imeshev <vi...@viewtier.com> wrote:
> > > > I seriously doubt that this would require switching to Maven
> > > > build.
> > > >
> > > > I cannot speak for a global catalog, but adding an item built
> > > > with Ant to a local Maven repository is a one-liner.
> > > >
> > > > Regards,
> > > >
> > > > Slava Imeshev
> >
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Slava Imeshev <vi...@viewtier.com>.
FYI, Parabuild allows you manually entering and passing parameters
to a build at build start time. pass phrase seem to be a good candidate.
This way, Maven or not, you can fully control your build from Web UI ...
Regards,
Slava Imeshev
----- Original Message -----
From: "Clinton Begin" <cl...@gmail.com>
To: <de...@ibatis.apache.org>
Sent: Wednesday, February 14, 2007 5:03 PM
Subject: Re: [VOTE] Support for Maven (impacts Java version only)
> If that's the case, would it make sense to use Ant for build and Maven
> for deploy?
>
> One thing I'll miss with Maven is the tool integration. I imagine I
> could get a Maven plugin for IDEA and Eclipse, but Ant is ubiquitous
> and works with a lot of other tools.
>
> At least I know Continuum works with Maven! Continuum* rocks.
>
> Clinton
>
> * We're using Parabuild strictly because the company set it up for us
> and is willing to host it for us.
>
> On 2/14/07, Ted Husted <hu...@apache.org> wrote:
> > Maybe a one-liner to deploy the JAR to a local repository, but to
> > ready the JARs for public distribution, we also need to sign them and
> > such. You can do everything that's needed by hand, without Maven, but
> > it can be a lot of work.
> >
> > Even at Struts, we don't have the complete Maven build and deploy down
> > to a one-liner yet. A key bottleneck is that signing the JARs should
> > not be a fully automatic process, since its not a good idea to embed a
> > passphrase in a script. So, it's more like three steps: build, sign,
> > deploy. But, the same should be true of Ant, if we are being careful
> > about signing.
> >
> > -Ted.
> >
> > On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> > > The broader purpose of this is not just to see if we can get jars into maven
> > > but rather to see if maven can simplify our build/release process. If you
> > > have a one liner then that is great. I'd love to see it.
> > >
> > > Brandon
> > >
> > >
> > > On 2/14/07, Slava Imeshev <vi...@viewtier.com> wrote:
> > > > I seriously doubt that this would require switching to Maven
> > > > build.
> > > >
> > > > I cannot speak for a global catalog, but adding an item built
> > > > with Ant to a local Maven repository is a one-liner.
> > > >
> > > > Regards,
> > > >
> > > > Slava Imeshev
> >
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Clinton Begin <cl...@gmail.com>.
If that's the case, would it make sense to use Ant for build and Maven
for deploy?
One thing I'll miss with Maven is the tool integration. I imagine I
could get a Maven plugin for IDEA and Eclipse, but Ant is ubiquitous
and works with a lot of other tools.
At least I know Continuum works with Maven! Continuum* rocks.
Clinton
* We're using Parabuild strictly because the company set it up for us
and is willing to host it for us.
On 2/14/07, Ted Husted <hu...@apache.org> wrote:
> Maybe a one-liner to deploy the JAR to a local repository, but to
> ready the JARs for public distribution, we also need to sign them and
> such. You can do everything that's needed by hand, without Maven, but
> it can be a lot of work.
>
> Even at Struts, we don't have the complete Maven build and deploy down
> to a one-liner yet. A key bottleneck is that signing the JARs should
> not be a fully automatic process, since its not a good idea to embed a
> passphrase in a script. So, it's more like three steps: build, sign,
> deploy. But, the same should be true of Ant, if we are being careful
> about signing.
>
> -Ted.
>
> On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> > The broader purpose of this is not just to see if we can get jars into maven
> > but rather to see if maven can simplify our build/release process. If you
> > have a one liner then that is great. I'd love to see it.
> >
> > Brandon
> >
> >
> > On 2/14/07, Slava Imeshev <vi...@viewtier.com> wrote:
> > > I seriously doubt that this would require switching to Maven
> > > build.
> > >
> > > I cannot speak for a global catalog, but adding an item built
> > > with Ant to a local Maven repository is a one-liner.
> > >
> > > Regards,
> > >
> > > Slava Imeshev
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Ted Husted <hu...@apache.org>.
Maybe a one-liner to deploy the JAR to a local repository, but to
ready the JARs for public distribution, we also need to sign them and
such. You can do everything that's needed by hand, without Maven, but
it can be a lot of work.
Even at Struts, we don't have the complete Maven build and deploy down
to a one-liner yet. A key bottleneck is that signing the JARs should
not be a fully automatic process, since its not a good idea to embed a
passphrase in a script. So, it's more like three steps: build, sign,
deploy. But, the same should be true of Ant, if we are being careful
about signing.
-Ted.
On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> The broader purpose of this is not just to see if we can get jars into maven
> but rather to see if maven can simplify our build/release process. If you
> have a one liner then that is great. I'd love to see it.
>
> Brandon
>
>
> On 2/14/07, Slava Imeshev <vi...@viewtier.com> wrote:
> > I seriously doubt that this would require switching to Maven
> > build.
> >
> > I cannot speak for a global catalog, but adding an item built
> > with Ant to a local Maven repository is a one-liner.
> >
> > Regards,
> >
> > Slava Imeshev
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Brandon Goodin <br...@gmail.com>.
The broader purpose of this is not just to see if we can get jars into maven
but rather to see if maven can simplify our build/release process. If you
have a one liner then that is great. I'd love to see it.
Brandon
On 2/14/07, Slava Imeshev <vi...@viewtier.com> wrote:
>
> I seriously doubt that this would require switching to Maven
> build.
>
> I cannot speak for a global catalog, but adding an item built
> with Ant to a local Maven repository is a one-liner.
>
> Regards,
>
> Slava Imeshev
>
> ----- Original Message -----
> From: "Jeff Butler" <je...@gmail.com>
> To: <de...@ibatis.apache.org>; <lm...@apache.org>
> Sent: Wednesday, February 14, 2007 10:09 AM
> Subject: Re: [VOTE] Support for Maven (impacts Java version only)
>
>
> > Yes - I should have asked that question with more subtlety. I guess the
> > bottom line is that it is *possible* to get the jars to the repository
> > without doing a maven build, but doing a maven build makes it much
> easier to
> > publish to the repository. And our history shows that we are unlikely
> to
> > get the jars to the repository with the build process we are using now.
> > Right?
> >
> > Jeff
> >
> >
> >
> > On 2/14/07, Larry Meadors <lm...@apache.org> wrote:
> > >
> > > IMO, that is like "Can we clean a toilet with a toothbrush?"
> > >
> > > Yes, we can, but who wants to offer up their toothbrush? Not me! :-)
> > >
> > > The question to me is:
> > >
> > > "Can we get the iBATIS jars to the maven repository without doing a
> > > maven build, and is it the right way to do it?"
> > >
> > > Yes we can, but no it's not.
> > >
> > > Larry
> > >
> > >
> > > On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> > > > "Can we get the iBATIS jars to the maven repository without doing a
> > > maven
> > > > build?"
> > > >
> > > > Yes
> > > >
> > > >
> > > > On 2/14/07, Jeff Butler < jeffgbutler@gmail.com> wrote:
> > > > >
> > > > > In my own little perfect world, I'm -1. The iBATIS ant build is
> so
> > > simple
> > > > now - I hate to see it mucked up just to supply the Maven meta-bs as
> > > Clinton
> > > > so eloquently put it.
> > > > >
> > > > > However, I would like to see the iBATIS jars in the Maven
> repository -
> > > if
> > > > for no other reason than to help those who can't figure out how to
> set a
> > > > classpath without a tool. If a maven build makes that possible then
> I
> > > guess
> > > > I'd be +2, but reluctantly.
> > > > >
> > > > > I think that supporting both Ant and Maven is problematical -
> seems
> > > like
> > > > we should just pick one for simplicity going forward.
> > > > >
> > > > > So I guess I can't give a single vote. Can someone definitively
> > > answer
> > > > this question: Can we get the iBATIS jars to the maven repository
> > > without
> > > > doing a maven build? That's the key point for me.
> > > > >
> > > > > Jeff Butler
> > > > >
> > > > >
> > > > >
> > > > > On 2/14/07, Clinton Begin < clinton.begin@gmail.com > wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > It strikes me that there was enough discussion around the Maven
> > > build
> > > > > > to warrant an official vote for Maven support.
> > > > > >
> > > > > > +2 => Replace our Ant build entirely with a Maven build.
> > > > > >
> > > > > > +1 => Support Maven by including a Maven build alongside our
> Ant
> > > build.
> > > > > >
> > > > > > 0 => Don't care or I don't know enough about Maven to decide.
> > > > > >
> > > > > > -1 => Do not support maven.
> > > > > >
> > > > > > Cheers,
> > > > > > Clinton
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> >
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Slava Imeshev <vi...@viewtier.com>.
I seriously doubt that this would require switching to Maven
build.
I cannot speak for a global catalog, but adding an item built
with Ant to a local Maven repository is a one-liner.
Regards,
Slava Imeshev
----- Original Message -----
From: "Jeff Butler" <je...@gmail.com>
To: <de...@ibatis.apache.org>; <lm...@apache.org>
Sent: Wednesday, February 14, 2007 10:09 AM
Subject: Re: [VOTE] Support for Maven (impacts Java version only)
> Yes - I should have asked that question with more subtlety. I guess the
> bottom line is that it is *possible* to get the jars to the repository
> without doing a maven build, but doing a maven build makes it much easier to
> publish to the repository. And our history shows that we are unlikely to
> get the jars to the repository with the build process we are using now.
> Right?
>
> Jeff
>
>
>
> On 2/14/07, Larry Meadors <lm...@apache.org> wrote:
> >
> > IMO, that is like "Can we clean a toilet with a toothbrush?"
> >
> > Yes, we can, but who wants to offer up their toothbrush? Not me! :-)
> >
> > The question to me is:
> >
> > "Can we get the iBATIS jars to the maven repository without doing a
> > maven build, and is it the right way to do it?"
> >
> > Yes we can, but no it's not.
> >
> > Larry
> >
> >
> > On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> > > "Can we get the iBATIS jars to the maven repository without doing a
> > maven
> > > build?"
> > >
> > > Yes
> > >
> > >
> > > On 2/14/07, Jeff Butler < jeffgbutler@gmail.com> wrote:
> > > >
> > > > In my own little perfect world, I'm -1. The iBATIS ant build is so
> > simple
> > > now - I hate to see it mucked up just to supply the Maven meta-bs as
> > Clinton
> > > so eloquently put it.
> > > >
> > > > However, I would like to see the iBATIS jars in the Maven repository -
> > if
> > > for no other reason than to help those who can't figure out how to set a
> > > classpath without a tool. If a maven build makes that possible then I
> > guess
> > > I'd be +2, but reluctantly.
> > > >
> > > > I think that supporting both Ant and Maven is problematical - seems
> > like
> > > we should just pick one for simplicity going forward.
> > > >
> > > > So I guess I can't give a single vote. Can someone definitively
> > answer
> > > this question: Can we get the iBATIS jars to the maven repository
> > without
> > > doing a maven build? That's the key point for me.
> > > >
> > > > Jeff Butler
> > > >
> > > >
> > > >
> > > > On 2/14/07, Clinton Begin < clinton.begin@gmail.com > wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > It strikes me that there was enough discussion around the Maven
> > build
> > > > > to warrant an official vote for Maven support.
> > > > >
> > > > > +2 => Replace our Ant build entirely with a Maven build.
> > > > >
> > > > > +1 => Support Maven by including a Maven build alongside our Ant
> > build.
> > > > >
> > > > > 0 => Don't care or I don't know enough about Maven to decide.
> > > > >
> > > > > -1 => Do not support maven.
> > > > >
> > > > > Cheers,
> > > > > Clinton
> > > > >
> > > >
> > > >
> > >
> > >
> >
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Jeff Butler <je...@gmail.com>.
Yes - I should have asked that question with more subtlety. I guess the
bottom line is that it is *possible* to get the jars to the repository
without doing a maven build, but doing a maven build makes it much easier to
publish to the repository. And our history shows that we are unlikely to
get the jars to the repository with the build process we are using now.
Right?
Jeff
On 2/14/07, Larry Meadors <lm...@apache.org> wrote:
>
> IMO, that is like "Can we clean a toilet with a toothbrush?"
>
> Yes, we can, but who wants to offer up their toothbrush? Not me! :-)
>
> The question to me is:
>
> "Can we get the iBATIS jars to the maven repository without doing a
> maven build, and is it the right way to do it?"
>
> Yes we can, but no it's not.
>
> Larry
>
>
> On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> > "Can we get the iBATIS jars to the maven repository without doing a
> maven
> > build?"
> >
> > Yes
> >
> >
> > On 2/14/07, Jeff Butler < jeffgbutler@gmail.com> wrote:
> > >
> > > In my own little perfect world, I'm -1. The iBATIS ant build is so
> simple
> > now - I hate to see it mucked up just to supply the Maven meta-bs as
> Clinton
> > so eloquently put it.
> > >
> > > However, I would like to see the iBATIS jars in the Maven repository -
> if
> > for no other reason than to help those who can't figure out how to set a
> > classpath without a tool. If a maven build makes that possible then I
> guess
> > I'd be +2, but reluctantly.
> > >
> > > I think that supporting both Ant and Maven is problematical - seems
> like
> > we should just pick one for simplicity going forward.
> > >
> > > So I guess I can't give a single vote. Can someone definitively
> answer
> > this question: Can we get the iBATIS jars to the maven repository
> without
> > doing a maven build? That's the key point for me.
> > >
> > > Jeff Butler
> > >
> > >
> > >
> > > On 2/14/07, Clinton Begin < clinton.begin@gmail.com > wrote:
> > >
> > > > Hi all,
> > > >
> > > > It strikes me that there was enough discussion around the Maven
> build
> > > > to warrant an official vote for Maven support.
> > > >
> > > > +2 => Replace our Ant build entirely with a Maven build.
> > > >
> > > > +1 => Support Maven by including a Maven build alongside our Ant
> build.
> > > >
> > > > 0 => Don't care or I don't know enough about Maven to decide.
> > > >
> > > > -1 => Do not support maven.
> > > >
> > > > Cheers,
> > > > Clinton
> > > >
> > >
> > >
> >
> >
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Larry Meadors <lm...@apache.org>.
IMO, that is like "Can we clean a toilet with a toothbrush?"
Yes, we can, but who wants to offer up their toothbrush? Not me! :-)
The question to me is:
"Can we get the iBATIS jars to the maven repository without doing a
maven build, and is it the right way to do it?"
Yes we can, but no it's not.
Larry
On 2/14/07, Brandon Goodin <br...@gmail.com> wrote:
> "Can we get the iBATIS jars to the maven repository without doing a maven
> build?"
>
> Yes
>
>
> On 2/14/07, Jeff Butler < jeffgbutler@gmail.com> wrote:
> >
> > In my own little perfect world, I'm -1. The iBATIS ant build is so simple
> now - I hate to see it mucked up just to supply the Maven meta-bs as Clinton
> so eloquently put it.
> >
> > However, I would like to see the iBATIS jars in the Maven repository - if
> for no other reason than to help those who can't figure out how to set a
> classpath without a tool. If a maven build makes that possible then I guess
> I'd be +2, but reluctantly.
> >
> > I think that supporting both Ant and Maven is problematical - seems like
> we should just pick one for simplicity going forward.
> >
> > So I guess I can't give a single vote. Can someone definitively answer
> this question: Can we get the iBATIS jars to the maven repository without
> doing a maven build? That's the key point for me.
> >
> > Jeff Butler
> >
> >
> >
> > On 2/14/07, Clinton Begin < clinton.begin@gmail.com > wrote:
> >
> > > Hi all,
> > >
> > > It strikes me that there was enough discussion around the Maven build
> > > to warrant an official vote for Maven support.
> > >
> > > +2 => Replace our Ant build entirely with a Maven build.
> > >
> > > +1 => Support Maven by including a Maven build alongside our Ant build.
> > >
> > > 0 => Don't care or I don't know enough about Maven to decide.
> > >
> > > -1 => Do not support maven.
> > >
> > > Cheers,
> > > Clinton
> > >
> >
> >
>
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Brandon Goodin <br...@gmail.com>.
"Can we get the iBATIS jars to the maven repository without doing a maven
build?"
Yes
On 2/14/07, Jeff Butler <je...@gmail.com> wrote:
>
> In my own little perfect world, I'm -1. The iBATIS ant build is so
> simple now - I hate to see it mucked up just to supply the Maven meta-bs as
> Clinton so eloquently put it.
>
> However, I would like to see the iBATIS jars in the Maven repository - if
> for no other reason than to help those who can't figure out how to set a
> classpath without a tool. If a maven build makes that possible then I guess
> I'd be +2, but reluctantly.
>
> I think that supporting both Ant and Maven is problematical - seems like
> we should just pick one for simplicity going forward.
>
> So I guess I can't give a single vote. Can someone definitively answer
> this question: Can we get the iBATIS jars to the maven repository without
> doing a maven build? That's the key point for me.
>
> Jeff Butler
>
>
>
> On 2/14/07, Clinton Begin <clinton.begin@gmail.com > wrote:
> >
> > Hi all,
> >
> > It strikes me that there was enough discussion around the Maven build
> > to warrant an official vote for Maven support.
> >
> > +2 => Replace our Ant build entirely with a Maven build.
> >
> > +1 => Support Maven by including a Maven build alongside our Ant build.
> >
> > 0 => Don't care or I don't know enough about Maven to decide.
> >
> > -1 => Do not support maven.
> >
> > Cheers,
> > Clinton
> >
>
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Jeff Butler <je...@gmail.com>.
In my own little perfect world, I'm -1. The iBATIS ant build is so
simple now - I hate to see it mucked up just to supply the Maven meta-bs as
Clinton so eloquently put it.
However, I would like to see the iBATIS jars in the Maven repository - if
for no other reason than to help those who can't figure out how to set a
classpath without a tool. If a maven build makes that possible then I guess
I'd be +2, but reluctantly.
I think that supporting both Ant and Maven is problematical - seems like we
should just pick one for simplicity going forward.
So I guess I can't give a single vote. Can someone definitively answer this
question: Can we get the iBATIS jars to the maven repository without doing
a maven build? That's the key point for me.
Jeff Butler
On 2/14/07, Clinton Begin <clinton.begin@gmail.com > wrote:
>
> Hi all,
>
> It strikes me that there was enough discussion around the Maven build
> to warrant an official vote for Maven support.
>
> +2 => Replace our Ant build entirely with a Maven build.
>
> +1 => Support Maven by including a Maven build alongside our Ant build.
>
> 0 => Don't care or I don't know enough about Maven to decide.
>
> -1 => Do not support maven.
>
> Cheers,
> Clinton
>
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by "Bruno Silva (Cool Advance)" <br...@cooladvance.com>.
If you want to know my opinion, +1. I guess Ant is everywhere in the
Java world while Maven is not (I personally prefer Ivy for dependency
management).
Regards,
Bruno Silva
Clinton Begin wrote:
> Hi all,
>
> It strikes me that there was enough discussion around the Maven build
> to warrant an official vote for Maven support.
>
> +2 => Replace our Ant build entirely with a Maven build.
>
> +1 => Support Maven by including a Maven build alongside our Ant build.
>
> 0 => Don't care or I don't know enough about Maven to decide.
>
> -1 => Do not support maven.
>
> Cheers,
> Clinton
Re: [VOTE] Support for Maven (impacts Java version only)
Posted by Larry Meadors <lm...@apache.org>.
+2
On 2/14/07, Clinton Begin <cl...@gmail.com> wrote:
> Hi all,
>
> It strikes me that there was enough discussion around the Maven build
> to warrant an official vote for Maven support.
>
> +2 => Replace our Ant build entirely with a Maven build.
>
> +1 => Support Maven by including a Maven build alongside our Ant build.
>
> 0 => Don't care or I don't know enough about Maven to decide.
>
> -1 => Do not support maven.
>
> Cheers,
> Clinton
>