http://freshmeat.net/projects/ntlmaps/
Run this proxy and tell your Subversion client, or Maven, to use the APS
proxy.
This will work for http but won't for https. ntlmaps has problems with
chunked encodings.
From the original problem email the scm url looks like it is http, so
you should be
It's planned for 1.1
Is there an ETA for 1.1?
Or better yet, is someone already working on it and if I get some time
can help out?
And it does not help me to make continuum run in batch.
I'm not suggesting to run continuum in batch.
What I am saying is that you should be able to run the same mvn
command as continuum does. When you that command it should not prompt
for any information and complete correctly (i.e in a batch
On 7/5/06, Mark Reynolds [EMAIL PROTECTED] wrote:
I have changed my multi-project build so it only builds the parent pom
without --non-recursive.
There are some double negatives here.
Do you mean you have deleted your other projects from the continuum
build and that there is now only one
But when adding the module pom I think it is failing to find the
parent pom (or even looking for it) and gives you an error that the
version for the dependency is mandatory and missing.
Perhaps the parent pom's module has not been 'installed' in continuum's
repository with the
Any chance a continuum developer could take a look at the notes I
added to http://jira.codehaus.org/browse/CONTINUUM-243 and see if what
I have written is on the correct path?
I notice in the continuum logs that the following command is run to
update the project prior to running a build:
cvs -z3 -f -d :pserver:anonymous@host:path -q update -d
The -P for pruning should als be included to clean up when stuff is
deleted from cvs.
Is there a reason that this option is
If I add another module to the parent pom and then rebuild the parent
project in continuum the new module does not get added as another
project.
If I re-add the pom file via Maven 2.0+ Project link (I am using
file:// urls to do this) I get a second parent project but not
sub-modules.
If I try
While I'm discussing this, I notice because I am using the recommended
project layout:
ROOT
- pom.xml
- module1/pom.xml
- moduel2/pom.xml
That to rebuild the ROOT project it takes forever since it has to
checkout the entire CVS tree.
Whereas the module builds only checkout the module
