Re: Using xfire interface to initiate the build of a project?
The xfire interface wasn't released because we need to test/fix it. You can find it in subversion in continuum-xfire module. Emmanuel Donszelmann, Mark a écrit : Hi can I use the Xfire/SOAP interface to initiate the build of a project, as suggested by: http://maven.apache.org/continuum/guides/mini/guide-soap-api.html If so, where can I find the jar file to link against ? Regards Mark Donszelmann
Re: Configuration of jabber notifier
In jabber notifier configuration screen, you need to add the recipient too. Note: your google sender must be a friend of your recipient, and you can't use the same use for sender and recipient because google talk doesn't accept two connections for the same user. Emmanuel Anthony Bargnesi a écrit : Hello all, I noticed that there is no documentation on the jabber notifier's configuration options. The FAQ mentions the config values that are needed for google talk but it does not mentiond the tags needed. If someone can inform me what the configuration block in the notifier should look like for the following: *Jabber Host :* talk.google.com *Jabber Port :* 5222 *Jabber Login :* abargnesi *Jabber Domain Name :* gmail.com *Is it a SSL Connection?* false Thanks, Anthony Bargnesi
Re: How to setup ant build file that is not under root?
I suppose you use continuum 1.0.1. It wasn't possible with it. We fixed it in continuum 1.0.2 Emmanuel [EMAIL PROTECTED] a écrit : Hey, i try to build a projekt, that's Build File is not in projekt root. So i setup the POM File to \deploy\xyz\build.xml So the absoluth pat is workingDir\6\deploy\xyz\build.xml But i doesn't work, what's wrong? Fredy
Re: How to setup ant build file that is not under root?
Than ks anyway ;-) continuum-users@maven.apache.org schrieb am 12.12.05 15:19:41: I suppose you use continuum 1.0.1. It wasn't possible with it. We fixed it in continuum 1.0.2 Emmanuel [EMAIL PROTECTED] a écrit : Hey, i try to build a projekt, that's Build File is not in projekt root. So i setup the POM File to \deploy\xyz\build.xml So the absoluth pat is workingDir\6\deploy\xyz\build.xml But i doesn't work, what's wrong? Fredy -- Mit freundlichen Grüßen Fred Robert Hauschel http://www.Hauschel.de Mobil:0179 - 6917092 Telefon: 07427 - 91179 Fax: 07427 - 91178
Cannot add Perforce project to Continuum 1.0.2
Hi, I've just installed Continuum 1.0.2 for testing. I'm unable to add a Perforce project by URL. I'm trying to add the following URL: scm:perforce:[EMAIL PROTECTED]:1666://depot/osc-fingerpost-dispatch er/MAIN/project.xml This gives me the message [ You must provide a valid url ]. background is a valid perforce user, my P4PORT is development:1666 and the path //depot/osc-fingerpost-dispatcher-MAIN-project.xml points to my Maven 1 POM. I've tried all sorts of combinations of the URL, but I always get the same message. I am able to add the project by specifying a local filename, but then building the project gives a Provider message: Unable to sync in the mailed output. -- Neil http://www.bbc.co.uk/ This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. http://www.bbc.co.uk/ This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this.
Continuum 1.0.2 ERROR: Could not write pid file
Hello all, Has anybody stumbled into this error, any fixes/workarounds? I'm running Continuum 1.0.2 in Solaris 5.8. bash-2.03$ ./run.sh console Running continuum... wrapper | ERROR: Could not write pid file ./continuum.pid: Permission denied Regards, Alex
[Fwd: Re: Perforce provider generates error]
---BeginMessage--- Robert, your path should just be //depot/CRUD/securityApp (remove a slash). mike -Original Message- From: Stone, Robert [mailto:[EMAIL PROTECTED] Sent: Friday, December 09, 2005 3:18 PM To: continuum-users@maven.apache.org Subject: RE: Perforce provider generates error Thanks, Emmanuel I'm trying 1.0.2 today. The error I had previously is gone but I get another one: Provider message: Unable to sync which, probably, means that my p4 client is not configured correctly. Just to make sure that I'm doing the right thing here're my settings(can you verify?) - 1. I'm using maven2 2. Here's a scm snippet from pom.xml scm connection scm:perforce:[EMAIL PROTECTED]:1666:///depot/CRUD/securityApp /connection /scm ciManagement systemcontinuum/system notifiers notifier typemail/type configuration address[EMAIL PROTECTED]/address /configuration /notifier /notifiers /ciManagement Regards, Robert Stone -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Friday, December 09, 2005 12:54 AM To: continuum-users@maven.apache.org Subject: Re: Perforce provider generates error hi I'm happy to see a perforce tester for Continuum. You don't need to use beta-3-SNAPSHOT, but beta-2 of maven-scm. PErforce provider isn't the only one jar to add/update. You need to update too : maven-scm-api and maven-scm-manager-plexus. I'll release continuum 1.0.2 today and all jars will be in it, but if you can test it before and send us the result, it will be great. Emmanuel Stone, Robert a écrit : Hi, Running continuum-1.0.1 on Linux, Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03) I've added maven-scm-provider-perforce-1.0-beta-3-SNAPSHOT.jar to /opt/continuum-1.0.1/apps/continuum/lib. After I restart continuum and attempt to access the site the following exception is generated which is displayed in browser and duplicated in the log file INFO | jvm 1| 2005/12/08 18:07:12 | javax.servlet.ServletException: could not lookup service org.codehaus.plexus.summit.pipeline.Pipeline INFO | jvm 1| 2005/12/08 18:07:12 | at org.codehaus.plexus.servlet.PlexusServletUtils.lookup(PlexusServletUti ls .java:82) INFO | jvm 1| 2005/12/08 18:07:12 | at org.codehaus.plexus.servlet.PlexusServlet.lookup(PlexusServlet.java:59 ) INFO | jvm 1| 2005/12/08 18:07:12 | at org.codehaus.plexus.summit.Summit.doGet(Summit.java:52) INFO | jvm 1| 2005/12/08 18:07:12 | at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) INFO | jvm 1| 2005/12/08 18:07:12 | at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) INFO | jvm 1| 2005/12/08 18:07:12 | at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) INFO | jvm 1| 2005/12/08 18:07:12 | at org.mortbay.jetty.servlet.Invoker.service(Invoker.java:184) INFO | jvm 1| 2005/12/08 18:07:12 | at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) INFO | jvm 1| 2005/12/08 18:07:12 | at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) INFO | jvm 1| 2005/12/08 18:07:12 | at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicatio nH andler.java:294) INFO | jvm 1| 2005/12/08 18:07:12 | at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:56 7) INFO | jvm 1| 2005/12/08 18:07:12 | at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) INFO | jvm 1| 2005/12/08 18:07:12 | at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationC on text.java:525) INFO | jvm 1| 2005/12/08 18:07:12 | at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) INFO | jvm 1| 2005/12/08 18:07:12 | at org.mortbay.http.HttpServer.service(HttpServer.java:879) INFO | jvm 1| 2005/12/08 18:07:12 | at org.mortbay.http.HttpConnection.service(HttpConnection.java:789) INFO | jvm 1| 2005/12/08 18:07:12 | at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) INFO | jvm 1| 2005/12/08 18:07:12 | at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) INFO | jvm 1| 2005/12/08 18:07:12 | at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:2 18 ) INFO | jvm 1| 2005/12/08 18:07:12 | at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331) INFO | jvm 1| 2005/12/08 18:07:12 | at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520) INFO |
Re: Continuum 1.0.2
No, you don't need to use the shell feature for adding a m2 project with modules. You use the shell feature if you want to see your projects as one in continuum. Emmanuel dan tran a écrit : could you post your pom? Btw, if you define modules in your pom, you will need to use a shell to wrap the call http://maven.apache.org/continuum/faqs.html -D On 12/12/05, Michael Fiedler [EMAIL PROTECTED] wrote: I am able to execute the maven (mvn) validate and install to the same pom. I also added the subprojects (instead of the higher level pom) into Continuum and both worked fine. How can I get a verbose message regarding the pom being invalid? Thank you, Michael -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Monday, December 12, 2005 1:59 PM To: continuum-users@maven.apache.org Subject: Re: Continuum 1.0.2 are you able to build your project manually before addin it to continuum? it seems, your pom is not a 4.0.0 model. -D On 12/12/05, Michael Fiedler [EMAIL PROTECTED] wrote: Hi, I tried to load a maven2 pom into Continuum 1.0.2. It complained that the POM was invalid. However, when I ran the maven2 validate goal on the same file, nothing was wrong. Does Continuum have a different validate? How can I find out more about what was invalid? console: jvm 1| 2005-12-12 12:43:24,312 [SocketListener0-0] ERROR MavenBuilderHelper - Cannot build maven project from C:\DOCUME~1\OMA-SV~1\LOCALS~1\Temp\continuum-10186.tmp. jvm 1| org.apache.maven.project.InvalidProjectModelException: Invalid POM (not v4.0.0 modelVersion) jvm 1| at org.apache.maven.project.DefaultMavenProjectBuilder.readModel( DefaultMavenProjectBuilder.java:1086) jvm 1| at org.apache.maven.project.DefaultMavenProjectBuilder.readModel( DefaultMavenProjectBuilder.java:1057) jvm 1| at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile( DefaultMavenProjectBuilder.java:291) jvm 1| at org.apache.maven.project.DefaultMavenProjectBuilder.build( DefaultMavenProjectBuilder.java:283) jvm 1| at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject (DefaultMavenBuilderHelper.java:260) jvm 1| at org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilder.readModules (MavenTwoContinuumProjectBuilder.java:100) jvm 1| at org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilder.buildProjectsFromMetadata (MavenTwoContinuumProjectBuilder.java:83) jvm 1| at org.apache.maven.continuum.core.action.CreateProjectsFromMetadata.execute( CreateProjectsFromMetadata.java:63) jvm 1| at org.apache.maven.continuum.DefaultContinuum.executeAction( DefaultContinuum.java:1809) jvm 1| at org.apache.maven.continuum.DefaultContinuum.executeAddProjectsFromMetadataActivity (DefaultContinuum.java:674) jvm 1| at org.apache.maven.continuum.DefaultContinuum.addMavenTwoProject( DefaultContinuum.java:582) jvm 1| at org.apache.maven.continuum.web.action.AddMavenTwoProject.uponSuccessfulValidation (AddMavenTwoProject.java:52) jvm 1| at org.codehaus.plexus.formica.action.AbstractEntityAction.execute( AbstractEntityAction.java:136) jvm 1| at org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke( ActionValve.java:68) jvm 1| at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke( AbstractPipeline.java:70) jvm 1| at org.codehaus.plexus.summit.Summit.doGet(Summit.java :54) jvm 1| at org.codehaus.plexus.summit.Summit.doPost(Summit.java :108) jvm 1| at javax.servlet.http.HttpServlet.service( HttpServlet.java :615) jvm 1| at javax.servlet.http.HttpServlet.service( HttpServlet.java :688) jvm 1| at org.mortbay.jetty.servlet.ServletHolder.handle( ServletHolder.java:358) jvm 1| at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch( WebApplicationHandler.java:294) jvm 1| at org.mortbay.jetty.servlet.ServletHandler.handle( ServletHandler.java:567) jvm 1| at org.mortbay.http.HttpContext.handle(HttpContext.java :1807) jvm 1| at org.mortbay.jetty.servlet.WebApplicationContext.handle( WebApplicationContext.java:525) jvm 1| at org.mortbay.http.HttpContext.handle(HttpContext.java :1757) jvm 1| at org.mortbay.http.HttpServer.service(HttpServer.java :879) jvm 1| at org.mortbay.http.HttpConnection.service( HttpConnection.java:789) jvm 1| at org.mortbay.http.HttpConnection.handleNext( HttpConnection.java:960) jvm 1| at org.mortbay.http.HttpConnection.handle( HttpConnection.java:806) jvm 1| at org.mortbay.http.SocketListener.handleConnection( SocketListener.java:218) jvm 1| at org.mortbay.util.ThreadedServer.handle( ThreadedServer.java:331) jvm 1| at org.mortbay.util.ThreadPool$PoolThread.run(
