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 i
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 node.
Alternatively, you can try
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
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
chan
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, packa
