RE: AddressException in notifying with multiple email addresses
Adam,
I had the same problem. I wanted to define the notifications in the POM
and not through the Continuum admin screen. The whole comma (why not
';'?) separated list thing never worked for me. So in each of my sub
module POM.XML files I added sections like this and it has worked
perfectly since.
(A comma separate list is really not a good idea since it circumvents
the advantages of well-formed and repeatable XML elements.)
Continuum
http://yourcontinuumservermachine:8080/continuum
mail
[EMAIL PROTECTED]
true
true
false
true
mail
[EMAIL PROTECTED]
true
true
false
true
mail
[EMAIL PROTECTED]
true
true
true
true
I tried adding this notifiers list to the parent POM.XML but that did
not work. I had to add it to each sub-module pom.xml. I also tried
referencing the list of the developers ids in my parent pom to get their
emails but that did not work either. From what I have experienced the
list and the lists are separate even though
some of the information is duplicated and cannot be connected.
Good luck/
- Jonathan
-Original Message-
From: Adam Hardy [mailto:[EMAIL PROTECTED]
Sent: Friday, September 08, 2006 1:34 PM
To: continuum-users@maven.apache.org
Subject: AddressException in notifying with multiple email addresses
Hi Continuum People,
I am looking at a problem whose solution has eluded me for the past
couple of hours.
I set up my continuum with a single notification address via the pom.xml
and everything worked. I then added extra email addresses delimited by
commas so:
[EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED],jua
[EMAIL PROTECTED]
and continuum 1.0.3 seemed to like it and picked it up and displayed it
in the project config. Javamail 1.3.2 though does not like it. I get the
stack trace:
javax.mail.internet.AddressException: Illegal route-addr in string
[EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED],juan.cerve
[EMAIL PROTECTED]''
(see more log output below).
Interestingly sendmail on my linux box where continuum runs is quite
happy with the format:
[EMAIL PROTECTED]:/ctxtools/continuum-1.0.3$ /usr/sbin/sendmail
[EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED],juan.cervera
@no.com
Lastly, here's the application.xml for the notification. Any help
gratefully received.
Adam
org.codehaus.plexus.notification.notifier.Notifier
mail
org.apache.maven.continuum.notification.mail.MailContinu
umNotifier
org.codehaus.plexus.velocity.VelocityComponent
org.apache.maven.continuum.store.ContinuumStore
org.codehaus.plexus.mailsender.MailSender
org.apache.maven.continuum.configuration.ConfigurationService
EEE, d MMM HH:mm:ss Z
true
true
org.codehaus.plexus.notification.RecipientSource
org.apache.maven.continuum.notification.ContinuumRecipie
ntSource
org.codehaus.plexus.mailsender.MailSender
org.codehaus.plexus.mailsender.javamail.JavamailMailSend
er
localhost
25
com.sun.net.ssl.internal.ssl.Provider
soa
soa1
false
jvm 1| 2006-09-08 17:44:17,616 [Thread-2] INFO
ContinuumBuildExecutor:maven2 - Exit code: 1
jvm 1| 2006-09-08 17:44:17,920 [Thread-2] INFO Notifier:mail
- Sending message: From '"[EMAIL PROTECTED]"
<[EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED],juan.cerver
[EMAIL PROTECTED]>'.
jvm 1| 2006-09-08 17:44:17,920 [Thread-2] INFO Notifier:mail
- Recipient: To '<[EMAIL PROTECTED]>'.
jvm 1| 2006-09-08 17:44:17,921 [Thread-2] INFO Notifier:mail
- Recipient: To '<[EMAIL PROTECTED]>'.
jvm 1| 2006-09-08 17:44:17,922 [Thread-2] INFO Notifier:mail
- Recipient: To '<[EMAIL PROTECTED]>'.
jvm 1| 2006-09-08 17:44:17,922 [Thread-2] INFO Notifier:mail
- Recipient: To '<[EMAIL PROTECTED]>'.
jvm 1| DEBUG: JavaMail version 1.3.2
jvm 1| DEBUG: java.io.FileNotFoundException:
/ctxtools/jdk1.5.0_06/jre/lib/javamail.providers (No such file or
directory)
jvm 1| DEBUG: !anyLoaded
jvm 1| DEBUG: not loading resource: /META-INF/javamail.providers
jvm 1| DEBUG: successfully loaded resource:
/META-INF/javamail.default.providers
jvm 1| DEBUG: Tables of loaded providers
jvm 1| DEBUG: Providers Listed By Class Name:
{com.sun.mail.smtp.SMTPSSLTransport=javax.mail.Provider[TRANSPORT,smtps,
com.sun.mail.smtp.SMTPSSLTranspor
RE: One sub module randomly appears twice after adding a parent multi-module 1.0.3
Adam, This is a very helpful workaround. It worked for me. Thanks, I updated the bug report with this comment. All, For those of your getting duplicate modules and cannot remove the duplicate make sure you go to the "Build Definitions" section and remove any goals. You should then be able to remove the duplicate module. - Jonathan -Original Message- From: Adam [mailto:[EMAIL PROTECTED] Sent: Thursday, August 03, 2006 8:45 AM To: continuum-users@maven.apache.org Subject: Re: One sub module randomly appears twice after adding a parent multi-module 1.0.3 I've had this as well. If you delete the build definitions from the doubled project, you should be able to delete the project then. On 8/1/06, Johnson, Jonathan <[EMAIL PROTECTED]> wrote: > Baron, > > Thanks for the reality check. I added our comments to a new Continuum > defect report > > http://jira.codehaus.org/browse/CONTINUUM-799 > > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 01, 2006 10:04 AM > To: continuum-users@maven.apache.org; continuum-users@maven.apache.org > Subject: RE: One sub module randomly appears twice after adding a parent > multi-module 1.0.3 > > I've had a similar problem when using continuum with SVN. I end up with > two projects that have the exact same SCM url, but different continuum > build id's (sequential, in my case). Updating the build definition for > one, automatically updates it for the other. However, updates inside svn > only trigger one of them to be built by continuum, and not both. If I > try to delete the duplicated project, I get the continuum error page > with the same error output. > > > -Original Message- > From: Jesse McConnell [mailto:[EMAIL PROTECTED] > Sent: Tue 8/1/2006 8:50 AM > To: continuum-users@maven.apache.org > Subject: Re: One sub module randomly appears twice after adding a parent > multi-module 1.0.3 > > have you looked into the working directory that corresponds to that > project id to see what is in there? > > in the working directory there should be a mess of numbered > directories corresponding to each of the projects as they exist in > continuum, mouse over the link to the project and you should see the > project id in the url. I would be interested to know what was checked > out in that sub directory...and if that project was assigned a > different project id then its duplicate. something is making > continuum think there is another project to get setup... > > thanks, > jesse > > On 8/1/06, Johnson, Jonathan <[EMAIL PROTECTED]> wrote: > > Using cvs but problem occurs before build happens and before cvs is > > accessed. Problem occurs when adding a parent pom.xml M2 project file > > via URL. Thanks for the link, I will submit the problem. > > > > -Original Message- > > From: Jesse McConnell [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, August 01, 2006 9:31 AM > > To: continuum-users@maven.apache.org > > Subject: Re: One sub module randomly appears twice after adding a > parent > > multi-module 1.0.3 > > > > hm, how odd... > > > > what scm are you using? > > > > also, could you file this at http://jira.codehaus.org/browse/CONTINUUM > > > > jesse > > > > On 7/31/06, Johnson, Jonathan <[EMAIL PROTECTED]> wrote: > > > One sub module randomly appears twice after adding a parent > > multi-module > > > to continuum 1.0.3. > > > > > > I have a parent maven 2 pom with 16 sub-modules. If I reset the > > > database ( by removing the database directory) and add my parent > > pom.xml > > > all the modules will be added correctly except one random module > will > > be > > > added twice. I tried this three times and a different module in the > > > list is duplicated once. This also happens after a fresh install of > > > version 1.0.3. > > > > > > If I run a "Build All" one of the duplicate modules builds, while > the > > > other remains with a "New" status. When attempting to remove the > > > duplicate module with the "New" status I get > > > > > > ognl.MethodFailedException: Method "removeProject" failed for object > > > [EMAIL PROTECTED] > > > [javax.jdo.JDOUserException: One or more instances could not be > > deleted > > > NestedThrowables: > > > javax.jdo.JDODataStoreException: Delete request failed: DELETE FROM > > > BUILDDEFINITION WHERE ID = ? > > > NestedThrowables: > > > SQL Exception: DELETE on table 'BUILDDEFINITION
RE: One sub module randomly appears twice after adding a parent multi-module 1.0.3
Baron, Thanks for the reality check. I added our comments to a new Continuum defect report http://jira.codehaus.org/browse/CONTINUUM-799 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 01, 2006 10:04 AM To: continuum-users@maven.apache.org; continuum-users@maven.apache.org Subject: RE: One sub module randomly appears twice after adding a parent multi-module 1.0.3 I've had a similar problem when using continuum with SVN. I end up with two projects that have the exact same SCM url, but different continuum build id's (sequential, in my case). Updating the build definition for one, automatically updates it for the other. However, updates inside svn only trigger one of them to be built by continuum, and not both. If I try to delete the duplicated project, I get the continuum error page with the same error output. -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Tue 8/1/2006 8:50 AM To: continuum-users@maven.apache.org Subject: Re: One sub module randomly appears twice after adding a parent multi-module 1.0.3 have you looked into the working directory that corresponds to that project id to see what is in there? in the working directory there should be a mess of numbered directories corresponding to each of the projects as they exist in continuum, mouse over the link to the project and you should see the project id in the url. I would be interested to know what was checked out in that sub directory...and if that project was assigned a different project id then its duplicate. something is making continuum think there is another project to get setup... thanks, jesse On 8/1/06, Johnson, Jonathan <[EMAIL PROTECTED]> wrote: > Using cvs but problem occurs before build happens and before cvs is > accessed. Problem occurs when adding a parent pom.xml M2 project file > via URL. Thanks for the link, I will submit the problem. > > -Original Message- > From: Jesse McConnell [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 01, 2006 9:31 AM > To: continuum-users@maven.apache.org > Subject: Re: One sub module randomly appears twice after adding a parent > multi-module 1.0.3 > > hm, how odd... > > what scm are you using? > > also, could you file this at http://jira.codehaus.org/browse/CONTINUUM > > jesse > > On 7/31/06, Johnson, Jonathan <[EMAIL PROTECTED]> wrote: > > One sub module randomly appears twice after adding a parent > multi-module > > to continuum 1.0.3. > > > > I have a parent maven 2 pom with 16 sub-modules. If I reset the > > database ( by removing the database directory) and add my parent > pom.xml > > all the modules will be added correctly except one random module will > be > > added twice. I tried this three times and a different module in the > > list is duplicated once. This also happens after a fresh install of > > version 1.0.3. > > > > If I run a "Build All" one of the duplicate modules builds, while the > > other remains with a "New" status. When attempting to remove the > > duplicate module with the "New" status I get > > > > ognl.MethodFailedException: Method "removeProject" failed for object > > [EMAIL PROTECTED] > > [javax.jdo.JDOUserException: One or more instances could not be > deleted > > NestedThrowables: > > javax.jdo.JDODataStoreException: Delete request failed: DELETE FROM > > BUILDDEFINITION WHERE ID = ? > > NestedThrowables: > > SQL Exception: DELETE on table 'BUILDDEFINITION' caused a violation of > > foreign key constraint 'PROJECT_BUILP8_FK2' for key (10). The > statement > > has been rolled back.] > > at > ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:796) > > at > > ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) > > at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) > > at ognl.ASTMethod.getValueBody(ASTMethod.java:75) > > at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) > > at ognl.SimpleNode.getValue(SimpleNode.java:210) > > at ognl.Ognl.getValue(Ognl.java:333) > > at ognl.Ognl.getValue(Ognl.java:378) > > at ognl.Ognl.getValue(Ognl.java:357) > > at > > > org.codehaus.plexus.formica.action.DeleteEntity.uponSuccessfulValidation > > (DeleteEntity.java:57) > > at > > > org.codehaus.plexus.formica.action.DeleteEntity.execute(DeleteEntity.jav > > a:47) > > at > > > org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve > > .java:68) > > at > > > org.codehaus.plexus.summit.pipeli
RE: One sub module randomly appears twice after adding a parent multi-module 1.0.3
I looked in the working directory. I have 1-15 directories under working-directory. The module that is duplicated has an id of 10 and another of 16. The one that is 16 is the module that still has the status of "New" and throws the database DELETE exception when I try to remove the module from the Continuum list. >> what was checked out I don't fully understand your term "checked out". Perhaps the above description is enough. >> if that project was assigned a different project id Yes different ids (10 and 16) but working directory does not have a "16" folder. -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 01, 2006 9:51 AM To: continuum-users@maven.apache.org Subject: Re: One sub module randomly appears twice after adding a parent multi-module 1.0.3 have you looked into the working directory that corresponds to that project id to see what is in there? in the working directory there should be a mess of numbered directories corresponding to each of the projects as they exist in continuum, mouse over the link to the project and you should see the project id in the url. I would be interested to know what was checked out in that sub directory...and if that project was assigned a different project id then its duplicate. something is making continuum think there is another project to get setup... thanks, jesse On 8/1/06, Johnson, Jonathan <[EMAIL PROTECTED]> wrote: > Using cvs but problem occurs before build happens and before cvs is > accessed. Problem occurs when adding a parent pom.xml M2 project file > via URL. Thanks for the link, I will submit the problem. > > -Original Message- > From: Jesse McConnell [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 01, 2006 9:31 AM > To: continuum-users@maven.apache.org > Subject: Re: One sub module randomly appears twice after adding a parent > multi-module 1.0.3 > > hm, how odd... > > what scm are you using? > > also, could you file this at http://jira.codehaus.org/browse/CONTINUUM > > jesse > > On 7/31/06, Johnson, Jonathan <[EMAIL PROTECTED]> wrote: > > One sub module randomly appears twice after adding a parent > multi-module > > to continuum 1.0.3. > > > > I have a parent maven 2 pom with 16 sub-modules. If I reset the > > database ( by removing the database directory) and add my parent > pom.xml > > all the modules will be added correctly except one random module will > be > > added twice. I tried this three times and a different module in the > > list is duplicated once. This also happens after a fresh install of > > version 1.0.3. > > > > If I run a "Build All" one of the duplicate modules builds, while the > > other remains with a "New" status. When attempting to remove the > > duplicate module with the "New" status I get > > > > ognl.MethodFailedException: Method "removeProject" failed for object > > [EMAIL PROTECTED] > > [javax.jdo.JDOUserException: One or more instances could not be > deleted > > NestedThrowables: > > javax.jdo.JDODataStoreException: Delete request failed: DELETE FROM > > BUILDDEFINITION WHERE ID = ? > > NestedThrowables: > > SQL Exception: DELETE on table 'BUILDDEFINITION' caused a violation of > > foreign key constraint 'PROJECT_BUILP8_FK2' for key (10). The > statement > > has been rolled back.] > > at > ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:796) > > at > > ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) > > at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) > > at ognl.ASTMethod.getValueBody(ASTMethod.java:75) > > at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) > > at ognl.SimpleNode.getValue(SimpleNode.java:210) > > at ognl.Ognl.getValue(Ognl.java:333) > > at ognl.Ognl.getValue(Ognl.java:378) > > at ognl.Ognl.getValue(Ognl.java:357) > > at > > > org.codehaus.plexus.formica.action.DeleteEntity.uponSuccessfulValidation > > (DeleteEntity.java:57) > > at > > > org.codehaus.plexus.formica.action.DeleteEntity.execute(DeleteEntity.jav > > a:47) > > at > > > org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve > > .java:68) > > at > > > org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipe > > line.java:70) > > at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) > > at org.codehaus.plexus.summit.Summit.doPost(Summit.java:108) > > at > java
RE: One sub module randomly appears twice after adding a parent multi-module 1.0.3
Using cvs but problem occurs before build happens and before cvs is accessed. Problem occurs when adding a parent pom.xml M2 project file via URL. Thanks for the link, I will submit the problem. -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 01, 2006 9:31 AM To: continuum-users@maven.apache.org Subject: Re: One sub module randomly appears twice after adding a parent multi-module 1.0.3 hm, how odd... what scm are you using? also, could you file this at http://jira.codehaus.org/browse/CONTINUUM jesse On 7/31/06, Johnson, Jonathan <[EMAIL PROTECTED]> wrote: > One sub module randomly appears twice after adding a parent multi-module > to continuum 1.0.3. > > I have a parent maven 2 pom with 16 sub-modules. If I reset the > database ( by removing the database directory) and add my parent pom.xml > all the modules will be added correctly except one random module will be > added twice. I tried this three times and a different module in the > list is duplicated once. This also happens after a fresh install of > version 1.0.3. > > If I run a "Build All" one of the duplicate modules builds, while the > other remains with a "New" status. When attempting to remove the > duplicate module with the "New" status I get > > ognl.MethodFailedException: Method "removeProject" failed for object > [EMAIL PROTECTED] > [javax.jdo.JDOUserException: One or more instances could not be deleted > NestedThrowables: > javax.jdo.JDODataStoreException: Delete request failed: DELETE FROM > BUILDDEFINITION WHERE ID = ? > NestedThrowables: > SQL Exception: DELETE on table 'BUILDDEFINITION' caused a violation of > foreign key constraint 'PROJECT_BUILP8_FK2' for key (10). The statement > has been rolled back.] > at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:796) > at > ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) > at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) > at ognl.ASTMethod.getValueBody(ASTMethod.java:75) > at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) > at ognl.SimpleNode.getValue(SimpleNode.java:210) > at ognl.Ognl.getValue(Ognl.java:333) > at ognl.Ognl.getValue(Ognl.java:378) > at ognl.Ognl.getValue(Ognl.java:357) > at > org.codehaus.plexus.formica.action.DeleteEntity.uponSuccessfulValidation > (DeleteEntity.java:57) > at > org.codehaus.plexus.formica.action.DeleteEntity.execute(DeleteEntity.jav > a:47) > at > org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve > .java:68) > at > org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipe > 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) > at > org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationH > andler.java:294) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) > at > org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationCon > text.java:525) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) > at org.mortbay.http.HttpServer.service(HttpServer.java:879) > at > org.mortbay.http.HttpConnection.service(HttpConnection.java:789) > at > org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) > at > org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) > at > org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218 > ) > at > org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331) > at > org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520) > /-- Encapsulated exception \ > javax.jdo.JDOUserException: One or more instances could not be deleted > at > org.jpox.AbstractPersistenceManager.deletePersistentAll(AbstractPersiste > nceManager.java:1438) > at > org.jpox.store.rdbms.scostore.ElementContainerStore.clear(ElementContain > erStore.java:595) > at > org.jpox.store.mapping.CollectionMapping.preDelete(CollectionMapping.jav > a:304) > at > org.jpox.store.mapping.CollectionMapping.deleteDependent(CollectionMappi > ng.java:332) >
One sub module randomly appears twice after adding a parent multi-module 1.0.3
One sub module randomly appears twice after adding a parent multi-module to continuum 1.0.3. I have a parent maven 2 pom with 16 sub-modules. If I reset the database ( by removing the database directory) and add my parent pom.xml all the modules will be added correctly except one random module will be added twice. I tried this three times and a different module in the list is duplicated once. This also happens after a fresh install of version 1.0.3. If I run a "Build All" one of the duplicate modules builds, while the other remains with a "New" status. When attempting to remove the duplicate module with the "New" status I get ognl.MethodFailedException: Method "removeProject" failed for object [EMAIL PROTECTED] [javax.jdo.JDOUserException: One or more instances could not be deleted NestedThrowables: javax.jdo.JDODataStoreException: Delete request failed: DELETE FROM BUILDDEFINITION WHERE ID = ? NestedThrowables: SQL Exception: DELETE on table 'BUILDDEFINITION' caused a violation of foreign key constraint 'PROJECT_BUILP8_FK2' for key (10). The statement has been rolled back.] at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:796) at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) at ognl.ASTMethod.getValueBody(ASTMethod.java:75) at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) at ognl.SimpleNode.getValue(SimpleNode.java:210) at ognl.Ognl.getValue(Ognl.java:333) at ognl.Ognl.getValue(Ognl.java:378) at ognl.Ognl.getValue(Ognl.java:357) at org.codehaus.plexus.formica.action.DeleteEntity.uponSuccessfulValidation (DeleteEntity.java:57) at org.codehaus.plexus.formica.action.DeleteEntity.execute(DeleteEntity.jav a:47) at org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve .java:68) at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipe 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) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationH andler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationCon text.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.mortbay.http.HttpConnection.service(HttpConnection.java:789) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218 ) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520) /-- Encapsulated exception \ javax.jdo.JDOUserException: One or more instances could not be deleted at org.jpox.AbstractPersistenceManager.deletePersistentAll(AbstractPersiste nceManager.java:1438) at org.jpox.store.rdbms.scostore.ElementContainerStore.clear(ElementContain erStore.java:595) at org.jpox.store.mapping.CollectionMapping.preDelete(CollectionMapping.jav a:304) at org.jpox.store.mapping.CollectionMapping.deleteDependent(CollectionMappi ng.java:332) at org.jpox.store.rdbms.table.ClassTable.deleteDependent(ClassTable.java:22 80) at org.jpox.store.StoreManager.deleteDependent(StoreManager.java:838) at org.jpox.state.StateManagerImpl.deletePersistent(StateManagerImpl.java:4 049) at org.jpox.AbstractPersistenceManager.internalDeletePersistent(AbstractPer sistenceManager.java:1391) at org.jpox.AbstractPersistenceManager.deletePersistent(AbstractPersistence Manager.java:1402) at org.codehaus.plexus.jdo.PlexusJdoUtils.removeObject(PlexusJdoUtils.java: 53) at org.apache.maven.continuum.store.JdoContinuumStore.removeObject(JdoConti nuumStore.java:969) at org.apache.maven.continuum.store.JdoContinuumStore.removeProject(JdoCont inuumStore.java:901) at org.apache.maven.continuum.DefaultContinuum.removeProject(DefaultContinu um.java:328) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Me
Multiple modules with gobal developers list and sub-module notifiers list
I have not been able to get continuum to send emails when the build fails. On this page http://today.java.net/pub/a/today/2006/05/30/continuous-integration-with -continuum.html it indicates that one can put in a developers id (and not their email address) in the address element for the continuum address but I suspect this does not work with developers defined in the parent pom.xml and a ciManagement section defined in the sub-modules. Can someone confirm this? I have a parent/top-level pom.xml with a section like this... jjohnson Jonathan Johnson [EMAIL PROTECTED] 454 Life Sciences http://www.454.com Developer Administrator -5 In my maven 2 sub modules I have ciManagement sections like this. Continuum http://mymachine:8080/continuum mail jjohnson true true false true Thanks - Jonathan LEGAL NOTICE: Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this e-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately.
RE: Why Continuum?
Continuum checks for changes and builds on a time based schedule. An alternate (and better) approach would be to build after changes have been applied. Continuous integration tools have the ability to listen or get notified by the SCM system when changes have been made. You can configure the build to launch shortly after changes have been made to the codebase. The intelligence behind the feature launches a build after changes have been made but wait long enough to ensure it does not launch a build while more changes are being committed. A common problem with timed builds is if team mebers are in the middle of committing changes the build may fail. The Continuum team is planning this feature: http://maven.apache.org/continuum/planned-features.html -Original Message- From: Torsten Curdt [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 21, 2006 6:49 PM To: continuum-users@maven.apache.org Subject: Re: Why Continuum? 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 LEGAL NOTICE: Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this e-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately.
RE: Re: Why Continuum?
This is a good doc. Thanks. I don't think its entirely accurate though. For instance Continuum does not have the feature yet to invoke builds based on SCM changes. It is strictly a time based configuration. This document indicates differently. Its also says that CruiseControl does not support M2. Not sure if that is accurate now/still. It's a helpful and ambitious document, but is it being maintaining for accuracy over time? >> Continuum / M2 tighter integration My comment here is not based on fact, just an observation that the people behind these scenes of M2 and Continuum project a sense they are all pointing in the same, metaphorical direction. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Herscu Sent: Tuesday, February 21, 2006 3:55 PM To: continuum-users@maven.apache.org Subject: Re: Why Continuum? Jonathan, thanks for your fast reply. Finally, I have found a comparison here: http://docs.codehaus.org/display/DAMAGECONTROL/Continuous+Integration+Se rver+Feature+Matrix But, still I do not understand what is the "tighter integration with Maven 2" all about. Using CC I still can invoke Maven (1 or 2 -- does it matter?) through the shell interface -- isn't it? Johnson, Jonathan wrote: > If you are looking for a richer feature set stick with CruiseControl. > > Continuum is still relatively new and many features you have > CruiseControl are not yet available in Continuum. > > I chose to try Continuum because of my simple build requirements which > will grow hopefully with the Continuum and Maven 2 feature sets. In > addition I opted for Continuums tighter integration with Maven 2. > > If the feature sets were the same I would recommend Continuum because of > it tighter integration with Maven 2. > > Many of the feature you might expect to find in Continuum are really in > Maven 2 (where they should be, well.. at least when they are written as > a plugin for Maven 2). Be careful of comparing the apples to oranges. > Be aware that Maven 2 and Continuum have only been around for a few > months and more features are anticipated this year. > > > > > -Original Message- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Herscu > Sent: Tuesday, February 21, 2006 2:59 PM > To: continuum-users@maven.apache.org > Subject: Why Continuum? > > Hi all, > > I am trying to find the answer to this question with no success. > Currently, I am using CruiseControl -- why should I (or others like me) > switch to Continuum? > > Adrian. > > > LEGAL NOTICE: > Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this e-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately. > > >
RE: Why Continuum?
If you are looking for a richer feature set stick with CruiseControl. Continuum is still relatively new and many features you have CruiseControl are not yet available in Continuum. I chose to try Continuum because of my simple build requirements which will grow hopefully with the Continuum and Maven 2 feature sets. In addition I opted for Continuums tighter integration with Maven 2. If the feature sets were the same I would recommend Continuum because of it tighter integration with Maven 2. Many of the feature you might expect to find in Continuum are really in Maven 2 (where they should be, well.. at least when they are written as a plugin for Maven 2). Be careful of comparing the apples to oranges. Be aware that Maven 2 and Continuum have only been around for a few months and more features are anticipated this year. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Herscu Sent: Tuesday, February 21, 2006 2:59 PM To: continuum-users@maven.apache.org Subject: Why Continuum? Hi all, I am trying to find the answer to this question with no success. Currently, I am using CruiseControl -- why should I (or others like me) switch to Continuum? Adrian. LEGAL NOTICE: Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this e-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately.
Site-deploy or wagon hanging (Maven 2.0.2, Red Hat and SuSe)
Hi all, Is anyone aware that the following command mvn clean install deploy site-deploy will hang when site-deploy executes the following rm command command: cd /home/builder/454/deploy/site/common/.; unzip -o > wagon47499.zip; rm -f wagon47499.zip I'm using Maven 2.0.2, Red Hat 4. Arnaud Bally reported the same using Maven 2.0.2, SuSe 9.2. The threads below are from our discussions in the Continuum group. We determined this is NOT a Continuum problem, rather is appears to be consistently stemming from the site-deploy plugin. -Original Message- From: Michael Böckling [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 07, 2006 5:05 AM To: continuum-users@maven.apache.org Subject: Re: Continuum and site-deploy or wagon hanging Nope, I experienced the exact same problem. Here it happens on a SuSe 9.2 with Maven 2.0.2 (and also in Continuum, of course). I had the impression that this does not affect small sites, but only large ones with many reports and all. It seems the site *does* get deployed correctly, but it hangs at very same line (wagon47499.zip; rm -f wagon47499.zip) when trying to delete the temporary upload file. Can't be a problem with permissions, since it only happens now and then. Defining a timeout is really essential, since it hangs forever once it gets stuck. Regards, Michael > Hmm, all problems were fixed in wagon for maven 2.0.2. > > If you have pb with this version, send a message to maven user list. > > Emmanuel > > Arnaud Bailly a écrit : > >> Hi, >> We are experiencing same problem : wagon hangs on ssh deploy and >> site-deploy in a random way. Sometimes it works, sometimes it doesn't. >> This has nothing to do with continuum as the problem occurs in maven >> direct invocations. Solutions are of course welcomed, I was not able >> to trace the cause of >> this problem (files permissions ok, ssh auth ok). > -- Giniality AG - Michael Böckling; Steinenberg 21, CH-4051 Basel P: +41 61 226 99 63 - F: +41 61 226 99 69 [EMAIL PROTECTED]; http://www.giniality.com/ Good question, thanks. Yes when run from the command line mvn clean install deploy site-deploy it Maven hangs in the sample place. The M2 site-deploy plugin is hanging on the unzip command. I will send my findings to the site-deploy plugin mailing list and let you know when there is a resolution. Although this is unrelated to Continuum, Continuum should handle this gracefully. The only way to work around the problem is to restart the Continuum server (and not use the site-deploy command for the moment). Perhaps adding some sort of daemon that detects a hung condition would strengthen its fault tolerance. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Monday, February 06, 2006 3:52 PM To: continuum-users@maven.apache.org Subject: Re: Continuum and site-deploy or wagon hanging Do you have the same problem when you call site-deploy directly for maven on your continuum machine? When a goal is called, it's an external maven process that run it and not Continuum. Emmanuel Johnson, Jonathan a écrit : > Anyone having problems with Continuum or site-deploy or wagon hanging? > > Using Continuum 1.0.2, Maven 2.0.2. > > I recently added deploy and deploy-site to my Continuum build and have > found Continuum will hang waiting for the build to finish. If I > restart Continuum and force the build again it will sometimes work, > sometimes it hangs again. > > It always hangs at the same place, just after calling unzip on the > site zip file expansion. The site does get expanded so it seems to > hang just after completing the expansion. > > Tail of build report. > > ... > [INFO] ResourceManager : found templates/package-frame.vm with loader > org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader > [INFO] Generate "Maven Surefire Report" report. > [INFO] Generate "Tag List" report. > [INFO] Generate an index file for the English version. > [INFO] [site:deploy] > scp://hober/home/builder/454/deploy/site/common - Session: Opened > Executing command: mkdir -p /home/builder/454/deploy/site/common/. > Executing command: mkdir -p /home/builder/454/deploy/site/common/. > Executing command: scp -t > /home/builder/454/deploy/site/common/./wagon47499.zip > Uploading: ./wagon47499.zip to > scp://hober/home/builder/454/deploy/site/common > > ###[...for email, bunch of pounds omitted...]#! > ###[...omitted...]## > > Transfer finished. 6317094 bytes copied in 3.269 seconds Executing > command: cd /home/builder/454/deploy/site/common/.; unzip -o > wagon47499.zip; rm -f wagon47499.zip Hung here LEGAL NOTICE: Unless expressly stated otherwise, this message is confidential
RE: Continuum and site-deploy or wagon hanging
Good question, thanks. Yes when run from the command line mvn clean install deploy site-deploy it Maven hangs in the sample place. The M2 site-deploy plugin is hanging on the unzip command. I will send my findings to the site-deploy plugin mailing list and let you know when there is a resolution. Although this is unrelated to Continuum, Continuum should handle this gracefully. The only way to work around the problem is to restart the Continuum server (and not use the site-deploy command for the moment). Perhaps adding some sort of daemon that detects a hung condition would strengthen its fault tolerance. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Monday, February 06, 2006 3:52 PM To: continuum-users@maven.apache.org Subject: Re: Continuum and site-deploy or wagon hanging Do you have the same problem when you call site-deploy directly for maven on your continuum machine? When a goal is called, it's an external maven process that run it and not Continuum. Emmanuel Johnson, Jonathan a écrit : > Anyone having problems with Continuum or site-deploy or wagon hanging? > > Using Continuum 1.0.2, Maven 2.0.2. > > I recently added deploy and deploy-site to my Continuum build and have > found Continuum will hang waiting for the build to finish. If I restart > Continuum and force the build again it will sometimes work, sometimes it > hangs again. > > It always hangs at the same place, just after calling unzip on the site > zip file expansion. The site does get expanded so it seems to hang just > after completing the expansion. > > Tail of build report. > > ... > [INFO] ResourceManager : found templates/package-frame.vm with loader > org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader > [INFO] Generate "Maven Surefire Report" report. > [INFO] Generate "Tag List" report. > [INFO] Generate an index file for the English version. > [INFO] [site:deploy] > scp://hober/home/builder/454/deploy/site/common - Session: Opened > Executing command: mkdir -p /home/builder/454/deploy/site/common/. > Executing command: mkdir -p /home/builder/454/deploy/site/common/. > Executing command: scp -t > /home/builder/454/deploy/site/common/./wagon47499.zip > Uploading: ./wagon47499.zip to > scp://hober/home/builder/454/deploy/site/common > > ###[...for email, bunch of pounds omitted...]#! ###[...omitted...]## > > Transfer finished. 6317094 bytes copied in 3.269 seconds Executing > command: cd /home/builder/454/deploy/site/common/.; unzip -o > wagon47499.zip; rm -f wagon47499.zip > Hung here > > LEGAL NOTICE: > Unless expressly stated otherwise, this message is confidential and may be > privileged. It is intended for the addressee(s) only. Access to this e-mail > by anyone else is unauthorized. If you are not an addressee, any disclosure > or copying of the contents or any action taken (or not taken) in reliance on > it is unauthorized and may be unlawful. If you are not an addressee, please > inform the sender immediately. > > > > >
RE: multi-module maven 2 project
Emmanuel, I was hoping that Continuum would preserve the parent-child relationship of a parent and child poms. It would be nice to force a build on either a child or the parent. Forcing a build on the parent pom would build its child modules. As it stands now I can use the parent pom.xml to load all the sub-modules in Continuum, then I can remove the parent project since it is not necessary. This is confusing. As it stands now if you try to run the parent project it just reports a success without doing anything. I would expect an error saying it can't build the sub-modules or it builds the sub-modules. If you are saying that the parent pom.xml is not needed then shouldn't Continuum just add the child modules and not the parent. Also, What if you add three parent pom.xml to Continuum. The flat list of modules looses the project groupings. Perhaps adding a tree or grouping concept for the Continuum Projects list would be a helpful addition. - Jonathan -Original Message- From: Stevenson, Chris [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 01, 2006 6:27 AM To: 'continuum-users@maven.apache.org' Subject: RE: multi-module maven 2 project Thanks for your responses gents. I was under wrong the impression that continuum didn't support multi module builds. Now I know it does I will definitely be using them more. Cheers, Chris -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 31 January 2006 08:46 To: continuum-users@maven.apache.org Subject: Re: multi-module maven 2 project a "command line project" is a Shell project. If you want to build all sub-modules when you build the parent, you have several solution. 1- You want all projects are independant in Continuum, so you add a Maven project. The default goal of a maven parent project isclean install with -N parameter that means that mvn doesn't run recursivly in all modules. You can remove -N parameter in build definition but all your submodules will be built twice (with parent pom and with independant project) 2- You don't need independant projects for submodules in Continuum. Add a Shell project instead of Maven project and set up the command line to run. Emmanuel Johnson, Jonathan a écrit : > I submitted the parent pom to continuum. Its very nicely found all the sub-modules and set those up as well. I did not have to set up a command line project (not sure what that is either). > > One thing that could be enhanced for continuum is a tree structure instead of a flat list. The tree structure would indicate while module is the parent module. Currently there is not indicator which is you parent module. Of course that begs the question of a hierarchical, multi-project tree in maven and continuum. > > The other thing I noticed is forcing a build on the parent module in continuum does not execute the build on the all children. For me it quickly executes with a success yet the sub-module builds are not invoked. > > This is the build report on the parent module named "Java Modules". > > > [INFO] Scanning for projects... > [INFO] > -- > -- > [INFO] Building Java Modules > [INFO]task-segment: [clean, install] > [INFO] > -- > -- > [INFO] [clean:clean] > [INFO] Skipping missing optional mojo: > org.apache.maven.plugins:maven-site-plugin:attach-descriptor > [INFO] [install:install] > [INFO] Installing /home/builder/454/AppJava/modules/66/pom.xml to > /home/builder/.m2/repository/com/fourfivefour/AppJavaModules/1.0/AppJa > vaModules-1.0.pom [INFO] > -- > -- > [INFO] BUILD SUCCESSFUL > [INFO] > -- > -- > [INFO] Total time: 2 seconds > [INFO] Finished at: Mon Jan 30 14:02:38 EST 2006 [INFO] Final Memory: > 2M/5M [INFO] > -- > -- > > -Original Message- > From: Stevenson, Chris [mailto:[EMAIL PROTECTED] > Sent: Monday, January 30, 2006 1:04 PM > To: 'continuum-users@maven.apache.org' > Subject: RE: multi-module maven 2 project > > Gents, > > Can I just check, did you setup your mvn multi module project by > submitting the parent pom and continuum working it out? Or did you > have to create a command line project? > > I remember a while back that continuum couldn't build multi module > projects, except as a command line project. Or am I going nuts.. > > Chris > > -Original Message- > From: Johnson, Jonathan [mailto:[EMAIL PROTECTED] > Sent: 27 January 2006 15:26 &
RE: multi-module maven 2 project
I submitted the parent pom to continuum. Its very nicely found all the sub-modules and set those up as well. I did not have to set up a command line project (not sure what that is either). One thing that could be enhanced for continuum is a tree structure instead of a flat list. The tree structure would indicate while module is the parent module. Currently there is not indicator which is you parent module. Of course that begs the question of a hierarchical, multi-project tree in maven and continuum. The other thing I noticed is forcing a build on the parent module in continuum does not execute the build on the all children. For me it quickly executes with a success yet the sub-module builds are not invoked. This is the build report on the parent module named "Java Modules". [INFO] Scanning for projects... [INFO] [INFO] Building Java Modules [INFO]task-segment: [clean, install] [INFO] [INFO] [clean:clean] [INFO] Skipping missing optional mojo: org.apache.maven.plugins:maven-site-plugin:attach-descriptor [INFO] [install:install] [INFO] Installing /home/builder/454/AppJava/modules/66/pom.xml to /home/builder/.m2/repository/com/fourfivefour/AppJavaModules/1.0/AppJavaModules-1.0.pom [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Mon Jan 30 14:02:38 EST 2006 [INFO] Final Memory: 2M/5M [INFO] -Original Message- From: Stevenson, Chris [mailto:[EMAIL PROTECTED] Sent: Monday, January 30, 2006 1:04 PM To: 'continuum-users@maven.apache.org' Subject: RE: multi-module maven 2 project Gents, Can I just check, did you setup your mvn multi module project by submitting the parent pom and continuum working it out? Or did you have to create a command line project? I remember a while back that continuum couldn't build multi module projects, except as a command line project. Or am I going nuts.. Chris -Original Message- From: Johnson, Jonathan [mailto:[EMAIL PROTECTED] Sent: 27 January 2006 15:26 To: continuum-users@maven.apache.org Subject: RE: multi-module maven 2 project Thanks Emmanuel - comments below. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Friday, January 27, 2006 9:37 AM To: continuum-users@maven.apache.org Subject: Re: multi-module maven 2 project Johnson, Jonathan a écrit : > I'm using maven 2.0.2, Continuum 1.0.2 and java 1.5. My project is a > multi-module that is laid out in the recommended maven 2 manner and is > building my projects (phew). I have a couple questions about my > experiences so far. > > > > 1.When I change some information in my parent pom.xml (such as the > developer list.) do I have to readd the pom again. Is there a > refresh option? >> Normally, the pom will be refresh automatically by continuum, but it >> >> >> doens't to do it. File an issue about it. >> So actually, if your pom isn't updated in continuum, delete your project >> and readd it. I will file the issue. > > 2.If I add my parent pom.xsl it adds all the child modules again > and there are duplicate modules in the continuum projects list. I > then have to remove my old modules and readjust the local continuum > settings such as the schedule and targets. When I apply and updated > pom, I wish it just updated them and kept my local continuum settings. >> File an issue, i'll look at it. >> Your modules was already in continuum before adding the parent, right? Yes. The steps are add a parent pom.xml file. Notice the parent and all submodules appear. Not add a new version of the same parent pom.xml. The sub-modules will appear twice in the list. I will file the issue. > > 3.Removing projects from continuum can take several minutes. >> If your project is big, it can take several minutes because we clean >> all >> infos in database and directories. The more classes in the module, the longer it takes, yet for a module with <1000 classes is takes several minutes. I will file the issue. > > 4.Adding project to continuum takes several minutes. >> Only if you have lot of modules. > > 5.Is performance being addressed or am I doing something wrong? > I'm running red hat linux box with a decent processor. My > multi-module project only has about 1000 classes. Its take me about > 15 minutes to update a pom.xml in continuum. > >> Is it 15 minutes to checkout/u
RE: ContinuumBuildExecutorException: Could not find Maven project descriptor
Emmanuel, Your advice was superb. That fixed the problem. Once I added the working directory and path to the module in the scm url it all worked. The reasons for my problems were this: 1. I did not understand what a working directory was and therefore skipped the configuration setting for this. It would be helpful if the web page for configuration has simple help text explaining what these setting are. The unfortunate term of 'working directory' is subjective and a more descriptive term should have been used. Something like 'project root directory'. Tooltip text should be added with further descriptions. Build output directory term should also be changed. Its really should be "Build Log Directory'. A new user might be misled thinking that all the build artifacts (class, jar, Javadoc, etc) are being placed here. 2. Did not understand that I had to add a scm element to every pom.xml even when I have multi-module structure with a parent pom. For continuum the scm in the parent pom.xml should be sufficient for all the child poms in the module subdirectories. Defining the scm in the sub poms is redundant. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Thursday, January 26, 2006 9:58 AM To: continuum-users@maven.apache.org Subject: Re: ContinuumBuildExecutorException: Could not find Maven project descriptor The 'working directory' is the directory where your files will be checkout ($CONTINUUM_HOME/apps/continuum/working_directory/). The pom.xml of your project must be there. If it isn't that, your scm url is wrong. Your scm url is 'scm:cvs:pserver:[EMAIL PROTECTED]:/home/Repository:project' so you must have your pom.xml in /home/Repository/project in cvs. For your project, scm url must something like this : scm:cvs:pserver:[EMAIL PROTECTED]:/home/Repository:project//modules/myproject Emmanuel Johnson, Jonathan a écrit : >>>You don't have a pom.xml in your working directory. > > > What does 'working directory' mean. How would one define it? Is this a new > pom.xml just for continuum? What has to be in it? I do have a parent > pom.xml one directory above my myproject directory. For the maven 2 parent > element the default location for a parent pom.xml is ../poml.xml. My Maven 2 > build works correctly. I have a pom.xml in the parent directory and in every > module directory as recommended by the maven multi-project directory layout. > Below is a tree of my project. > > >>>Check your scm url for your project. > > Also this error occurs without the tag that was included below, so I > think its unrelated to the exception. > > ├───modules <-- parent pom.xml here. > │ ├───Common<-- pom.xml fo common here. > │ │ └───src > │ │ ├───main > │ │ │ └───java > │ │ │ └───com > │ │ │ └───... > │ │ └───test > │ │ └───java > │ │ └───com > │ │ └───... > │ ├───myproject <-- pom.xml fr myproject here. > │ │ └───src > │ │ └───main > │ │ ├───config > │ │ ├───java > │ │ │ └───com > │ │ │ └───... > │ │ └───resources > > -Original Message- > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 26, 2006 4:08 AM > To: continuum-users@maven.apache.org > Subject: Re: ContinuumBuildExecutorException: Could not find Maven project > descriptor > > You don't have a pom.xml in your working directory. Check your scm url for > your project. > > Emmanuel > > Johnson, Jonathan a écrit : > >>I'm getting an exception and not sure why it means. >> >> >> >>Being new to Continuum I have yet to get it to build any of my modules. >> >> >> >>Here is my platform >> >> >> >>Red Hat >> >>Maven 2.0.2 >> >>Continuum 1.0.2 >> >>Java 1.5.0_06 >> >> >> >>I'm getting this exception when running a build on a single, simple >>module within my multi-module structure. >> >> >> >>org.apache.maven.continuum.execution.ContinuumBuildExecutorException: >>Could not find Maven project descriptor. >> >> at >>org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda >>teProjectFromCheckOut(MavenTwoBuildExecutor.java:111) >> >> at >>org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectory >>ContinuumAction.execute(UpdateProject
RE: ContinuumBuildExecutorException: Could not find Maven project descriptor
>> You don't have a pom.xml in your working directory. What does 'working directory' mean. How would one define it? Is this a new pom.xml just for continuum? What has to be in it? I do have a parent pom.xml one directory above my myproject directory. For the maven 2 parent element the default location for a parent pom.xml is ../poml.xml. My Maven 2 build works correctly. I have a pom.xml in the parent directory and in every module directory as recommended by the maven multi-project directory layout. Below is a tree of my project. >> Check your scm url for your project. Also this error occurs without the tag that was included below, so I think its unrelated to the exception. ├───modules <-- parent pom.xml here. │ ├───Common <-- pom.xml fo common here. │ │ └───src │ │ ├───main │ │ │ └───java │ │ │ └───com │ │ │ └───... │ │ └───test │ │ └───java │ │ └───com │ │ └───... │ ├───myproject <-- pom.xml fr myproject here. │ │ └───src │ │ └───main │ │ ├───config │ │ ├───java │ │ │ └───com │ │ │ └───... │ │ └───resources -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Thursday, January 26, 2006 4:08 AM To: continuum-users@maven.apache.org Subject: Re: ContinuumBuildExecutorException: Could not find Maven project descriptor You don't have a pom.xml in your working directory. Check your scm url for your project. Emmanuel Johnson, Jonathan a écrit : > I'm getting an exception and not sure why it means. > > > > Being new to Continuum I have yet to get it to build any of my modules. > > > > Here is my platform > > > > Red Hat > > Maven 2.0.2 > > Continuum 1.0.2 > > Java 1.5.0_06 > > > > I'm getting this exception when running a build on a single, simple > module within my multi-module structure. > > > > org.apache.maven.continuum.execution.ContinuumBuildExecutorException: > Could not find Maven project descriptor. > > at > org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda > teProjectFromCheckOut(MavenTwoBuildExecutor.java:111) > > at > org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectory > ContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction > .java:62) > > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( > DefaultBuildController.java:169) > > at > org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec > uteTask(BuildProjectTaskExecutor.java:53) > > at > org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut > orRunnable.run(ThreadedTaskQueueExecutor.java:103) > > at java.lang.Thread.run(Thread.java:595) > > > > Most of the settings are supposed to come from the parent pom. My Maven > compile and package of the modules works correctly. The pom.xml of the > sub-module I am trying to execute is this. > > > > 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";> > > 4.0.0 > > com.fourfivefour.myproject > > myproject > > jar > > 0.9 > > myproject > > todo > > > > > > com.fourfivefour > > AppJavaModules > > 1.0 > > > > > > > > > > > > > > > > > scm:cvs:pserver:[EMAIL PROTECTED]:/home/Repository:project > > > > > > > > > > > > > > > > > > > > > LEGAL NOTICE: > Unless expressly stated otherwise, this message is confidential and may be > privileged. It is intended for the addressee(s) only. Access to this e-mail > by anyone else is unauthorized. If you are not an addressee, any disclosure > or copying of the contents or any action taken (or not taken) in reliance on > it is unauthorized and may be unlawful. If you are not an addressee, please > inform the sender immediately. > > >
ContinuumBuildExecutorException: Could not find Maven project descriptor
I'm getting an exception and not sure why it means. Being new to Continuum I have yet to get it to build any of my modules. Here is my platform Red Hat Maven 2.0.2 Continuum 1.0.2 Java 1.5.0_06 I'm getting this exception when running a build on a single, simple module within my multi-module structure. org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Could not find Maven project descriptor. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:111) at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectory ContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction .java:62) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:169) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec uteTask(BuildProjectTaskExecutor.java:53) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:595) Most of the settings are supposed to come from the parent pom. My Maven compile and package of the modules works correctly. The pom.xml of the sub-module I am trying to execute is this. 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";> 4.0.0 com.fourfivefour.myproject myproject jar 0.9 myproject todo com.fourfivefour AppJavaModules 1.0 scm:cvs:pserver:[EMAIL PROTECTED]:/home/Repository:AppJava LEGAL NOTICE: Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this e-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately.
