Hi Kenney, > -----Original Message----- > From: Kenney Westerhof [mailto:[EMAIL PROTECTED] > Sent: jeudi 25 août 2005 12:24 > To: cactus-dev@jakarta.apache.org > Subject: Converting to maven2 > > > Hi,
Hey, welcome aboard! > > I've been looking at the current build system used, and OMG, OMG? > it's > ant-hell! :) Come on! It's not that bad :-) > I could leave the current directory structure intact, but then I'd have to > use custom maven2 plugins and embedded ant scripts all the way to support > that since this structure is not according to the maven philosphy > (the main problem being you can only specify 1 source folder, just as in > maven1, but it can't be easily circumvented using a maven.xml script like > Vincent has done.) Yep, I agree about doing it right, i.e. moving files around. > To the point: I'd like to move some directories around. Is it ok > if I create a branch containing the new directory structure + pom.xml > files, possibly using symlinks (yes you can version those > too nowadays, I believe) to point to the real source directories? Here's the issue I see with this approach: Cactus developers and users are not going to use the Maven2 build system before it is fully functional and before it allows to fully build Cactus. This won't happen overnight either... :-) So I think working on branch till the full m2 build is usable is going to be hard and I would be more comfortable if we were doing it step by step. For example: Step 1: ------- * Refactor the framework/ project into 5 modules (share-12-13-14, share-13-14, j2ee-12, j2ee-13 and j2ee-14). BTW if you have a better idea for naming and organization I'm all ears! * Modify the Ant build so that it can build those 5 new projects * Check in the Maven2 build for those 5 modules * Note: We do not want to release those module jars separately. I guess we'll need to use the assembly plugin to aggregate them. Step 2: ------- Tackle the integration/ant subproject and do the same. Step 3: ------- Etc. Step N: ------- Handle the documentation/ subproject by breaking it into the different existing modules (framework doc, integration/ant doc, etc). Top level documentation would stay in the top level directory. WDYT? It's a bit more work provided that we want to drop support for Ant but I think it's going to be too hard to merge a long-running branch. You'd need to merge all the changes done on the main trunk. > That way everybody can keep working. The other solution, building custom > plugins to facilitate keeping the current directory structure, will take > a lot more time and is more error prone, but you should decide. Nah... I agree that's a bad idea. > Btw, if a new directory structure is made, the ant build system will > need modification ofcourse, if we want to support the two side by side > (but only after the branch with the new system has made it into trunk!) I think we have a slightly different POV but I'm all ears... Let me know what you prefer. What do others think? Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
