> -Original Message-
> From: jk jk [mailto:[EMAIL PROTECTED]
> WTP does sound pretty good and I might try it out down
> the road. When you were using MyEclipse or maybe this
> actually applies to just eclipse, do you need to
> execute, maven eclipse goal to generate the MAVEN_REPO
> vari
Hi,
I don't know if it's of any interest to you, but I managed to use the
newly released WTP (http://www.eclipse.org/webtools/ )to do just that.
I like WTP a lot as with my setup it seems much faster/stable than myEclipse
for jsp editing.
Moreover the deployement is much closer to a real one bec
run the maven.bat command from the command line
then you'll be able to see the message.
to achieve that follow the instructions:
click on the start menu then choose "Run..."
enter "cmd" and click OK
The black box is called "The Command Line"
drag an drop from Explorer to "The Command Line" the ma
> Right, part of my problem is that I don't understand exactly how the
> SNAPSHOT stuff works. Perhaps SNAPSHOTs don't make as much sense in a
> "multiproject" context at least as far the modules are concerned. I
> replaced SNAPSHOT with an actual version number within the different
> modules' pr
> Thanks for the answer. It is indeed a good solution.
>
> Just one think : in your goal above, you don't call the
> goal, so I don't see how your dependent
> projects can refer to the last good versions of each other ?
you are right, the line was a strip-down version of my goal
which use a
Hi,
> -Original Message-
> From: Laurent PETIT [mailto:[EMAIL PROTECTED]
> I have multiple subprojects which are continuously integrated with
> CruiseControl.
> I generate for each subproject the artifact, and install it.
>
> I also use CruiseControl to generate the whole site, with
> m
Hi,
> It's always hard to tell what settings log4j is actually using
yes that's why there is the log4j.debug switch.
it forces log4j to spit out which configuration file it is using
it you are not forking your test, you have to define the MAVEN_OPTS env variable
unix:
MAVEN_OPTS=-Dlog4j.debug
