Re: Re : Re : Re : Re : Build number and current date
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
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 : 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]
[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
