I do; the pom.xml is identical to my workstation pom.xml. And the same
pom.xml works in Continuum 1.0.3.
On Feb 7, 2008 3:03 PM, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
> do you have scm element defined in the pom stored in your svn?
>
> Emmanuel
>
>
> On Feb 7, 2008 9:25 PM, Jan Nielsen <[EMAIL PROTECTED]> wrote:
>
> > In Continuum 1.1, installed as a WAR in GlassFish 9.1ur1 on Windows, I
> > have a multi-module Maven 2 POM being uploaded with a POM Url:
> >
> > file:///c:/dev/myproj/trunk/pom.xml
> >
> > with appropriate username, password, "Defined by POM" project group,
> > and a checked "load only root as recursive build" and the default
> > build definition template ("Default"). I have enabled file scheme;
> > svn.exe is part of the %PATH%; and the pom.xml has the following scm
> > element (sub-modules do not have an SCM element):
> >
> > <scm>
> > <connection>scm:svn:svn://xxx.xxx.xxx.xxx/myproj/trunk</connection>
> >
> >
> > <developerConnection>scm:svn:svn://xxx.xxx.xxx.xxx/myproj/trunk</developerConnection>
> > <url>http://xxx.xxx.xxx/view/myproj/trunk/</url>
> > </scm>
> >
> > The build from CLI with Maven 2.0.8 works fine, including the site
> > goal which uses the scm element data successfully in the StatScm
> > plugin; and this POM is successfully executed by Continuum 1.0.3 on
> > Tomcat 6.0 instance to build everything including the site goal which
> > includes the StatScm plugin.
> >
> > I found a few relevant other posts like:
> >
> >
> > http://www.nabble.com/trouble-adding-Maven-2.0-pom-td13778433.html#a13778433
> >
> > but in "myproj" is, in fact, in Subversion and the SCM URLs appear to
> > be correct.
> >
> > Any ideas?
> >
> >
> > Thanks,
> >
> > -Jan
> >
>
