Hi Darryl, Looks like you night have missed the mail thread I started yesterday about stopping versioning dependency artifacts.We should be doing somthing almost immediately (i.e next week, I have already put together part of it) on that point.
On using Maven, that would be a larger discussion and work effort to move us over. I admit I would use Maven if we were starting from scratch, there is little doubt it offers benefits, but it would be a fair amount of effort to swap over that is hard to justify in some ways and there is an unfortunate history with its prior usage in the project that I think puts many off. I also wouldnt want to end up with 2 build systems running side by side before anyone suggests it, thats been done already :) Robbie On 4 May 2012 17:17, Darryl L. Pierce <[email protected]> wrote: > On Fri, May 04, 2012 at 10:41:55AM -0400, Weston M. Price wrote: >> In the JCA example code, we have a dependency on the Servlet API. Currently >> we include a few JEE jars from Geronimo (ejb, jca etc). I would like the >> include the geronimo-servlet-spec jar as well. Is it as simple as taking a >> copy of the jar and putting it in the java/lib directory or is there >> something more to it? > > Side question: > > Are there any plans to, in future, go with a Maven development > environment for the Java code? That way we can avoid versioning > artifacts. > > -- > Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. > Delivering value year after year. > Red Hat ranks #1 in value among software vendors. > http://www.redhat.com/promo/vendor/ > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
