Re: Confused by Continuum and Maven2 multimodule integration
yes, please. Emmanuel Julien Stern a écrit : Emmanuel, thanks for your reply. I have been going back and forth between the two structures, and actually even tried a mix of both, with two poms, one for inheritance (flat) and the other for aggregation (hierachical). It works, but it is kind of a mess :) The addition of this check in a way or an other would be a real saver for us: we cannot afford 4 hours of builds each type someone fixes a typo in a Javadoc ... Should I file a JIRA issue regarding this ? -- Julien On Mon, Dec 17, 2007 at 10:23:01PM +0100, Emmanuel Venisse wrote: The standard maven directory structure is recommended, but you're right, it rebuild all. We must add a check in next version to know if the build generated a real artifact that require a children build Emmanuel Julien Stern a écrit : Hi list, when using Maven2, it appear to be recommended to have the following directory structure for a multi-module build: - pom.xml (parent pom of all modules) --- module1 +-- pom.xml --- module2 +-- pom.xml etc When using such a structure with continuum, if I commit a change in module28, then EVERY module will be rebuilt: indeed the parent pom will be rebuilt because the change is "under" its scm tree, and all the other modules will therefore we rebuilt because of a "dependencies change" on the parent pom. When trying to avoid this, I attempted to use the following structure: --- parent +-- pom.xml --- module1 +-- pom.xml --- module2 +-- pom.xml However, this prevents a number of M2 functionnalities, such as, for instance, the usage of the release plugin for the whole project (as far as I understood). What are the best practices when using Continuum and M2 with multimodule builds together ? How does the Maven team avoids this issue when building Maven2 and Continuum themselves with Continuum ? Thanks in advance. -- Julien
Re: Confused by Continuum and Maven2 multimodule integration
Emmanuel, thanks for your reply. I have been going back and forth between the two structures, and actually even tried a mix of both, with two poms, one for inheritance (flat) and the other for aggregation (hierachical). It works, but it is kind of a mess :) The addition of this check in a way or an other would be a real saver for us: we cannot afford 4 hours of builds each type someone fixes a typo in a Javadoc ... Should I file a JIRA issue regarding this ? -- Julien On Mon, Dec 17, 2007 at 10:23:01PM +0100, Emmanuel Venisse wrote: > The standard maven directory structure is recommended, but you're right, it > rebuild all. We must add a check in next version to know if the build > generated a real artifact that require a children build > > Emmanuel > > Julien Stern a écrit : > >Hi list, > > > >when using Maven2, it appear to be recommended to have the following > >directory structure for a multi-module build: > > > >- pom.xml (parent pom of all modules) > >--- module1 > > +-- pom.xml > >--- module2 > > +-- pom.xml > >etc > > > >When using such a structure with continuum, if I commit a change > >in module28, then EVERY module will be rebuilt: > >indeed the parent pom will be rebuilt because the change is "under" > >its scm tree, and all the other modules will therefore we rebuilt > >because of a "dependencies change" on the parent pom. > > > >When trying to avoid this, I attempted to use the following structure: > > > >--- parent > > +-- pom.xml > >--- module1 > > +-- pom.xml > >--- module2 > > +-- pom.xml > > > >However, this prevents a number of M2 functionnalities, such as, for > >instance, the usage of the release plugin for the whole project (as > >far as I understood). > > > >What are the best practices when using Continuum and M2 with multimodule > >builds together ? > > > >How does the Maven team avoids this issue when building Maven2 and > >Continuum themselves with Continuum ? > > > >Thanks in advance. > > > >-- > >Julien > > > > >
Re: AW: AW: AW: Wrong build status in Project Group Summary
open your db with a SQL client like SQuirrelSQL and run some sql request to change the column length Emmanuel [EMAIL PROTECTED] a écrit : Hi Emmanuel, If you don't want to see it an other time, you can increase the length of the COMMAND_OUTPUT field in your db. in my case this problem completely breaks the usefullness of continuum, so I nedd to fix it in my installation. I would appreciate if you can you give me a hint how to do this. Thanks in advance Manuel -Ursprüngliche Nachricht- Von: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 13. Dezember 2007 21:09 An: continuum-users@maven.apache.org Betreff: Re: AW: AW: Wrong build status in Project Group Summary It seems the cvs output was big. Continuum allow only 1024 caracters. If you don't want to see it an other time, you can increase the length of the COMMAND_OUTPUT field in your db. Emmanuel [EMAIL PROTECTED] a écrit : I searched in JIRA but I could not find a entry that describes the problem. Here you can see a snippet from the logs: 276440818 [pool-1-thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm:default - Provider message: The cvs command failed. 276440850 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Merging SCM results 276440896 [Thread-6] ERROR org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:build-projec t - Error executing task edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: javax.jdo.JDOFatalUserException: Attempt to store value "cvs server: src/...CheckBox.java is no longer in the repository cvs server: src/...ResearchConstants.java is no longer in the repository cvs update: move away src/...Model.java; it is in the way . . [snip] . cvs server: src...Researcj.java is no longer in the repository cvs server: src/...Something.java is no longer in the repository " in column "COMMAND_OUTPUT" that has maximum length of 1024. Please correct your data! at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:118) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.waitForTask(ThreadedTaskQueueExecutor.java:159) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Exec utorRunnable.run(ThreadedTaskQueueExecutor.java:127) Caused by: javax.jdo.JDOFatalUserException: Attempt to store value "cvs server: src/...Box.java is no longer in the repository cvs server: src...Constants.java is no longer in the repository . . [snip] . cvs update: move away src/...Panel.java; it is in the way " in column "COMMAND_OUTPUT" that has maximum length of 1024. Please correct your data! at org.jpox.store.rdbms.mapping.CharRDBMSMapping.setString(CharRDBMSMapping.java:214) at org.jpox.store.mapping.SingleFieldMapping.setString(SingleFieldMapping.java:203) at org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeStringField(ParameterSetter.java:122) at org.jpox.state.StateManagerImpl.providedStringField(StateManagerImpl.java:2757) at org.apache.maven.continuum.model.scm.ScmResult.jdoProvideField(ScmResult.java) at org.apache.maven.continuum.model.scm.ScmResult.jdoProvideFields(ScmResult.java) at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115) at org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:252) at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519) at org.jpox.store.StoreManager.insert(StoreManager.java:920) at org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3667) at org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3646) at org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1198) at org.jpox.AbstractPersistenceManager.makePersistentInternal(AbstractPersistenceManager.java:1243) at org.jpox.store.mapping.PersistenceCapableMapping.setObject(PersistenceCapableMapping.java:450) at org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeObjectField(ParameterSetter.java:144) at org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.java:2771) at org.apache.maven.continuum.model.project.BuildResult.jdoProvideField(BuildResult.java) at org.apache.maven.continuum.model.project.BuildResult.jdoProvideFields(BuildResult.java) at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115) at org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:252) at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519) at org.jpox.store.StoreManager.insert(StoreManager.java:920) at org.jpox.state.StateManagerImpl.internalMakePersistent(State
Code checkout not happening
I have set up a pretty typical Maven2 Java project and trying to execute it using Continuum 1.1. I've set "Build Fresh" to true. It doesn't seem like continuum is actually doing a checkout of the project from the source code repository. As a result, the maven compiler complains that there are "No sources to compile". When I go look into the working directory, there is no code at all. When I previously used Continuum 1.0.3, it seemed that Continuum would, by default, checkout the code. Is this still the case? Or is there a setting I'm missing somewhere? Thanks in advance. - Doug -- View this message in context: http://www.nabble.com/Code-checkout-not-happening-tp14373893p14373893.html Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Problem with surefire-reports in Continuum 1.1 final
Hi Olivier, I unzip apache-continuum-1.1.zip file in directory C:\continuum-1.1. Then I executed the C:\continuum-1.1\bin\windows-x86-32\InstallService.bat. In Windows´s services, at Apache Continuum I change Log On of the service to my network user (following documentation). Then I start the service and set admin user of continuum. I added the M2 Project from web interface of continuum. I don´t checkout the project manually. To add M2 project in continuum, I used URL POM, set http://*, user and password. Can you test this in Windows? Without to change user of Windows´s service (keep local system) work out. - Original Message - From: "olivier lamy" <[EMAIL PROTECTED]> To: Sent: Monday, December 17, 2007 11:19 AM Subject: Re: Problem with surefire-reports in Continuum 1.1 final As I understand here it's a permission issue. If your first continuum start was with a user a : all projects have been checkout and working directories created with this user. Now you shutdown continuum and restart it with a user b, this user b don't have the permissions on the files/directories created by the user a. Two solutions : - re use the same user - change the permission rights (chown/chmod on unix sorry don't know on windows) -- Olivier 2007/12/17, Claudio Ranieri <[EMAIL PROTECTED]>: Hi Olivier, When I launch mvn clean install into C:\continuum\work\6, the maven work out. After various tests, I isolated the problem. The problem occurs when I install continuum as a Windows Service and change service´s Log on to a net´s user (following documentation). When I use the local system to log on, the problem doesn´t occur. Can you do a test changing the user of service´s log on to a net´s user? Thanks. - Original Message - From: "olivier lamy" <[EMAIL PROTECTED]> To: Sent: Thursday, December 13, 2007 7:10 PM Subject: Re: Problem with surefire-reports in Continuum 1.1 final If you cd to C:\continuum\work\6 and launch mvn clean install. What's happened ? Because as I see in the stack Trace it looks to be more an issue with surefire. Thanks, -- Olivier 2007/12/13, Diego <[EMAIL PROTECTED]>: > > Hi Oliver ... > > It means :"The system could not found the specified path" > > tks > > olivier lamy escreveu: > > Hi, > > What does it mean in english : > > Caused by: java.io.IOException: O sistema não pode encontrar o > > caminho especificado > > > > ? > > :-) > > Thanks, > > -- > > Olivier > > > > 2007/12/13, Diego <[EMAIL PROTECTED]>: > > > >> Hi, > >> > >> I am using Continuum 1.1 final, Maven 2.0.7, Java 1.5.0_06 and > WindowsXP > >> > >> I added a M2 project in Continuum, but in result of build I got: > >> > >> + Error stacktraces are turned on. > >> [INFO] Scanning for projects... > >> [INFO] > >> > >> > > >> [INFO] Building Sincronismo > >> [INFO]task-segment: [clean, install] > >> [INFO] > >> > >> > > >> [INFO] [clean:clean] > >> [INFO] Deleting directory C:\continuum\work\6\target > >> [INFO] [resources:resources] > >> [INFO] Using default encoding to copy filtered resources. > >> [INFO] [compiler:compile] > >> [INFO] Compiling 8 source files to C:\continuum\work\6\target\classes > >> [INFO] [resources:testResources] > >> [INFO] Using default encoding to copy filtered resources. > >> [INFO] [compiler:testCompile] > >> [INFO] Compiling 1 source file to > C:\continuum\work\6\target\test-classes > >> [INFO] [surefire:test] > >> [INFO] Surefire report directory: > >> C:\continuum\work\6\target\surefire-reports > >> [INFO] > >> > > >> [ERROR] BUILD ERROR > >> [INFO] > >> > > >> [INFO] Error creating properties files for forking; nested exception > >> is > >> java.io.IOException: O sistema não pode encontrar o caminho > >> especificado > >> > >> [INFO] > >> > > >> [INFO] Trace > >> org.apache.maven.lifecycle.LifecycleExecutionException: Error > >> creating > >> properties files for forking; nested exception is > >> java.io.IOException: > O > >> sistema não pode encontrar o caminho especificado > >> at > >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( > >> DefaultLifecycleExecutor.java:564) > >> at > >> > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle > >> (DefaultLifecycleExecutor.java:480) > >> at > >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( > >> DefaultLifecycleExecutor.java:459) > >> at > >> > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures > >> (DefaultLifecycleExecutor.java:311) > >> at > >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments > ( > >> DefaultLifecycleExecutor
AW: AW: AW: Wrong build status in Project Group Summary
Hi Emmanuel, > If you don't want to see it an other time, you can increase the length of the > COMMAND_OUTPUT field in your db. in my case this problem completely breaks the usefullness of continuum, so I nedd to fix it in my installation. I would appreciate if you can you give me a hint how to do this. Thanks in advance Manuel -Ursprüngliche Nachricht- Von: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 13. Dezember 2007 21:09 An: continuum-users@maven.apache.org Betreff: Re: AW: AW: Wrong build status in Project Group Summary It seems the cvs output was big. Continuum allow only 1024 caracters. If you don't want to see it an other time, you can increase the length of the COMMAND_OUTPUT field in your db. Emmanuel [EMAIL PROTECTED] a écrit : > > I searched in JIRA but I could not find a entry that describes the problem. > > Here you can see a snippet from the logs: > > 276440818 [pool-1-thread-1] WARN > org.apache.maven.continuum.scm.ContinuumScm:default - Provider message: The > cvs command failed. > 276440850 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - > Merging SCM results > 276440896 [Thread-6] ERROR > org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:build-projec > t - Error executing task > edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: > javax.jdo.JDOFatalUserException: Attempt to store value "cvs server: > src/...CheckBox.java is no longer in the repository cvs server: > src/...ResearchConstants.java is no longer in the repository cvs update: move > away src/...Model.java; it is in the way . > . [snip] > . > cvs server: src...Researcj.java is no longer in the repository cvs > server: src/...Something.java is no longer in the repository " in > column "COMMAND_OUTPUT" that has maximum length of 1024. Please correct your > data! > at > edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299) > at > edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:118) > at > org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.waitForTask(ThreadedTaskQueueExecutor.java:159) > at > org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Exec > utorRunnable.run(ThreadedTaskQueueExecutor.java:127) > Caused by: javax.jdo.JDOFatalUserException: Attempt to store value > "cvs server: src/...Box.java is no longer in the repository cvs > server: src...Constants.java is no longer in the repository . > . [snip] > . > cvs update: move away src/...Panel.java; it is in the way " in column > "COMMAND_OUTPUT" that has maximum length of 1024. Please correct your data! > at > org.jpox.store.rdbms.mapping.CharRDBMSMapping.setString(CharRDBMSMapping.java:214) > at > org.jpox.store.mapping.SingleFieldMapping.setString(SingleFieldMapping.java:203) > at > org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeStringField(ParameterSetter.java:122) > at > org.jpox.state.StateManagerImpl.providedStringField(StateManagerImpl.java:2757) > at > org.apache.maven.continuum.model.scm.ScmResult.jdoProvideField(ScmResult.java) > at > org.apache.maven.continuum.model.scm.ScmResult.jdoProvideFields(ScmResult.java) > at > org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115) > at > org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:252) > at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519) > at org.jpox.store.StoreManager.insert(StoreManager.java:920) > at > org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3667) > at > org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3646) > at > org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1198) > at > org.jpox.AbstractPersistenceManager.makePersistentInternal(AbstractPersistenceManager.java:1243) > at > org.jpox.store.mapping.PersistenceCapableMapping.setObject(PersistenceCapableMapping.java:450) > at > org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeObjectField(ParameterSetter.java:144) > at > org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.java:2771) > at > org.apache.maven.continuum.model.project.BuildResult.jdoProvideField(BuildResult.java) > at > org.apache.maven.continuum.model.project.BuildResult.jdoProvideFields(BuildResult.java) > at > org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115) > at > org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:252) > at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519) > at org.jpox.store.StoreManager.insert(StoreManager.java:920) > at > org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3667) >
Re: Problem with surefire-reports in Continuum 1.1 final
As I understand here it's a permission issue. If your first continuum start was with a user a : all projects have been checkout and working directories created with this user. Now you shutdown continuum and restart it with a user b, this user b don't have the permissions on the files/directories created by the user a. Two solutions : - re use the same user - change the permission rights (chown/chmod on unix sorry don't know on windows) -- Olivier 2007/12/17, Claudio Ranieri <[EMAIL PROTECTED]>: > Hi Olivier, > > When I launch mvn clean install into C:\continuum\work\6, the maven work > out. > After various tests, I isolated the problem. > The problem occurs when I install continuum as a Windows Service and change > service´s Log on to a net´s user (following documentation). > When I use the local system to log on, the problem doesn´t occur. > Can you do a test changing the user of service´s log on to a net´s user? > Thanks. > > - Original Message - > From: "olivier lamy" <[EMAIL PROTECTED]> > To: > Sent: Thursday, December 13, 2007 7:10 PM > Subject: Re: Problem with surefire-reports in Continuum 1.1 final > > > If you cd to C:\continuum\work\6 and launch mvn clean install. > What's happened ? > Because as I see in the stack Trace it looks to be more an issue with > surefire. > Thanks, > -- > Olivier > > 2007/12/13, Diego <[EMAIL PROTECTED]>: > > > > Hi Oliver ... > > > > It means :"The system could not found the specified path" > > > > tks > > > > olivier lamy escreveu: > > > Hi, > > > What does it mean in english : > > > Caused by: java.io.IOException: O sistema não pode encontrar o > > > caminho especificado > > > > > > ? > > > :-) > > > Thanks, > > > -- > > > Olivier > > > > > > 2007/12/13, Diego <[EMAIL PROTECTED]>: > > > > > >> Hi, > > >> > > >> I am using Continuum 1.1 final, Maven 2.0.7, Java 1.5.0_06 and > > WindowsXP > > >> > > >> I added a M2 project in Continuum, but in result of build I got: > > >> > > >> + Error stacktraces are turned on. > > >> [INFO] Scanning for projects... > > >> [INFO] > > >> > > >> > > > > >> [INFO] Building Sincronismo > > >> [INFO]task-segment: [clean, install] > > >> [INFO] > > >> > > >> > > > > >> [INFO] [clean:clean] > > >> [INFO] Deleting directory C:\continuum\work\6\target > > >> [INFO] [resources:resources] > > >> [INFO] Using default encoding to copy filtered resources. > > >> [INFO] [compiler:compile] > > >> [INFO] Compiling 8 source files to C:\continuum\work\6\target\classes > > >> [INFO] [resources:testResources] > > >> [INFO] Using default encoding to copy filtered resources. > > >> [INFO] [compiler:testCompile] > > >> [INFO] Compiling 1 source file to > > C:\continuum\work\6\target\test-classes > > >> [INFO] [surefire:test] > > >> [INFO] Surefire report directory: > > >> C:\continuum\work\6\target\surefire-reports > > >> [INFO] > > >> > > > > >> [ERROR] BUILD ERROR > > >> [INFO] > > >> > > > > >> [INFO] Error creating properties files for forking; nested exception is > > >> java.io.IOException: O sistema não pode encontrar o caminho > > >> especificado > > >> > > >> [INFO] > > >> > > > > >> [INFO] Trace > > >> org.apache.maven.lifecycle.LifecycleExecutionException: Error creating > > >> properties files for forking; nested exception is java.io.IOException: > > O > > >> sistema não pode encontrar o caminho especificado > > >> at > > >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( > > >> DefaultLifecycleExecutor.java:564) > > >> at > > >> > > >> > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle > > >> (DefaultLifecycleExecutor.java:480) > > >> at > > >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( > > >> DefaultLifecycleExecutor.java:459) > > >> at > > >> > > >> > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures > > >> (DefaultLifecycleExecutor.java:311) > > >> at > > >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments > > ( > > >> DefaultLifecycleExecutor.java:278) > > >> at > > >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( > > >> DefaultLifecycleExecutor.java:143) > > >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > > >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > > >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) > > >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > >> at > > >> sun.reflect.NativeMethodAccessorImpl.invoke( > > NativeMethodAccessorImpl.java > > >> :39) > > >> at > > >> sun.reflect.DelegatingMethodAccessorImpl.invoke( > > >> DelegatingMet
Re: Problem with surefire-reports in Continuum 1.1 final
Hi Olivier, When I launch mvn clean install into C:\continuum\work\6, the maven work out. After various tests, I isolated the problem. The problem occurs when I install continuum as a Windows Service and change service´s Log on to a net´s user (following documentation). When I use the local system to log on, the problem doesn´t occur. Can you do a test changing the user of service´s log on to a net´s user? Thanks. - Original Message - From: "olivier lamy" <[EMAIL PROTECTED]> To: Sent: Thursday, December 13, 2007 7:10 PM Subject: Re: Problem with surefire-reports in Continuum 1.1 final If you cd to C:\continuum\work\6 and launch mvn clean install. What's happened ? Because as I see in the stack Trace it looks to be more an issue with surefire. Thanks, -- Olivier 2007/12/13, Diego <[EMAIL PROTECTED]>: Hi Oliver ... It means :"The system could not found the specified path" tks olivier lamy escreveu: > Hi, > What does it mean in english : > Caused by: java.io.IOException: O sistema não pode encontrar o > caminho especificado > > ? > :-) > Thanks, > -- > Olivier > > 2007/12/13, Diego <[EMAIL PROTECTED]>: > >> Hi, >> >> I am using Continuum 1.1 final, Maven 2.0.7, Java 1.5.0_06 and WindowsXP >> >> I added a M2 project in Continuum, but in result of build I got: >> >> + Error stacktraces are turned on. >> [INFO] Scanning for projects... >> [INFO] >> >> >> [INFO] Building Sincronismo >> [INFO]task-segment: [clean, install] >> [INFO] >> >> >> [INFO] [clean:clean] >> [INFO] Deleting directory C:\continuum\work\6\target >> [INFO] [resources:resources] >> [INFO] Using default encoding to copy filtered resources. >> [INFO] [compiler:compile] >> [INFO] Compiling 8 source files to C:\continuum\work\6\target\classes >> [INFO] [resources:testResources] >> [INFO] Using default encoding to copy filtered resources. >> [INFO] [compiler:testCompile] >> [INFO] Compiling 1 source file to C:\continuum\work\6\target\test-classes >> [INFO] [surefire:test] >> [INFO] Surefire report directory: >> C:\continuum\work\6\target\surefire-reports >> [INFO] >> >> [ERROR] BUILD ERROR >> [INFO] >> >> [INFO] Error creating properties files for forking; nested exception is >> java.io.IOException: O sistema não pode encontrar o caminho >> especificado >> >> [INFO] >> >> [INFO] Trace >> org.apache.maven.lifecycle.LifecycleExecutionException: Error creating >> properties files for forking; nested exception is java.io.IOException: O >> sistema não pode encontrar o caminho especificado >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( >> DefaultLifecycleExecutor.java:564) >> at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle >> (DefaultLifecycleExecutor.java:480) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( >> DefaultLifecycleExecutor.java:459) >> at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures >> (DefaultLifecycleExecutor.java:311) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments ( >> DefaultLifecycleExecutor.java:278) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( >> DefaultLifecycleExecutor.java:143) >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java >> :39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke( >> DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:585) >> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java :430) >> at org.codehaus.classworlds.Launcher.main(Launcher.java:375) >> Caused by: org.apache.maven.plugin.MojoExecutionException: Error >> creating properties files for forking; nested exception is >> java.io.IOException: O sistema não pode encontrar o caminho >> especificado >> at >> org.apache.maven.plugin.surefire.SurefirePlugin.execute( >> SurefirePlugin.java:402) >> at >> org.apache.maven.plugin.DefaultPluginManager.executeMojo( >> DefaultPluginManager.java:443) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( >> DefaultLifecycleExecutor.java:539) >> ... 16 more >> Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException
Re: Problem with surefire-reports in Continuum 1.1 final
Hi Olivier, When I launch mvn clean install into C:\continuum\work\6, the maven work out. After various tests, I isolated the problem. The problem occurs when I install continuum as a Windows Service and change service´s Log on to a net´s user (following documentation). When I use the local system to log on, the problem doesn´t occur. Can you do a test changing the user of service´s log on to a net´s user? Thanks. - Original Message - From: "olivier lamy" <[EMAIL PROTECTED]> To: Sent: Thursday, December 13, 2007 7:10 PM Subject: Re: Problem with surefire-reports in Continuum 1.1 final If you cd to C:\continuum\work\6 and launch mvn clean install. What's happened ? Because as I see in the stack Trace it looks to be more an issue with surefire. Thanks, -- Olivier 2007/12/13, Diego <[EMAIL PROTECTED]>: Hi Oliver ... It means :"The system could not found the specified path" tks olivier lamy escreveu: > Hi, > What does it mean in english : > Caused by: java.io.IOException: O sistema não pode encontrar o > caminho especificado > > ? > :-) > Thanks, > -- > Olivier > > 2007/12/13, Diego <[EMAIL PROTECTED]>: > >> Hi, >> >> I am using Continuum 1.1 final, Maven 2.0.7, Java 1.5.0_06 and WindowsXP >> >> I added a M2 project in Continuum, but in result of build I got: >> >> + Error stacktraces are turned on. >> [INFO] Scanning for projects... >> [INFO] >> >> >> [INFO] Building Sincronismo >> [INFO]task-segment: [clean, install] >> [INFO] >> >> >> [INFO] [clean:clean] >> [INFO] Deleting directory C:\continuum\work\6\target >> [INFO] [resources:resources] >> [INFO] Using default encoding to copy filtered resources. >> [INFO] [compiler:compile] >> [INFO] Compiling 8 source files to C:\continuum\work\6\target\classes >> [INFO] [resources:testResources] >> [INFO] Using default encoding to copy filtered resources. >> [INFO] [compiler:testCompile] >> [INFO] Compiling 1 source file to C:\continuum\work\6\target\test-classes >> [INFO] [surefire:test] >> [INFO] Surefire report directory: >> C:\continuum\work\6\target\surefire-reports >> [INFO] >> >> [ERROR] BUILD ERROR >> [INFO] >> >> [INFO] Error creating properties files for forking; nested exception is >> java.io.IOException: O sistema não pode encontrar o caminho >> especificado >> >> [INFO] >> >> [INFO] Trace >> org.apache.maven.lifecycle.LifecycleExecutionException: Error creating >> properties files for forking; nested exception is java.io.IOException: O >> sistema não pode encontrar o caminho especificado >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( >> DefaultLifecycleExecutor.java:564) >> at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle >> (DefaultLifecycleExecutor.java:480) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( >> DefaultLifecycleExecutor.java:459) >> at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures >> (DefaultLifecycleExecutor.java:311) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments ( >> DefaultLifecycleExecutor.java:278) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( >> DefaultLifecycleExecutor.java:143) >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java >> :39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke( >> DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:585) >> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java :430) >> at org.codehaus.classworlds.Launcher.main(Launcher.java:375) >> Caused by: org.apache.maven.plugin.MojoExecutionException: Error >> creating properties files for forking; nested exception is >> java.io.IOException: O sistema não pode encontrar o caminho >> especificado >> at >> org.apache.maven.plugin.surefire.SurefirePlugin.execute( >> SurefirePlugin.java:402) >> at >> org.apache.maven.plugin.DefaultPluginManager.executeMojo( >> DefaultPluginManager.java:443) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( >> DefaultLifecycleExecutor.java:539) >> ... 16 more >> Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException
Re: mail-notifier
[EMAIL PROTECTED] wrote: Take a look at your configuration: mail.smtp.socketFactory.class javax.net.ssl.SSLSocketFactory Maybe if you try it with SocketFactory instead of SSLSocketFactory? Hth, Hi! I just commented this ! And it works! SSL is disable. Nick Stolwijk -Original Message- From: ivan [mailto:[EMAIL PROTECTED] Sent: Mon 12/17/2007 11:04 AM To: continuum-users@maven.apache.org Subject: mail-notifier Hi! I installed continuum as single application and have problem with notifier. I configured plexus.xml like in example (http://maven.apache.org/continuum/documentation/1_1/installation/standalone.html#Mail_server_configuration) but continuum could send mail. 853279 [pool-1-thread-1] ERROR org.apache.maven.continuum.notification.ContinuumNotificationDispatcher:default - Error while trying to use the mail notifier. org.codehaus.plexus.notification.NotificationException: Exception while sending message. at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendMessage(MailContinuumNotifier.java:566) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:387) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendNotification(MailContinuumNotifier.java:254) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:199) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:151) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.buildComplete(DefaultContinuumNotificationDispatcher.java:103) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.endBuild(DefaultBuildController.java:221) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:175) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:50) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:619) Caused by: org.codehaus.plexus.mailsender.MailSenderException: Error while sending the message. at org.codehaus.plexus.mailsender.javamail.AbstractJavamailMailSender.send(AbstractJavamailMailSender.java:226) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendMessage(MailContinuumNotifier.java:562) ... 14 more Caused by: javax.mail.MessagingException: Exception reading response; nested exception is: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? at com.sun.mail.smtp.SMTPTransport.readServerResponse(SMTPTransport.java:1462) at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1260) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:370) at javax.mail.Service.connect(Service.java:275) at org.codehaus.plexus.mailsender.javamail.AbstractJavamailMailSender.send(AbstractJavamailMailSender.java:212) ... 15 more Caused by: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? at com.sun.net.ssl.internal.ssl.InputRecord.handleUnknownRecord(InputRecord.java:521) at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:355) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1096) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:744) at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75) at com.sun.mail.util.TraceInputStream.read(TraceInputStream.java:97) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at com.sun.mail.util.LineInputStream.readLine(LineInputStream.java:75) at com.sun.mail.smtp.SMTPTransport.readServerResponse(SMTPTransport.java:1440) ... 19 more May be I forgot to set some other parameters? Thanks.
RE: mail-notifier
Take a look at your configuration: mail.smtp.socketFactory.class javax.net.ssl.SSLSocketFactory Maybe if you try it with SocketFactory instead of SSLSocketFactory? Hth, Nick Stolwijk -Original Message- From: ivan [mailto:[EMAIL PROTECTED] Sent: Mon 12/17/2007 11:04 AM To: continuum-users@maven.apache.org Subject: mail-notifier Hi! I installed continuum as single application and have problem with notifier. I configured plexus.xml like in example (http://maven.apache.org/continuum/documentation/1_1/installation/standalone.html#Mail_server_configuration) but continuum could send mail. 853279 [pool-1-thread-1] ERROR org.apache.maven.continuum.notification.ContinuumNotificationDispatcher:default - Error while trying to use the mail notifier. org.codehaus.plexus.notification.NotificationException: Exception while sending message. at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendMessage(MailContinuumNotifier.java:566) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:387) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendNotification(MailContinuumNotifier.java:254) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:199) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:151) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.buildComplete(DefaultContinuumNotificationDispatcher.java:103) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.endBuild(DefaultBuildController.java:221) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:175) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:50) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:619) Caused by: org.codehaus.plexus.mailsender.MailSenderException: Error while sending the message. at org.codehaus.plexus.mailsender.javamail.AbstractJavamailMailSender.send(AbstractJavamailMailSender.java:226) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendMessage(MailContinuumNotifier.java:562) ... 14 more Caused by: javax.mail.MessagingException: Exception reading response; nested exception is: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? at com.sun.mail.smtp.SMTPTransport.readServerResponse(SMTPTransport.java:1462) at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1260) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:370) at javax.mail.Service.connect(Service.java:275) at org.codehaus.plexus.mailsender.javamail.AbstractJavamailMailSender.send(AbstractJavamailMailSender.java:212) ... 15 more Caused by: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? at com.sun.net.ssl.internal.ssl.InputRecord.handleUnknownRecord(InputRecord.java:521) at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:355) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1096) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:744) at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75) at com.sun.mail.util.TraceInputStream.read(TraceInputStream.java:97) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at com.sun.mail.util.LineInputStream.readLine(LineInputStream.java:75) at com.sun.mail.smtp.SMTPTransport.readServerResponse(SMTPTransport.java:1440) ... 19 more May be I forgot to set some other parameters? Thanks.
mail-notifier
Hi! I installed continuum as single application and have problem with notifier. I configured plexus.xml like in example (http://maven.apache.org/continuum/documentation/1_1/installation/standalone.html#Mail_server_configuration) but continuum could send mail. 853279 [pool-1-thread-1] ERROR org.apache.maven.continuum.notification.ContinuumNotificationDispatcher:default - Error while trying to use the mail notifier. org.codehaus.plexus.notification.NotificationException: Exception while sending message. at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendMessage(MailContinuumNotifier.java:566) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:387) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendNotification(MailContinuumNotifier.java:254) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:199) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:151) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.buildComplete(DefaultContinuumNotificationDispatcher.java:103) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.endBuild(DefaultBuildController.java:221) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:175) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:50) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:619) Caused by: org.codehaus.plexus.mailsender.MailSenderException: Error while sending the message. at org.codehaus.plexus.mailsender.javamail.AbstractJavamailMailSender.send(AbstractJavamailMailSender.java:226) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendMessage(MailContinuumNotifier.java:562) ... 14 more Caused by: javax.mail.MessagingException: Exception reading response; nested exception is: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? at com.sun.mail.smtp.SMTPTransport.readServerResponse(SMTPTransport.java:1462) at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1260) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:370) at javax.mail.Service.connect(Service.java:275) at org.codehaus.plexus.mailsender.javamail.AbstractJavamailMailSender.send(AbstractJavamailMailSender.java:212) ... 15 more Caused by: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? at com.sun.net.ssl.internal.ssl.InputRecord.handleUnknownRecord(InputRecord.java:521) at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:355) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1096) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:744) at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75) at com.sun.mail.util.TraceInputStream.read(TraceInputStream.java:97) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at com.sun.mail.util.LineInputStream.readLine(LineInputStream.java:75) at com.sun.mail.smtp.SMTPTransport.readServerResponse(SMTPTransport.java:1440) ... 19 more May be I forgot to set some other parameters? Thanks.
