Re: continuum 1.1-beta-4 on Windows 2000?

2007-11-06 Thread Emmanuel Venisse

Continuum is stable, but the stability can depends on lot of things (nb 
projects, schedule interval, build time average by project, memory, 
processor)

Emmanuel

VanIngen, Erik (ESTG) a écrit :
Hi continuum, 


We are working fine with continuum 1.1-beta-3 on Windows 2000. The only
annoying thing is that instability things keep happening like described
below. The reason is that some java processes or threads of Continuum are
remaining and locking resources.  


We don't want to upgrade to continuum 1.1-beta-4, unless it is resolving
stability issues like below. Am I right to say that beta-4 in not improving
the stability of Continuum?

Kind Regards,
Erik






-Original Message-
From: VanIngen, Erik (ESTG) 
Sent: 05 November 2007 09:24

To: continuum-users@maven.apache.org
Subject: Build Error: svn: Working copy '.' locked


Hi continuum, 


We are using continuum 1.1-beta-3 on Windows 2000. It is working fine but
today all of the sudden there is this message:


Build Error:

Provider message: The svn command failed.
Command output: 
-

--
svn: Working copy '.' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
Type 'svn help' for usage.
-
--

Does anyone have any idea how to solve this?

Kind Regards,
Erik van Ingen






continuum 1.1-beta-4 on Windows 2000?

2007-11-06 Thread VanIngen, Erik (ESTG)
Hi continuum, 

We are working fine with continuum 1.1-beta-3 on Windows 2000. The only
annoying thing is that instability things keep happening like described
below. The reason is that some java processes or threads of Continuum are
remaining and locking resources.  

We don't want to upgrade to continuum 1.1-beta-4, unless it is resolving
stability issues like below. Am I right to say that beta-4 in not improving
the stability of Continuum?

Kind Regards,
Erik






-Original Message-
From: VanIngen, Erik (ESTG) 
Sent: 05 November 2007 09:24
To: continuum-users@maven.apache.org
Subject: Build Error: svn: Working copy '.' locked


Hi continuum, 

We are using continuum 1.1-beta-3 on Windows 2000. It is working fine but
today all of the sudden there is this message:


Build Error:

Provider message: The svn command failed.
Command output: 
-
--
svn: Working copy '.' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
Type 'svn help' for usage.
-
--

Does anyone have any idea how to solve this?

Kind Regards,
Erik van Ingen


Re: builds not ordered by date

2007-11-06 Thread Emmanuel Venisse

Hmm, it isn't normal.
Please file an issue.

Emmanuel

Ionut S a écrit :
Sometimes I see that the build in progress is not the last one.. instead is somewhere below, after the builds that are already finished. 


Any idea why ?

 __
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 




Re: Shell builds in maven projects

2007-11-06 Thread Emmanuel Venisse



Raúl Arabaolaza Barquín a écrit :

Hi:

I,ve got  a shell project wich must be executed the last of my project group 
build queue.

When using continuum (1.1-beta4) you can add a build definition of type shell 
in a maven 2 project, but it dosen´t execute as a shell build but as a maven 
build. Is this the intended behaviour?


Hmm, no. Can we see the logs?



Alternativaly if you add a shell project you can´t specify dependencies so you can´t control the build order 


Is there a way to control the order in wich a shell project is executed into a 
m2 project group?


We'll add the possibility to add new dependencies to a project in 1.2 and 
Continuum use it only to find the order.

Maybe you can change your shell project to a m2 project and use the exec plugin 
to run your script. With this solution, you'll can configure maven dependencies 
so, the order.

Emmanuel



RE: Shell builds in maven projects

2007-11-06 Thread Raúl Arabaolaza Barquín


Hi:

This is part of the log:

1258990 [pool-1-thread-1] INFO  
org.apache.maven.continuum.buildcontroller.BuildController:default  - 
Performing action execute-builder
1259140 [pool-1-thread-1] INFO  
org.apache.maven.continuum.utils.shell.ShellCommandHelper:default  - Executing: 
cmd.exe /X /C 'C:\Archivos de programa\maven-2.0.7\bin\mvn -f 
copiarFicheros.bat -Dcontinuum.project.lastBuild.state=10 
-Dcontinuum.project.nextBuild.number=1 
-Dcontinuum.project.group.name=TelegestionMicronesiaParent 
-Dcontinuum.project.lastBuild.number=0'
1259140 [pool-1-thread-1] INFO  
org.apache.maven.continuum.utils.shell.ShellCommandHelper:default  - Working 
directory: C:\Archivos de 
programa\continuum-1.1-beta-4\apps\continuum\webapp\WEB-INF\working-directory\11
1260132 [pool-1-thread-1] INFO  
org.apache.maven.continuum.execution.ContinuumBuildExecutor:maven2  - Exit 
code: 0
1260232 [pool-1-thread-1] INFO  
org.apache.maven.continuum.buildcontroller.BuildController:default  - 
Performing action deploy-artifact

You can see that Continuum invokes maven but the build definition is of type 
shell, in fact when you try to add a shell build definition to a maven 2 
project the screen is the same that if you add a new m2 build definition. You 
can´t add the executable, but the pom file and the goals.

In the build result i obtain:

INFO] Scanning for projects...
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] You must specify at least one goal. Try 'install'
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: lt; 1 second
[INFO] Finished at: Tue Nov 06 19:52:54 CET 2007
[INFO] Final Memory: 1M/2M
[INFO] 

Which is the expected when you run maven without a valid goal.
 

I attach the entire log.

Thanks
Best Regards, Raul 

-Mensaje original-
De: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Enviado el: mar 06/11/2007 17:53
Para: continuum-users@maven.apache.org
Asunto: Re: Shell builds in maven projects
 


Raúl Arabaolaza Barquín a écrit :
 Hi:
 
 I,ve got  a shell project wich must be executed the last of my project group 
 build queue.
 
 When using continuum (1.1-beta4) you can add a build definition of type shell 
 in a maven 2 project, but it dosen´t execute as a shell build but as a maven 
 build. Is this the intended behaviour?

Hmm, no. Can we see the logs?

 
 Alternativaly if you add a shell project you can´t specify dependencies so 
 you can´t control the build order 
 
 Is there a way to control the order in wich a shell project is executed into 
 a m2 project group?

We'll add the possibility to add new dependencies to a project in 1.2 and 
Continuum use it only to find the order.

Maybe you can change your shell project to a m2 project and use the exec plugin 
to run your script. With this solution, you'll can configure maven dependencies 
so, the order.

Emmanuel




--
This e-mail and the documents attached are confidential and intended solely
for the addressee; it may also be privileged. If you receive this e-mail
in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin group
liability cannot be triggered for the message content. Although the
sender endeavours to maintain a computer virus-free network, the sender does
not warrant that this transmission is virus-free and will not be liable for
any damages resulting from any virus transmitted.

Este mensaje y los ficheros adjuntos pueden contener informacion
confidencial destinada solamente a la(s) persona(s) mencionadas
anteriormente. Pueden estar protegidos por secreto profesional Si usted
recibe este correo electronico por error, gracias de informar inmediatamente
al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
Origin no se hace responsable por su contenido. Su contenido no constituye
ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por
ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus
--


Re: locale settings

2007-11-06 Thread Erik Ruisma
Thanks a lot  for your answer.
I solved the problem be copying the continuum.proporties  file to
continuum_en.properties

I use firefox and I noticed the following in  the header (using
LiveHttpHeaders)
Accept-Language: en,nl;q=0.8,fr;q=0.5,no;q=0.3

I deleted the fr in the header  (by changing firefox settings) but I
continued to get the pages in english. So I decided to add a continuum_en
file.
So my problem is solved but I just wanted to let you know.



On Oct 31, 2007 6:49 PM, Emmanuel Venisse [EMAIL PROTECTED] wrote:

 The localization with french is new in this version and the locale to use
 is determined by the local sent by the browser to the server.

 If you don't want french, change your browser settings or remove
 _fr.properties file in the webapp.

 Emmanuel

 Erik Ruisma a écrit :
  Hello,
 
  I just installed the beta-4 of continuum.
  We run it standalone as a windows service (on windows server 2003).
  In previous releases (1.0.3 but also beta 3 and 2) continuum web pages
 were
  always displayed in English. Now (as of beta 4) they are in french.
  We still have the old version running on the same machine, and there the
  webapp is in English.
  Has anything changed in this release. How is the locale
  retrieved/determined?
 
  I'll check with our system admins to find out the specific settings for
 the
  user we use when running the service.
 
  I'll keep you informed, but any ideas are welcome.
 




RE: continuum 1.1-beta-4 on Windows 2000?

2007-11-06 Thread VanIngen, Erik (ESTG)
We are very enthousiastic about Continuum. But Continuum on Windows 2000 is
in our configuration not stable. More or less every week an instability
occurs.  Our configuration is plain and very straightforward. We build 4
projects which takes about 10 minutes (3 java projects and 1 web project).
The schedule is every hour. There are threads or processes remaining which
are breaking the build of the next hour. And thereofore we consider Continuum
on Windows 2000 as not stable. We did play with memory settings. It might be
very well stable on other platforms. In fact we are considering moving to
Linux. The question is, will that solve our problems?

Erik van Ingen



-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] 
Sent: 06 November 2007 14:18
To: continuum-users@maven.apache.org
Subject: Re: continuum 1.1-beta-4 on Windows 2000?


Continuum is stable, but the stability can depends on lot of things (nb
projects, schedule interval, build time average by project, memory,
processor)

Emmanuel

VanIngen, Erik (ESTG) a écrit :
 Hi continuum,
 
 We are working fine with continuum 1.1-beta-3 on Windows 2000. The 
 only annoying thing is that instability things keep happening like 
 described below. The reason is that some java processes or threads of 
 Continuum are remaining and locking resources.
 
 We don't want to upgrade to continuum 1.1-beta-4, unless it is 
 resolving stability issues like below. Am I right to say that beta-4 
 in not improving the stability of Continuum?
 
 Kind Regards,
 Erik
 
 
 
 
 
 
 -Original Message-
 From: VanIngen, Erik (ESTG)
 Sent: 05 November 2007 09:24
 To: continuum-users@maven.apache.org
 Subject: Build Error: svn: Working copy '.' locked
 
 
 Hi continuum,
 
 We are using continuum 1.1-beta-3 on Windows 2000. It is working fine 
 but today all of the sudden there is this message:
 
 **
 **
 Build Error:


 Provider message: The svn command failed.
 Command output: 

-
 --
 svn: Working copy '.' locked
 svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
details)
 Type 'svn help' for usage.

-
 --
 
 Does anyone have any idea how to solve this?
 
 Kind Regards,
 Erik van Ingen
 
 



Re: Shell builds in maven projects

2007-11-06 Thread Emmanuel Venisse

File an issue about the command line used for shell projects.

Emmanuel

Raúl Arabaolaza Barquín a écrit :

I forgot to attach the log

-Mensaje original-
De: Raúl Arabaolaza Barquín [mailto:[EMAIL PROTECTED]
Enviado el: mar 06/11/2007 20:04
Para: continuum-users@maven.apache.org
Asunto: RE: Shell builds in maven projects
 



Hi:

This is part of the log:

1258990 [pool-1-thread-1] INFO  
org.apache.maven.continuum.buildcontroller.BuildController:default  - 
Performing action execute-builder
1259140 [pool-1-thread-1] INFO  org.apache.maven.continuum.utils.shell.ShellCommandHelper:default  
- Executing: cmd.exe /X /C 'C:\Archivos de programa\maven-2.0.7\bin\mvn -f 
copiarFicheros.bat -Dcontinuum.project.lastBuild.state=10 -Dcontinuum.project.nextBuild.number=1 
-Dcontinuum.project.group.name=TelegestionMicronesiaParent 
-Dcontinuum.project.lastBuild.number=0'
1259140 [pool-1-thread-1] INFO  
org.apache.maven.continuum.utils.shell.ShellCommandHelper:default  - Working 
directory: C:\Archivos de 
programa\continuum-1.1-beta-4\apps\continuum\webapp\WEB-INF\working-directory\11
1260132 [pool-1-thread-1] INFO  
org.apache.maven.continuum.execution.ContinuumBuildExecutor:maven2  - Exit 
code: 0
1260232 [pool-1-thread-1] INFO  
org.apache.maven.continuum.buildcontroller.BuildController:default  - 
Performing action deploy-artifact

You can see that Continuum invokes maven but the build definition is of type 
shell, in fact when you try to add a shell build definition to a maven 2 
project the screen is the same that if you add a new m2 build definition. You 
can´t add the executable, but the pom file and the goals.

In the build result i obtain:

INFO] Scanning for projects...
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] You must specify at least one goal. Try 'install'
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: lt; 1 second
[INFO] Finished at: Tue Nov 06 19:52:54 CET 2007
[INFO] Final Memory: 1M/2M
[INFO] 

Which is the expected when you run maven without a valid goal.
 


I attach the entire log.

Thanks
Best Regards, Raul 


-Mensaje original-
De: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Enviado el: mar 06/11/2007 17:53
Para: continuum-users@maven.apache.org
Asunto: Re: Shell builds in maven projects
 



Raúl Arabaolaza Barquín a écrit :

Hi:

I,ve got  a shell project wich must be executed the last of my project group 
build queue.

When using continuum (1.1-beta4) you can add a build definition of type shell 
in a maven 2 project, but it dosen´t execute as a shell build but as a maven 
build. Is this the intended behaviour?


Hmm, no. Can we see the logs?

Alternativaly if you add a shell project you can´t specify dependencies so you can´t control the build order 


Is there a way to control the order in wich a shell project is executed into a 
m2 project group?


We'll add the possibility to add new dependencies to a project in 1.2 and 
Continuum use it only to find the order.

Maybe you can change your shell project to a m2 project and use the exec plugin 
to run your script. With this solution, you'll can configure maven dependencies 
so, the order.

Emmanuel




--
This e-mail and the documents attached are confidential and intended solely
for the addressee; it may also be privileged. If you receive this e-mail
in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin group
liability cannot be triggered for the message content. Although the
sender endeavours to maintain a computer virus-free network, the sender does
not warrant that this transmission is virus-free and will not be liable for
any damages resulting from any virus transmitted.

Este mensaje y los ficheros adjuntos pueden contener informacion
confidencial destinada solamente a la(s) persona(s) mencionadas
anteriormente. Pueden estar protegidos por secreto profesional Si usted
recibe este correo electronico por error, gracias de informar inmediatamente
al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
Origin no se hace responsable por su contenido. Su contenido no constituye
ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por
ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus
--