dev@javaserverfaces.java.net

Re: Proposed build change

From: Ryan Lubke <Ryan.Lubke_at_Sun.COM>
Date: Mon, 28 Jan 2008 15:16:22 -0800

Jason Lee wrote:
> I'd like to run an idea by the Mojarra devs. First, let me point to
> this entry on my blog:
>
> http://blogs.steeplesoft.com/2008/01/17/dependency-management-with-ant-and-ivy/
> <http://blogs.steeplesoft.com/2008/01/17/dependency-management-with-ant-and-ivy/>
>
> In a nut shell, I'm using ivy to manage the dependencies for Scales,
> and have been pondering making a similar change to Mojarra itself.
> I've talk to Ryan about this some, and he suggested getting some
> feedback from the developers as a whole. As we see it, our options
> are to adopt the approach detailed above, finally bite the bullet and
> migrate the build to maven 2, or do nothing.
>
> I know that people can be quite...zealous about build systems, so I
> apologize if I'm kicking a hornet's nest, but... What does everyone
> think? Is the ROI, so to speak, worth it? If we're going to change
> things, should we go ahead and move to maven, or do we not want to
> monkey with something like the build system while an EG is at work?
>
> I'm open to (and ultimately subject to) suggestions... :)
I'd say move to ivy for now. It has to be more robust than the solution
we're currently using.
We can move to maven later if need be.

>
> --
> Jason Lee, SCJP
> Software Architect -- Objectstream, Inc.
> Mojarra and Mojarra Scales Dev Team
> https://mojarra.dev.java.net
> https://scales.dev.java.net
> http://blogs.steeplesoft.com