Re: Missing 'scm' element in the POM.
It turns out that subproj23 did not have a parent element. As a result Continuum spits out a missing 'scm' message; it's interesting that Maven from the CLI does not complain about this. It would be nice(r) if Continuum would identify which module caused the error. Want to see it yourself? Do this: -check-out continuum -re-configure 1.1 to allow file scheme -remove the parent from a (sub-)module; see below -add the continuum project as a Maven 2.0 project via file scheme -Jan --- maven-continuum-plugin/pom.xml (revision 620407) +++ maven-continuum-plugin/pom.xml (working copy) @@ -18,24 +18,22 @@ ~ under the License. -- project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache. org/maven-v4_0_0.xsd - parent -artifactIdcontinuum-parent/artifactId -groupIdorg.apache.maven.continuum/groupId -version1.1/version - /parent modelVersion4.0.0/modelVersion groupIdorg.apache.maven.plugins/groupId artifactIdmaven-continuum-plugin/artifactId packagingmaven-plugin/packaging nameMaven Continuum Plugin/name + version1.1/version dependencies dependency groupIdorg.apache.maven.continuum/groupId artifactIdcontinuum-api/artifactId + version1.1/version /dependency dependency groupIdorg.apache.maven.continuum/groupId artifactIdcontinuum-xmlrpc-client/artifactId + version1.1/version /dependency dependency groupIdorg.apache.maven/groupId On Feb 8, 2008 9:40 AM, Jan Nielsen [EMAIL PROTECTED] wrote: The structure in Subversion is: myproj/pom.xml myproj/subproj1/pom.xml myproj/subproj2/pom.xml with a module definition of: modules modulesubproj1/module modulesubproj2/module /modules So, the sub-modules are sub-projects of the root module in Subversion. -Jan On Feb 7, 2008 5:11 PM, Jan Nielsen [EMAIL PROTECTED] wrote: 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 connectionscm:svn:svn://xxx.xxx.xxx.xxx/myproj/trunk/connection developerConnectionscm:svn:svn://xxx.xxx.xxx.xxx/myproj/trunk/developerConnection urlhttp://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
Missing 'scm' element in the POM.
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 connectionscm:svn:svn://xxx.xxx.xxx.xxx/myproj/trunk/connection developerConnectionscm:svn:svn://xxx.xxx.xxx.xxx/myproj/trunk/developerConnection urlhttp://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
Re: Missing 'scm' element in the POM.
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 connectionscm:svn:svn://xxx.xxx.xxx.xxx/myproj/trunk/connection developerConnectionscm:svn:svn://xxx.xxx.xxx.xxx/myproj/trunk/developerConnection urlhttp://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
Re: Missing 'scm' element in the POM.
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 connectionscm:svn:svn://xxx.xxx.xxx.xxx/myproj/trunk/connection developerConnectionscm:svn:svn://xxx.xxx.xxx.xxx/myproj/trunk/developerConnection urlhttp://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
