Hi Wayne, Thanks again for the feedback.
I've looked through the poms and don't see any suspicious 'module' entries. I am using Hudson to run the Maven build. Do you know if this might cause the problem? Wessie! Wayne Fay wrote: > > There is no particular reason why these files should land in this > directory using standard Maven configuration, so you must have > something custom in your build that is causing it to occur. > > Try scanning the pom.xml files for "modules". Obviously you can ignore > the <project><modules> node. > > Alternatively, you can try examining the build output which may > provide some clues: > mvn clean package | grep modules > > Wayne > > On 8/21/08, wessie <[EMAIL PROTECTED]> wrote: >> >> Hi Alex-450, >> >> Thanks for the quick response! >> >> I've tried changing the maven goals to "clean package". The problem is >> that >> after each build it still archives the built ear and war files into the >> 'PROJECTX'/modules/ directory every single time the project is built. >> >> Is it possible to get around this archiving? >> >> Thanks again >> Wessie! >> >> >> Alex-450 wrote: >> > >> > Hi Wessie, >> > >> > why not simply upload the ear file to a location outside the cvs which >> > is accessible via web (or via scp)? By the way, I was glad when we >> > switched from CVS to SVN. I'm not an expert, but I have the impression >> > that SVN is much more stable. Nevertheless I wouldn't put constantly >> > changing binary files under a version control system. >> > >> > Cheers >> > >> > Alex >> > >> > wessie wrote: >> >> Hi all, >> >> >> >> I've been given the task of maintaining an exisiting Hudson/Maven >> setup. >> >> I >> >> think i've got an 'ok' understanding of whats going on but i'm still >> >> learning daily. >> >> >> >> The problem I have is this. I have a multi-module build that checksout >> a >> >> project from a cvs repository, builds the source, packages it into an >> ear >> >> file and then checks the ear back into the same cvs repository (just a >> >> slightly different location). The project is run with "clean install" >> >> goals. >> >> >> >> All of the above works fine BUT the ear file (and it's inner war file) >> >> gets >> >> copied into the 'PROJECTX'/modules/ directory every single time the >> >> project >> >> is built. The result is frequent calls from maintenance teams at >> really >> >> crappy hours. >> >> >> >> Writing a script the /modules/ directory periodically is a solution >> but >> >> i'd >> >> prefer to fix the problem and not one of its symptoms. >> >> >> >> I'd be happy to provide any poms if anyone is willing to help. >> >> >> >> Wessie! >> > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/newby%3A-disk-space-consumption-tp19086120p19102282.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/newby%3A-disk-space-consumption-tp19086120p19138912.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
