I'm running continuum 1.0.3 on a large multimodule project. On one of my maven2
projects inside continuum, I have a 'clean deploy' build definition recursively
building a large chunk of code, which seems to keep hanging during the deploy
phase. I have to keep restarting continuum so that it can
I'm using continuum 1.0.3, and also the continuum-rpc-client v1.0.3.
Sorry for not including that originally.
Also, I noticed that project.getState() will return the state that shows on the
Continuum Projects page, which, has a bug and isn't always correct.
Thanks,
Baron
-Original Messag
I tried playing with the java XML-RPC client for continuum, and had a couple
questions.
- For a given project, I would like to query the state of the most recent build
for each build definition. Is this possible?
- For a given project, what is contained in the list returned by
project.getBuil
I've had a similar problem when using continuum with SVN. I end up with two
projects that have the exact same SCM url, but different continuum build id's
(sequential, in my case). Updating the build definition for one, automatically
updates it for the other. However, updates inside svn only trig
Try a mvn site:site on your cmd line to see the maven generated site, including
your cobertura report. Inside of continuum, I find it more useful to set
yourself up to use the mvn site-deploy goal. There is a site guide on the maven
website with more information about using/deploying maven gener
Thanks for the feedback. Definitely good to know others are in the same boat,
and I definitely never would've thought of the scm bootstrapping solution.
Thanks,
Baron
-Original Message-
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: Fri 7/21/2006 8:49 PM
To: continuum-users@maven.apache.
I was wondering if anyone has developed any best practices for performing a
release with maven when using continuum? To cut things down to the basics,
seems you pretty much have to:
1. Stop continuum
2. Perform the release (including deployment of jars to repository)
3. Restart continuum
Is thi
Another thing you can do, is create a settings.xml (which, doesn't help with
the security concerns Emmanuel listed) which contains something like:
website
someusername
password
where the id matches up with the site id in your pom.xml. That should at least
get
Even though it's a local machine, have you verified that you can scp a file to
yourself? Perhaps you need to permanently accept the ssh key?
-Original Message-
From: Srinivas Pavani [mailto:[EMAIL PROTECTED]
Sent: Thu 7/6/2006 11:01 AM
To: continuum-users@maven.apache.org
Subject: Site d