Thanks for your answers,
That's certainly what's wrong. We don't have any $USER_HOME/.m2/settings.xml
file. Only in $M2_HOME/conf.
In fact, the maven version and binaries we're using is distributed to our
developers with the right settings.xml file in $M2_HOME/conf directory.
How come maven,
It's a planned feature. I can't say for the moment when it will be
available.
Emmanuel
On Tue, Mar 4, 2008 at 2:23 AM, deckrider [EMAIL PROTECTED] wrote:
Hi,
We have a 4-cpu machine on which we run continuum 1.1. Unfortunately,
it only runs one build at a time. How can we run up to 4
On Tue, Mar 4, 2008 at 11:45 AM, Jonathan Share [EMAIL PROTECTED] wrote:
Hi,
I'm currently trying to get Continuum working standalone on a Debian
system and it seems that the documented instructions[1] are severely
flawed.
If you follow the instructions directly
ln -s
Hi,
Anybody there are solution to this problem.
I´ve never saw this.
Provider message: The svn command failed.
Command output:
---
svn: Your .svn/tmp directory may be missing or corrupt; run 'svn cleanup' and
try
Do you have a plugin or a test that modify/create a file or a directory in
the local copy?
Emmanuel
On Tue, Mar 4, 2008 at 2:03 PM, John Coleman
[EMAIL PROTECTED] wrote:
Hi,
I have had problems committing a source fiel recently and somehow this
has messed up out continuum build.
Emmanuel Venisse wrote:
Do you have a plugin or a test that modify/create a file or a directory in
the local copy?
Emmanuel
On Tue, Mar 4, 2008 at 2:03 PM, John Coleman
[EMAIL PROTECTED] wrote:
Hi,
I have had problems committing a source fiel recently and somehow this
has messed up out
You need file access to your continuum application. (Through ssh or on the
machine itself for example) Continuum uses a work directory where the checkouts
are made. Here lies the problem. (For every build the working copy is updated,
not recreated.)
As a side note for the dev'ers. Would it be
