river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wade Chandler <hwadechandler-apa...@yahoo.com>
Subject Re: Deciding the Future
Date Mon, 08 Dec 2008 14:40:48 GMT
----- Original Message ----

> From: Sean Landis <sean.landis@gmail.com>
> To: river-dev@incubator.apache.org
> Sent: Monday, December 8, 2008 9:09:09 AM
> Subject: Re: Deciding the Future
> I would be in favor of moving to Maven. This year we moved about 30
> projects from Ant to Maven. There are some gotchas though (disclaimer
> - I'm not the expert). One that I am aware of is the artifact per
> project preference of Maven that, as others pointed out, would pose a
> challenge for the Jini jar service pairs. Another side-effect of this
> constraint is how it interacts with Eclipse which does not support
> subprojects well. We have found that some thought is required to use
> Maven seamlessly within Eclipse. It's doable, but if you just do the
> obvious thing you might have a lot of problems.
> All that said, we have great benefits from Maven.

Hmm. Your points make me favor Ant. Essentially it seems with Ant we have more flexibility
out of the box. There may be a little more work to get what we want, but we can get what we
want with Ant, and we don't have any real lock in to a necessary structure; we can define
our own and output artifacts as needed. We can write extension tasks in Java to do anything
we need, and if needed we can also standardize on some language for build script extensions
such as Groovy or Jython or something and use the <script> tag for a lot. The script
tag has proven very useful to me different times using BeanShell. Is there any truth to what
I'm infering from your points or am I off base?



Wade Chandler, CCE
Software Engineer and Developer, Certified Forensic Computer Examiner, NetBeans Dream Team
Member, and NetBeans Board Member

View raw message