Vincent Massol wrote: >>No, the plugin is backwards compat as is. Cruisecontrol can be updated >>to use the URL itself. >> >> > >How? CruiseControl needs the module name. How can I get it from the SCM >plugin or from the URL? > > not according to this: http://cruisecontrol.sourceforge.net/main/configxml.html#svn.
Repository location is a full URL, and I'm sure if you put the whole URL in there instead of the root it would work as expected. The SCM plugin still supports the notation of ':' replacing one of the '/' to signify a "module" - however this is really arbitrary in Subversion, and is only used so the plugins can differentiate the root of the project from the subdirectories. To subversion, it's all the same. The "Root" of the repository is actually /repos/asf - not the value of maven.scm.svn.root, because that really isn't that useful given the current property set - the URL is all that is needed. > > >>I'm still thinking about this WRT subversion. At the moment, you can use >>a colon to specify your "module". However, this really isn't a natural >>thing for SVN, and the root is actually http:/.../repos/asf. >> >> > >Actually you can't... I've tried running "maven scm:checkout" and I get: > >Command output: >svn: URL 'https://[...]/trunk/code/webapp:webapp' doesn't exist > > So you're saying that .../trunk/code/webapp/webapp does exist, but this fails? Ok, then the SCM plugin needs to have a change to remain backwards compat. >So it seems that the scm plugin is not completely backward compatible. What >do I do: > >- I need the module specified as otherwise the cruisecontrol plugin will not >work. I'm happy to modify it but I don't know how to get the module name... > > This is what I'm trying to tackle. All we have is pom.artifactId which may or may not match up. >- When I run scm:checkout it says that it shouldn't end with a module > > Can you provide a more specific error message? I'm not sure what you are referring to here. > > >>What we probably expect the "module" to be is the last directory in the >>path of the root project, or last two if the last is "trunk", or the >>last 3 if one a branch or tag. >> >> > >But we can't assume this. Someone can use a name other than trunk, no? Same >for tags, branches. > >My feeling is that we need to split the URL into 2: one for the root and one >for the module... Sounds familiar? > > That's not enough - because say you specify the URL as: http://svn.apache.org/repos/asf/maven/maven-1/core/trunk:src/test/touchstone-build what happens when you are on the MAVEN-1_0-BRANCH? How do you translate this to http://svn.apache.org/repos/asf/maven/maven-1/core/branches/MAVEN-1_0-BRANCH:src/test/touchstone-build And it is different again under svn:externals. Really, you need to be able to make some substititutions. This will all be worked through in time, but beyond the 1.5 release. > > >>I think we actually need to be able to have the URL specify this, but >>really I haven't wrapped my head around best practices here and the >>number of people using svn:externals is also confusing it. I'd like >>something that works with both svn:externals, and the default layout. >> >> > >Thanks >-Vincent > > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
