You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Jean-Baptiste Quenot <jb...@apache.org> on 2006/11/20 09:28:11 UTC
Ant + Ivy
Hi,
I notice that you're using Ant to distribute the releases, right?
Then I have a simple question, are you interested in adding an
Ant-based dependency resolution tool named Ivy?
I generally prefer this tool rather than using the cryptic and
buggy Maven 2.
BTW I wrote a presentation about integrating Ivy in Cocoon:
http://www.mail-archive.com/dev@cocoon.apache.org/msg46985.html
WDYT?
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
Re: Ant + Ivy
Posted by Jean-Baptiste Quenot <jb...@apache.org>.
* Eelco Hillenius:
> Not that we don't like Ant/ Ivy, just that maven works good
> enough.
I understand that Maven works good enough with Wicket, as it is a
project with very few dependencies. Maven shows its limit when
the complexity of the project increases though.
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
Re: Ant + Ivy
Posted by Eelco Hillenius <ee...@gmail.com>.
FYI I have used Ivy/ Ant on a project a bit over a year ago. It worked
nicely alright. But the main reason to use it was because we couldn't
use maven. As with Wicket we standardized on maven from the start, and
maven suited our purposes well, I don't see any compelling reason to
replace it. Not that we don't like Ant/ Ivy, just that maven works
good enough.
Eelco
On 11/20/06, Martijn Dashorst <ma...@gmail.com> wrote:
> On 11/20/06, Jean-Baptiste Quenot <jb...@apache.org> wrote:
> > I notice that you're using Ant to distribute the releases, right?
>
> No. We supply the ant build file only for those that don't want to
> work with maven. Maven is our distribution and release platform.
>
> > Then I have a simple question, are you interested in adding an
> > Ant-based dependency resolution tool named Ivy?
>
> Nope. I'm not interested in moving to ant/ivy.
>
> > I generally prefer this tool rather than using the cryptic and
> > buggy Maven 2.
>
> Opinions opinions. Yes maven has its quirks, but sofar it has suited
> us very well. They are working very hard to resolve bugs in their
> current release.
>
> Now on the ivy/ant integration part. I'm happy to apply any patch to
> the build.xml files found in src/assembly/build.xml in our repository.
> But afaic we're not moving away from maven as our build/release
> system.
>
> Martijn
>
> --
> <a href="http://www.thebeststuffintheworld.com/vote_for/wicket">Vote</a>
> for <a href="http://www.thebeststuffintheworld.com/stuff/wicket">Wicket</a>
> at the <a href="http://www.thebeststuffintheworld.com/">Best Stuff in
> the World!</a>
>
Re: Ant + Ivy
Posted by Martijn Dashorst <ma...@gmail.com>.
On 11/20/06, Jean-Baptiste Quenot <jb...@apache.org> wrote:
> I notice that you're using Ant to distribute the releases, right?
No. We supply the ant build file only for those that don't want to
work with maven. Maven is our distribution and release platform.
> Then I have a simple question, are you interested in adding an
> Ant-based dependency resolution tool named Ivy?
Nope. I'm not interested in moving to ant/ivy.
> I generally prefer this tool rather than using the cryptic and
> buggy Maven 2.
Opinions opinions. Yes maven has its quirks, but sofar it has suited
us very well. They are working very hard to resolve bugs in their
current release.
Now on the ivy/ant integration part. I'm happy to apply any patch to
the build.xml files found in src/assembly/build.xml in our repository.
But afaic we're not moving away from maven as our build/release
system.
Martijn
--
<a href="http://www.thebeststuffintheworld.com/vote_for/wicket">Vote</a>
for <a href="http://www.thebeststuffintheworld.com/stuff/wicket">Wicket</a>
at the <a href="http://www.thebeststuffintheworld.com/">Best Stuff in
the World!</a>
Re: Ant + Ivy
Posted by Ross Gardler <rg...@apache.org>.
Jean-Baptiste Quenot wrote:
> I notice that you're using Ant to distribute the releases, right?
> Then I have a simple question, are you interested in adding an
> Ant-based dependency resolution tool named Ivy?
As a new Wicket (and Ivy) user, gradually getting into the code of
Wicket 2.0 I would love to see a move to Ivy. I'd be more than happy to
help maintain configs for this.
Ross
Re: Ant + Ivy
Posted by Ross Gardler <rg...@apache.org>.
Filippo Diotalevi wrote:
> On 11/20/06, Jean-Baptiste Quenot <jb...@apache.org> wrote:
>> Hi,
>> I notice that you're using Ant to distribute the releases, right?
>> Then I have a simple question, are you interested in adding an
>> Ant-based dependency resolution tool named Ivy?
>
> Hi, how does Ivy compare to Ant or Maven? Looking at the website, it
> seems to me a tool to manage dependencies, so it can be used to manage
> builds and packagings, not only distributing.. am I wrong?
Ivy integrates with ANT it is not to be compared to ANT. Ant does the
build management, Ivy does the dependency management. They make a
fantastic team.
As for Maven, I have very little personal experience of it, so I'll
avoid making ill-informed comparisons. All I will say is that I
originally went with Ivy because my desk research indicated that for
dependency management Ivy worked and Maven sometimes struggled in larger
projects. For an "at home" experience take a look at the Cocoon archives.
Having gone with Ivy I am very happy with it (even more so now that it
is in the Apache Incubator).
Ross
Re: Ant + Ivy
Posted by Jean-Baptiste Quenot <jb...@apache.org>.
* Filippo Diotalevi:
> Looking at the website, it seems to me a tool to manage
> dependencies, so it can be used to manage builds and packagings,
> not only distributing.. am I wrong?
Yes basically I'm proposing to use Ivy for resolving dependencies,
which occurs at build time for computing a compiling classpath,
and also upon packaging to include all needed libraries in the
release.
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
Re: Ant + Ivy
Posted by Filippo Diotalevi <fi...@gmail.com>.
On 11/20/06, Jean-Baptiste Quenot <jb...@apache.org> wrote:
> Hi,
> I notice that you're using Ant to distribute the releases, right?
> Then I have a simple question, are you interested in adding an
> Ant-based dependency resolution tool named Ivy?
Hi, how does Ivy compare to Ant or Maven? Looking at the website, it
seems to me a tool to manage dependencies, so it can be used to manage
builds and packagings, not only distributing.. am I wrong?
> I generally prefer this tool rather than using the cryptic and
> buggy Maven 2.
>From what I see, Wicket is using Maven 2 for it's build and release
process, and I'm not a great fan of it, to say the least. Right now
I'm struggling with mvn to try to automatically build an ear using
Java EE 5 formats...
--
Filippo Diotalevi
filippo.diotalevi@gmail.com
http://www.diotalevi.com/weblog
http://www.jugmilano.it