Re: Re: Continuum Gives a Not a v4.0.0 POM exception.

2006-08-29 Thread Torsten Curdt

Check your local repository. I've encountered a similar problem. Maven
downloaded an html error page instead of a valid pom. I had to change
the mirror and remove the invalid poms from my .m2/repository. Never
expected maven to be so stupid and not realize that it had downloaded
crap :-(

HTH
--
Torsten

On 8/29/06, Emmanuel Venisse [EMAIL PROTECTED] wrote:



Piyush Kumar Nahata a écrit :


 Hi,
   When I give the URL with the POM.xml included in it, as 
http://10.225.96.127:8089/svn/repos/steam/common/pom.xml 
http://10.225.96.127:8089/svn/repos/steam/common/pom.xml , I get a different 
Error.

 Could not download http://10.225.96.127:8089/svn/repos/steam/common/pom.xml: 
/work/servers/continuum-1.0.3/temp/continuum/svn/repos/steam/common/pom.xml (Not a 
directory)

 When I browsed to this path, I found that Steam is a directory, but common is 
a file and not a directory. Hence, the error is thrown as Not a directory. Any 
idea, why does common gets created as a file and not a directory.

 The following is the content of the common file. I decipher it is the same as what 
gets printed on the browser when I browse to the location  
http://10.225.96.127:8089/svn/repos/steam/common/ 
http://10.225.96.127:8089/svn/repos/steam/common/pom.xml

 htmlheadtitleRevision 2265: /steam/common/title/head
 body
  h2Revision 2265: /steam/common/h2
  ul
   lia href=../../a/li
   lia href=conf/conf//a/li
   lia href=pom.xmlpom.xml/a/li
   lia href=src/src//a/li
  /ul
  hr noshadeemPowered by a href=http://subversion.tigris.org/;Subversion/a 
http://subversion.tigris.org/;Subversion/a  version 1.1.4 (r13838)./em
 /body/html

This output isn't a pom but a directory listing of common directory

Emmanuel

  Thanks in advance

 Regards,
 Piyush Kumar Nahata,


 -Original Message-
 From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ]
 Sent: Tuesday, August 29, 2006 7:23 PM
 To: continuum-users@maven.apache.org
 Subject: Re: Continuum Gives a Not a v4.0.0 POM exception.


 Piyush Kumar Nahata a écrit :
 Hi all,
I'm using Continuum-1.0.3 with Maven 2.0.4. I have a multi project.
 When I try to give the URL of the child project, I get the folowing
 Error

 --START OF STACK
 TRACE

 2006-08-29 09:24:38,643 [SocketListener0-9] INFO
 ContinuumProjectBuilder:maven-two-builder - Downloading
 http://10.225.96.127:8089/svn/repos/steam/common 
http://10.225.96.127:8089/svn/repos/steam/common
 2006-08-29 09:24:38,678 [SocketListener0-9] ERROR MavenBuilderHelper
 - Cannot build maven project from
 /work/servers/continuum-1.0.3/temp/continuum/svn/repos/steam/common
 (Not a v4.0.0 POM.).

 org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0 POM.
 at
 org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultM
 av
 enProjectBuilder.java:1299)
 at
 org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultM
 av
 enProjectBuilder.java:1270)
 at
 org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFil
 eI
 nternal(DefaultMavenProjectBuilder.java:414)
 at
 org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMaven
 Pr
 ojectBuilder.java:201)
 at
 org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.
 getMavenProject(DefaultMavenBuilderHelper.java:306)
 at
 org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProj
 ec
 tBuilder.readModules(MavenTwoContinuumProjectBuilder.java:99)
 at
 org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProj
 ec
 tBuilder.buildProjectsFromMetadata(MavenTwoContinuumProjectBuilder.java:
 83)
 at
 org.apache.maven.continuum.core.action.CreateProjectsFromMetadata.exec
 ut
 e(CreateProjectsFromMetadata.java:74)
 at
 org.apache.maven.continuum.DefaultContinuum.executeAction(DefaultConti
 nu
 um.java:2089)
 at
 org.apache.maven.continuum.DefaultContinuum.executeAddProjectsFromMeta
 da
 taActivity(DefaultContinuum.java:804)
 at
 org.apache.maven.continuum.DefaultContinuum.addMavenTwoProject(Default
 Co
 ntinuum.java:712)
 at
 org.apache.maven.continuum.web.action.AddMavenTwoProject.uponSuccessfu
 lV
 alidation(AddMavenTwoProject.java:52)
 at
 org.codehaus.plexus.formica.action.AbstractEntityAction.execute(Abstra
 ct
 EntityAction.java:136)
 at
 org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionVal
 ve
 .java:68)
 at
 org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPi
 pe
 line.java:70)
 at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54)
 at org.codehaus.plexus.summit.Summit.doPost(Summit.java:108)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at
 org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358)

Re: Why Continuum?

2006-02-21 Thread Torsten Curdt


On 22.02.2006, at 08:34, Johnson, Jonathan wrote:


For instance Continuum does not have the feature yet to invoke
builds based on SCM changes.


Huh? ...it queries the SCM periodically to check for changes.
If there are changes it kicks off a build.

cheers
--
Torsten



smime.p7s
Description: S/MIME cryptographic signature