My Fellow Code Monkeys, You may have noticed I recommended for a push to change the build to a Maven 2 structure. Before starting a Mavenization discussion thread, I wanted to investigate the entire build process. My first day here, I noticed that we are downloading DBCP source files and compiling them with the Tomcat build. In my humble opinion, I think it would be nice to just include a reference to a working version of the DBCP as a Maven dependency. As I am still getting acquainted here, I have tried to refrain from rocking the boat, but, why do we tie ourselves to a build process of another completely separate and JDK-dependent project? Tomcat and DBCP should be built separately, and Tomcat should probably use the pre-built, fully-tested DBCP jar file. If I am missing something, please forgive and educate this poor Tomcat Newbie.
I hereby re-announce my willingness to volunteer efforts towards the the true Mavenization of the Tomcat build. Should we take a vote on this? As a proof-of-concept, may I start a Maven2-managed SVN branch somehow? Sincerely, Paul Shemansky Maven 2 Evangelist On 10/17/07, Rémy Maucherat <[EMAIL PROTECTED]> wrote: > > On Wed, 2007-10-17 at 08:41 -0400, Yoav Shapira wrote: > > Hi DI, > > > > On 10/17/07, DI Roman Fiedler <[EMAIL PROTECTED]> wrote: > > > If misunderstood: Change line to > > > Download a Java Development Kit (JDK) release (version 1.5.x) from: > > > > > > If error: > > > search for it? > > > > It's an error: the build is intended to work with Java 1.5 and later, > > including Java 1.6, but it doesn't right now. It's our fault and > > we're working on fixing it. Sorry about that ;) > > It's impossible to predict if it will work with newer versions. It's > supposed to, but Sun likes to break the JDBC interfaces on each major > upgrade :( > > Rémy > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
