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
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
"Can we get the iBATIS jars to the maven repository without doing a maven
build?"
Yes
On 2/14/07, Jeff Butler <[EMAIL PROTECTED]> 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 el
+2
On 2/14/07, Clinton Begin <[EMAIL PROTECTED]> 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 alongsi
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 <[EMAIL PROTECTED]> wrote:
Hi all,
It strikes me that there was enough discussion around the Maven build
to warrant an of
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 offic
Votes never close and can be changed, so don't worry about the timing.
Clinton
On 2/14/07, Brandon Goodin <[EMAIL PROTECTED]> 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, Cl
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 n
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
If past history is any indication of the future, that is correct.
:)
Larry
On 2/14/07, Jeff Butler <[EMAIL PROTECTED]> 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 b
t;
To: ; <[EMAIL PROTECTED]>
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
&
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
IL PROTECTED]>
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 do
uilt
> with Ant to a local Maven repository is a one-liner.
>
> Regards,
>
> Slava Imeshev
>
> - Original Message -
> From: "Jeff Butler" <[EMAIL PROTECTED]>
> To: ; < [EMAIL PROTECTED]>
> Sent: Wednesday, February 14, 2007 10:09 AM
> Subjec
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
k 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" <[EMAIL PROTECTED]>
> > To: &l
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 M
Begin" <[EMAIL PROTECTED]>
To:
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
lt
> > > with Ant to a local Maven repository is a one-liner.
> > >
> > > Regards,
> > >
> > > Slava Imeshev
> > >
> > > - Original Message -
> > > From: "Jeff Butler" <[EMAIL PROTECTED]>
> > > To: <
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 proje
em built
> > > > with Ant to a local Maven repository is a one-liner.
> > > >
> > > > Regards,
> > > >
> > > > Slava Imeshev
> > > >
> > > > - Original Message -
> > > > From: "Jeff Butler&quo
; [EMAIL PROTECTED]> 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 An
22 matches
Mail list logo
