Re: Re : Build number and current date

2007-11-19 Thread Julian Wood 
What does your scm tag look like? It needs an svn config at the  
moment, or else you need to configure it to use a sequential number  
(or something else) if you don't use svn. Or if you use cvs or  
something else, you could contribute the code.


The project is housed at the codehaus now:

http://mojo.codehaus.org/buildnumber-maven-plugin/


org.codehaus.mojo
buildnumber-maven-plugin
1.0-beta-1




mojo
Codehaus
http://repository.codehaus.org



J


On 19-Nov-07, at 4:48 AM, tec-goblin wrote:



Same problem here. Configured scm but we get the same error:
Cannot get the revision information from the scm repository :
Can't load the scm provider.

The scm url cannot be null.

If we remove the plugin from the pom, everything works ok.
Time to look at it, isn'it? ;-)


oups !

I tried to add this to the pom :


.



 org.codehaus.mojo
  maven-buildnumber-plugin
  0.9.4
  

  validate
  
create
  

  
  
true
true
  


  
...




tlc
TLC Repository
http://commons.ucalgary.ca/pub/m2

  

but unfortunately : here's the log !

[DEBUG]   Artifact resolved
[DEBUG] Configuring mojo
'org.codehaus.mojo:maven-buildnumber-plugin:0.9.4:create' -->
[DEBUG]   (s) basedir = C:\works\workspaceM2\TutelecOJV-v1.3
[DEBUG]   (s) doCheck = true
[DEBUG]   (s) doUpdate = true
[DEBUG]   (f) project = [EMAIL PROTECTED]
[DEBUG] -- end configuration --
[INFO] [buildnumber:create {execution: default}]
[INFO] Verifying there are no local modifications ...
[INFO]
-- 
--

[ERROR] BUILD ERROR
[INFO]
-- 
--

[INFO] An error has occurred while checking scm status.

Embedded error: Can't load the scm provider.
The scm url cannot be null.
--
View this message in context: http://www.nabble.com/Re-%3A-Build- 
number-and-current-date-tf3653099s177.html#a13834427

Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Julian Wood
Web, E-Mail, and Middleware Services
University of Calgary Information Technologies,
2500 University Drive, Calgary, Alberta, Canada T2N 1N4
(403) 220-5868

Re: Re : Build number and current date

2007-11-19 Thread tec-goblin 

Same problem here. Configured scm but we get the same error:
Cannot get the revision information from the scm repository : 
Can't load the scm provider.

The scm url cannot be null.

If we remove the plugin from the pom, everything works ok. 
Time to look at it, isn'it? ;-)


oups !

I tried to add this to the pom :


.



 org.codehaus.mojo
  maven-buildnumber-plugin
  0.9.4
  

  validate
  
create
  

  
  
true
true
  


  
...




tlc
TLC Repository
http://commons.ucalgary.ca/pub/m2

  

but unfortunately : here's the log !

[DEBUG]   Artifact resolved
[DEBUG] Configuring mojo
'org.codehaus.mojo:maven-buildnumber-plugin:0.9.4:create' -->
[DEBUG]   (s) basedir = C:\works\workspaceM2\TutelecOJV-v1.3
[DEBUG]   (s) doCheck = true
[DEBUG]   (s) doUpdate = true
[DEBUG]   (f) project = [EMAIL PROTECTED]
[DEBUG] -- end configuration --
[INFO] [buildnumber:create {execution: default}]
[INFO] Verifying there are no local modifications ...
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] An error has occurred while checking scm status.

Embedded error: Can't load the scm provider.
The scm url cannot be null.
-- 
View this message in context: 
http://www.nabble.com/Re-%3A-Build-number-and-current-date-tf3653099s177.html#a13834427
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re : Re : Re : Re : Build number and current date

2007-04-27 Thread Wayne Fay 

Maven SCM calls out to your svn binary to do its work. Therefore, you
must have a Subversion binary somewhere on your path. I have no idea
if the Eclipse bundle includes a binary or not.

Wayne

On 4/27/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

I'm  using 'The Eclipse Team Provider for the Subversion version control 
system.' not the binary

is it necessary to have the binary if I want to get the build number ?

Thanks friends
Nawfel

- Message d'origine 
De : Wayne Fay <[EMAIL PROTECTED]>
À : Maven Users List 
Envoyé le : Jeudi, 26 Avril 2007, 19h47mn 19s
Objet : Re: Re : Re : Re : Build number and current date

You *are* using Subversion for your source code management/repository, correct?

Make sure the "svn" binary is installed on your machine and in your
path -- typing "svn --version" should give a result. Then type "mvn
..." from that same command line.

Wayne

On 4/26/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I used this in my pom :
>
>  
> scm:svn:https://www.mycompany.ma/svnrepos/myAppName/v1.3
>scm:svn:https://www.mycompany.ma/svnrepos/myAppName/v1.3
>https://www.mycompany.ma/svnrepos/myAppName/v1.3
>  
>
> but i had this in the log :
>
> [DEBUG] Configuring mojo 
'org.codehaus.mojo:maven-buildnumber-plugin:0.9.4:create' -->
> [DEBUG]   (s) basedir = C:\works\workspaceM2\myAppName-v1.3
> [DEBUG]   (s) doCheck = true
> [DEBUG]   (s) doUpdate = true
> [DEBUG]   (f) project = [EMAIL PROTECTED]
> [DEBUG]   (s) urlScm = 
scm:svn:https://www.mycompany.ma/svnrepos/myAppName/v1.3
> [DEBUG] -- end configuration --
> [INFO] [buildnumber:create {execution: default}]
> [INFO] Verifying there are no local modifications ...
> [INFO] Executing: svn --non-interactive status
> [INFO] Working directory: C:\works\workspaceM2\myAppName-v1.3
> Provider message:
> The svn command failed.
> [INFO] 

> [ERROR] BUILD ERROR
> [INFO] 

> Command output:
> 'svn' is not recognized as an internal or external command,
> operable program or batch file.
>
> [INFO] An error has occurred while checking scm status.
>
> Embedded error: Error!
> [INFO] 

> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred 
while checking scm status.
>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:272)
>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:597)
>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: An error has 
occurred while checking scm status.
>at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkForLocalModifications(BuildNumberMojo.java:331)
>at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.execute(BuildNumberMojo.java:288)
>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.scm.ScmException: Error!
>at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkResult(BuildNumberMojo.java:510)
>at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.getStatus(BuildNumberMojo.java:388)
>at 
org.codehaus.mo

Re : Re : Re : Re : Build number and current date

2007-04-27 Thread spouynt 
I'm  using 'The Eclipse Team Provider for the Subversion version control 
system.' not the binary

is it necessary to have the binary if I want to get the build number ?

Thanks friends
Nawfel

- Message d'origine 
De : Wayne Fay <[EMAIL PROTECTED]>
À : Maven Users List 
Envoyé le : Jeudi, 26 Avril 2007, 19h47mn 19s
Objet : Re: Re : Re : Re : Build number and current date

You *are* using Subversion for your source code management/repository, correct?

Make sure the "svn" binary is installed on your machine and in your
path -- typing "svn --version" should give a result. Then type "mvn
..." from that same command line.

Wayne

On 4/26/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I used this in my pom :
>
>  
> scm:svn:https://www.mycompany.ma/svnrepos/myAppName/v1.3
>scm:svn:https://www.mycompany.ma/svnrepos/myAppName/v1.3
>https://www.mycompany.ma/svnrepos/myAppName/v1.3
>  
>
> but i had this in the log :
>
> [DEBUG] Configuring mojo 
> 'org.codehaus.mojo:maven-buildnumber-plugin:0.9.4:create' -->
> [DEBUG]   (s) basedir = C:\works\workspaceM2\myAppName-v1.3
> [DEBUG]   (s) doCheck = true
> [DEBUG]   (s) doUpdate = true
> [DEBUG]   (f) project = [EMAIL PROTECTED]
> [DEBUG]   (s) urlScm = 
> scm:svn:https://www.mycompany.ma/svnrepos/myAppName/v1.3
> [DEBUG] -- end configuration --
> [INFO] [buildnumber:create {execution: default}]
> [INFO] Verifying there are no local modifications ...
> [INFO] Executing: svn --non-interactive status
> [INFO] Working directory: C:\works\workspaceM2\myAppName-v1.3
> Provider message:
> The svn command failed.
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> Command output:
> 'svn' is not recognized as an internal or external command,
> operable program or batch file.
>
> [INFO] An error has occurred while checking scm status.
>
> Embedded error: Error!
> [INFO] 
> 
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred 
> while checking scm status.
>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:272)
>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:597)
>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: An error has 
> occurred while checking scm status.
>at 
> org.codehaus.mojo.buildNumber.BuildNumberMojo.checkForLocalModifications(BuildNumberMojo.java:331)
>at 
> org.codehaus.mojo.buildNumber.BuildNumberMojo.execute(BuildNumberMojo.java:288)
>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.scm.ScmException: Error!
>at 
> org.codehaus.mojo.buildNumber.BuildNumberMojo.checkResult(BuildNumberMojo.java:510)
>at 
> org.codehaus.mojo.buildNumber.BuildNumberMojo.getStatus(BuildNumberMojo.java:388)
>at 
> org.codehaus.mojo.buildNumber.BuildNumberMojo.checkForLocalModifications(BuildNumberMojo.java:327)
>... 19 more
> [INFO] 
> -

Re : Re : Re : Build number and current date

2007-04-27 Thread spouynt 

I used this in my pom :







 
scm:svn:https://www.ilem.ma/svnrepos/TutelecOJV/v1.3


scm:svn:https://www.ilem.ma/svnrepos/TutelecOJV/v1.3

https://www.ilem.ma/svnrepos/TutelecOJV/v1.3

  



 
but i had this in the log :



[DEBUG] Configuring mojo  
'org.codehaus.mojo:maven-buildnumber-plugin:0.9.4:create' -->

[DEBUG]   (s) basedir = C:\works\workspaceM2\myAppName-v1.3

[DEBUG]   (s) doCheck = true

[DEBUG]   (s) doUpdate = true

[DEBUG]   (f) project = [EMAIL PROTECTED]

[DEBUG]   (s) urlScm = scm:svn:https://www.mycompany.ma/svnrepos/myAppName/v1.3

[DEBUG] -- end configuration --

[INFO] [buildnumber:create {execution: default}]

[INFO] Verifying there are no local modifications ...

[INFO] Executing: svn --non-interactive status

[INFO] Working directory: C:\works\workspaceM2\myAppName-v1.3

Provider message:

The svn command failed.

[INFO] 

[ERROR] BUILD ERROR

[INFO]  

Command output:

'svn' is not recognized as an internal or external command,

operable program or batch file.



[INFO] An error has occurred while checking scm status.



Embedded error: Error!

[INFO] 

[DEBUG] Trace

org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred 
while checking scm status.

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:272)

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:597)

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: An error has 
occurred while checking scm status.

at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkForLocalModifications(BuildNumberMojo.java:331)

at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.execute(BuildNumberMojo.java:288)

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.scm.ScmException: Error!

at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkResult(BuildNumberMojo.java:510)

at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.getStatus(BuildNumberMojo.java:388)

at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkForLocalModifications(BuildNumberMojo.java:327)

... 19 more

[INFO] 

[INFO] Total time: 3 seconds

[INFO] Finished at: Thu Apr 26 19:03:22 GMT 2007

[INFO] Final Memory: 4M/9M

[INFO] 





- Message d'origine 

De : Phill Moran  <[EMAIL PROTECTED]>

À : [EMAIL PROTECTED]

Envoyé le : Jeudi, 26 Avril 2007, 18h25mn 03s

Objet : RE: [m2eclipse-user] Re : Re : Build number and current date



DIV { MARGIN:0px;}You use a combination of  
username@ and in your settings.xml you have   and user/password combo

  

Phill

   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]  

Sent: April 26, 2007 2:11 PM

To: Maven Users List;  [EMAIL PROTECTED]

Cc: [EMAIL PROTECTED]

Subject:  [m2eclipse-user] Re : Re : Build number and current date





 

  can  you be more specific please ? 

and about the username and password ? how will  I do ?

is it really necessary ?



thanks 

Nawfel



 -  Message d'origine 

De : Trevor Spackman <[EMAIL PROTECTED]>

À  : Maven Users List 

Envoyé le : Jeudi, 26 Avril  200

Re: Re : Re : Re : Build number and current date

2007-04-26 Thread Wayne Fay 

You *are* using Subversion for your source code management/repository, correct?

Make sure the "svn" binary is installed on your machine and in your
path -- typing "svn --version" should give a result. Then type "mvn
..." from that same command line.

Wayne

On 4/26/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

I used this in my pom :

 
scm:svn:https://www.mycompany.ma/svnrepos/myAppName/v1.3
   scm:svn:https://www.mycompany.ma/svnrepos/myAppName/v1.3
   https://www.mycompany.ma/svnrepos/myAppName/v1.3
 

but i had this in the log :

[DEBUG] Configuring mojo 'org.codehaus.mojo:maven-buildnumber-plugin:0.9.4:create' 
-->
[DEBUG]   (s) basedir = C:\works\workspaceM2\myAppName-v1.3
[DEBUG]   (s) doCheck = true
[DEBUG]   (s) doUpdate = true
[DEBUG]   (f) project = [EMAIL PROTECTED]
[DEBUG]   (s) urlScm = scm:svn:https://www.mycompany.ma/svnrepos/myAppName/v1.3
[DEBUG] -- end configuration --
[INFO] [buildnumber:create {execution: default}]
[INFO] Verifying there are no local modifications ...
[INFO] Executing: svn --non-interactive status
[INFO] Working directory: C:\works\workspaceM2\myAppName-v1.3
Provider message:
The svn command failed.
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
Command output:
'svn' is not recognized as an internal or external command,
operable program or batch file.

[INFO] An error has occurred while checking scm status.

Embedded error: Error!
[INFO] 
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred 
while checking scm status.
   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:272)
   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:597)
   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: An error has 
occurred while checking scm status.
   at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkForLocalModifications(BuildNumberMojo.java:331)
   at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.execute(BuildNumberMojo.java:288)
   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.scm.ScmException: Error!
   at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkResult(BuildNumberMojo.java:510)
   at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.getStatus(BuildNumberMojo.java:388)
   at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkForLocalModifications(BuildNumberMojo.java:327)
   ... 19 more
[INFO] 
[INFO] Total time: 3 seconds
[INFO] Finished at: Thu Apr 26 19:03:22 GMT 2007
[INFO] Final Memory: 4M/9M
[INFO] 


- Message d'origine 
De : Phill Moran <[EMAIL PROTECTED]>
À : [EMAIL PROTECTED]
Envoyé le : Jeudi, 26 Avril 2007, 18h25mn 03s
Objet : RE: [m2eclipse-user] Re : Re : Build number and current date




DIV {
MARGIN:0px;}



You use a combination of
username@ and in your settings.xml you have
 and user/password combo


Phill



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Sent: April 26, 2007 2:11 PM
To: Maven Users List;
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject:
[m2eclipse-user] Re : Re : Build number and current date






can
you be more specific please ?
and about the us

Re : Re : Re : Build number and current date

2007-04-26 Thread spouynt 
I used this in my pom :

 
 scm:svn:https://www.mycompany.ma/svnrepos/myAppName/v1.3
scm:svn:https://www.mycompany.ma/svnrepos/myAppName/v1.3
https://www.mycompany.ma/svnrepos/myAppName/v1.3
  

but i had this in the log :

[DEBUG] Configuring mojo 
'org.codehaus.mojo:maven-buildnumber-plugin:0.9.4:create' -->
[DEBUG]   (s) basedir = C:\works\workspaceM2\myAppName-v1.3
[DEBUG]   (s) doCheck = true
[DEBUG]   (s) doUpdate = true
[DEBUG]   (f) project = [EMAIL PROTECTED]
[DEBUG]   (s) urlScm = scm:svn:https://www.mycompany.ma/svnrepos/myAppName/v1.3
[DEBUG] -- end configuration --
[INFO] [buildnumber:create {execution: default}]
[INFO] Verifying there are no local modifications ...
[INFO] Executing: svn --non-interactive status
[INFO] Working directory: C:\works\workspaceM2\myAppName-v1.3
Provider message:
The svn command failed.
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
Command output:
'svn' is not recognized as an internal or external command,
operable program or batch file.

[INFO] An error has occurred while checking scm status.

Embedded error: Error!
[INFO] 
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred 
while checking scm status.
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:272)
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:597)
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: An error has 
occurred while checking scm status.
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkForLocalModifications(BuildNumberMojo.java:331)
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.execute(BuildNumberMojo.java:288)
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.scm.ScmException: Error!
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkResult(BuildNumberMojo.java:510)
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.getStatus(BuildNumberMojo.java:388)
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkForLocalModifications(BuildNumberMojo.java:327)
... 19 more
[INFO] 
[INFO] Total time: 3 seconds
[INFO] Finished at: Thu Apr 26 19:03:22 GMT 2007
[INFO] Final Memory: 4M/9M
[INFO] 


- Message d'origine 
De : Phill Moran <[EMAIL PROTECTED]>
À : [EMAIL PROTECTED]
Envoyé le : Jeudi, 26 Avril 2007, 18h25mn 03s
Objet : RE: [m2eclipse-user] Re : Re : Build number and current date



 
DIV {
MARGIN:0px;}



You use a combination of 
username@ and in your settings.xml you have 
 and user/password combo

 
Phill



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 

Sent: April 26, 2007 2:11 PM
To: Maven Users List; 
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: 
[m2eclipse-user] Re : Re : Build number and current date






can 
you be more specific please ? 
and about the username and password ? how will 
I do ?
is it really necessary ?

thanks 
Nawfel


- 
Message d'origine 
De : Trevor Spackman <[EMAIL PROTECTED]>
À 
: Maven Users List 
Envoyé le : Jeudi, 26 Avril 
2007, 18h01mn 14s
Objet : RE: Re : Build number and current date


Looks like you need to tell the po

Re : Re : Build number and current date

2007-04-26 Thread spouynt 
can you be more specific please ? 
and about the username and password ? how will I do ?
is it really necessary ?

thanks 
Nawfel

- Message d'origine 
De : Trevor Spackman <[EMAIL PROTECTED]>
À : Maven Users List 
Envoyé le : Jeudi, 26 Avril 2007, 18h01mn 14s
Objet : RE: Re : Build number and current date

Looks like you need to tell the pom where the scm is...

I have something like this in my pom.


  ...
  
scm:svn:http://example.com/artifactId/trunk
  
  ...

 

Trevor Spackman
 
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 26, 2007 11:39 AM
To: Maven Users List
Subject: Re : Build number and current date

oups !

I tried to add this to the pom :


.



 org.codehaus.mojo
  maven-buildnumber-plugin
  0.9.4
  

  validate
  
create
  

  
  
true
true
  


  
...




tlc
TLC Repository
http://commons.ucalgary.ca/pub/m2

  

but unfortunately : here's the log !

[DEBUG]   Artifact resolved
[DEBUG] Configuring mojo 
'org.codehaus.mojo:maven-buildnumber-plugin:0.9.4:create' -->
[DEBUG]   (s) basedir = C:\works\workspaceM2\TutelecOJV-v1.3
[DEBUG]   (s) doCheck = true
[DEBUG]   (s) doUpdate = true
[DEBUG]   (f) project = [EMAIL PROTECTED]
[DEBUG] -- end configuration --
[INFO] [buildnumber:create {execution: default}]
[INFO] Verifying there are no local modifications ...
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] An error has occurred while checking scm status.

Embedded error: Can't load the scm provider.
The scm url cannot be null.
[INFO] 
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred 
while checking scm status.
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:272)
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:597)
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: An error has 
occurred while checking scm status.
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkForLocalModifications(BuildNumberMojo.java:331)
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.execute(BuildNumberMojo.java:288)
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.scm.ScmException: Can't load the scm provider.
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.getScmRepository(BuildNumberMojo.java:490)
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.getStatus(BuildNumberMojo.java:384)
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkForLocalModifications(BuildNumberMojo.java:327)
... 19 more
Caused by: java.lang.NullPointerException: The scm url cannot be null.
at 
org.apache.maven.scm.manager.AbstractScmManager.makeScmRepository(AbstractScmManager.java:122)
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.getScmRepository(BuildNumberMojo.java:465)
... 21 more
[INFO] 
[INFO] Total time: 1 minute 
[INFO] Finished at: Thu Apr 26 17:17:25 GM

RE: Re : Build number and current date

2007-04-26 Thread Trevor Spackman 
Looks like you need to tell the pom where the scm is...

I have something like this in my pom.


  ...
  
scm:svn:http://example.com/artifactId/trunk
  
  ...

 

Trevor Spackman
 
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 26, 2007 11:39 AM
To: Maven Users List
Subject: Re : Build number and current date

oups !

I tried to add this to the pom :


.



 org.codehaus.mojo
  maven-buildnumber-plugin
  0.9.4
  

  validate
  
create
  

  
  
true
true
  


  
...




tlc
TLC Repository
http://commons.ucalgary.ca/pub/m2

  

but unfortunately : here's the log !

[DEBUG]   Artifact resolved
[DEBUG] Configuring mojo 
'org.codehaus.mojo:maven-buildnumber-plugin:0.9.4:create' -->
[DEBUG]   (s) basedir = C:\works\workspaceM2\TutelecOJV-v1.3
[DEBUG]   (s) doCheck = true
[DEBUG]   (s) doUpdate = true
[DEBUG]   (f) project = [EMAIL PROTECTED]
[DEBUG] -- end configuration --
[INFO] [buildnumber:create {execution: default}]
[INFO] Verifying there are no local modifications ...
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] An error has occurred while checking scm status.

Embedded error: Can't load the scm provider.
The scm url cannot be null.
[INFO] 
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred 
while checking scm status.
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:272)
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:597)
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: An error has 
occurred while checking scm status.
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkForLocalModifications(BuildNumberMojo.java:331)
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.execute(BuildNumberMojo.java:288)
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.scm.ScmException: Can't load the scm provider.
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.getScmRepository(BuildNumberMojo.java:490)
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.getStatus(BuildNumberMojo.java:384)
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkForLocalModifications(BuildNumberMojo.java:327)
... 19 more
Caused by: java.lang.NullPointerException: The scm url cannot be null.
at 
org.apache.maven.scm.manager.AbstractScmManager.makeScmRepository(AbstractScmManager.java:122)
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.getScmRepository(BuildNumberMojo.java:465)
... 21 more
[INFO] 
[INFO] Total time: 1 minute 
[INFO] Finished at: Thu Apr 26 17:17:25 GMT 2007
[INFO] Final Memory: 4M/8M
[INFO] 


can someone help me please ?

- Message d'origine 
De : Patrick Schneider <[EMAIL PROTECTED]>
À : Maven Users List 
Cc : [EMAIL PROTECTED]
Envoyé le : Mercredi, 25 Avril 2007, 21h38mn 50s
Objet : Re: Build number and current da

Re : Build number and current date

2007-04-26 Thread spouynt 
oups !

I tried to add this to the pom :


.



 org.codehaus.mojo
  maven-buildnumber-plugin
  0.9.4
  

  validate
  
create
  

  
  
true
true
  


  
...




tlc
TLC Repository
http://commons.ucalgary.ca/pub/m2

  

but unfortunately : here's the log !

[DEBUG]   Artifact resolved
[DEBUG] Configuring mojo 
'org.codehaus.mojo:maven-buildnumber-plugin:0.9.4:create' -->
[DEBUG]   (s) basedir = C:\works\workspaceM2\TutelecOJV-v1.3
[DEBUG]   (s) doCheck = true
[DEBUG]   (s) doUpdate = true
[DEBUG]   (f) project = [EMAIL PROTECTED]
[DEBUG] -- end configuration --
[INFO] [buildnumber:create {execution: default}]
[INFO] Verifying there are no local modifications ...
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] An error has occurred while checking scm status.

Embedded error: Can't load the scm provider.
The scm url cannot be null.
[INFO] 
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred 
while checking scm status.
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:272)
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:597)
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: An error has 
occurred while checking scm status.
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkForLocalModifications(BuildNumberMojo.java:331)
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.execute(BuildNumberMojo.java:288)
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.scm.ScmException: Can't load the scm provider.
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.getScmRepository(BuildNumberMojo.java:490)
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.getStatus(BuildNumberMojo.java:384)
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.checkForLocalModifications(BuildNumberMojo.java:327)
... 19 more
Caused by: java.lang.NullPointerException: The scm url cannot be null.
at 
org.apache.maven.scm.manager.AbstractScmManager.makeScmRepository(AbstractScmManager.java:122)
at 
org.codehaus.mojo.buildNumber.BuildNumberMojo.getScmRepository(BuildNumberMojo.java:465)
... 21 more
[INFO] 
[INFO] Total time: 1 minute 
[INFO] Finished at: Thu Apr 26 17:17:25 GMT 2007
[INFO] Final Memory: 4M/8M
[INFO] 


can someone help me please ?

- Message d'origine 
De : Patrick Schneider <[EMAIL PROTECTED]>
À : Maven Users List 
Cc : [EMAIL PROTECTED]
Envoyé le : Mercredi, 25 Avril 2007, 21h38mn 50s
Objet : Re: Build number and current date

You might look into the buildnumber plugin:

http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/index.html


Patrick

On 4/25/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> hello,
> how can I get the current date (formatted in english) and/or build number
> ??
>
> i.e : something like

Re: Build number and current date

2007-04-25 Thread Patrick Schneider 

You might look into the buildnumber plugin:

http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/index.html


Patrick

On 4/25/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:


hello,
how can I get the current date (formatted in english) and/or build number
??

i.e : something like a property or a filter or a $mvn.something

Thanks
Nawfel






___
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions
!
Profitez des connaissances, des opinions et des expériences des
internautes sur Yahoo! Questions/Réponses
http://fr.answers.yahoo.com

Re: Build number and current date

2007-04-25 Thread Tomasz Pik 

On 4/25/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

hello,
how can I get the current date (formatted in english) and/or build number ??

i.e : something like a property or a filter or a $mvn.something


check ${project.artifact.version}

Regards,
Tomek

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Build number and current date

2007-04-25 Thread spouynt 
hello,
how can I get the current date (formatted in english) and/or build number ??

i.e : something like a property or a filter or a $mvn.something

Thanks
Nawfel




  
___ 
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! 
Profitez des connaissances, des opinions et des expériences des internautes sur 
Yahoo! Questions/Réponses 
http://fr.answers.yahoo.com