Deploy problem with Maven2

 

I want to deploy my groovy scripts on axeda platform and i had followed  this how-to 

http://developer.axeda.com/learn/by-type/technical-article/developing-axeda-artisan 

but when i run the command, the script raise an error

 

 

mvn -f upload.xml -e -X

 

 

            

+ Error stacktraces are turned on.

Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)

Java version: 1.6.0_31

Java home: C:\Program Files\Java\jdk1.6.0_31\jre

Default locale: it_IT, platform encoding: Cp1252

OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"

[DEBUG] Building Maven user-level plugin registry from: 'C:\Users\Luca Gallici\.m2\plugin-registry.xml'

[DEBUG] Building Maven global-level plugin registry from: 'C:\Program Files\Apache Software foundation\apache-maven-2.2.1\conf\plugin-registry.xml'

[INFO] Scanning for projects...

[INFO] ------------------------------------------------------------------------

[ERROR] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO]

 

You must specify at least one goal or lifecycle phase to perform build steps.

The following list illustrates some commonly used build commands:

 

  mvn clean

    Deletes any build output (e.g. class files or JARs).

  mvn test

    Runs the unit tests for the project.

  mvn install

    Copies the project artifacts into your local repository.

  mvn deploy

    Copies the project artifacts into the remote repository.

  mvn site

    Creates project documentation (e.g. reports or Javadoc).

 

Please see

http://maven.apache.org/guides/introduction/introduction-to-the-lifecycl...

for a complete description of available lifecycle phases.

 

Use "mvn --help" to show general usage information about Maven's command line.

 

 

[INFO] ------------------------------------------------------------------------

[DEBUG] Trace

org.apache.maven.BuildFailureException:

 

You must specify at least one goal or lifecycle phase to perform build steps.

The following list illustrates some commonly used build commands:

 

  mvn clean

    Deletes any build output (e.g. class files or JARs).

  mvn test

    Runs the unit tests for the project.

  mvn install

    Copies the project artifacts into your local repository.

  mvn deploy

    Copies the project artifacts into the remote repository.

  mvn site

    Creates project documentation (e.g. reports or Javadoc).

 

Please see

http://maven.apache.org/guides/introduction/introduction-to-the-lifecycl...

for a complete description of available lifecycle phases.

 

Use "mvn --help" to show general usage information about Maven's command line.

 

 

        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:172)

        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)

        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)

        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)

        at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)

        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)

[INFO] ------------------------------------------------------------------------

[INFO] Total time: < 1 second

[INFO] Finished at: Mon May 14 11:17:09 CEST 2012

[INFO] Final Memory: 1M/57M

[INFO] ------------------------------------------------------------------------

 

Any suggestions?

Hi RedBass   You need to run

Hi RedBass

 

You need to run the mvn package -f upload.xml command from within the project directory

Try that and let me know if it works for you.

 

Thanks

 

Martin Tobias