maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Pöllath <li...@poellath.org>
Subject [m2-b2] install:install-file fails without pom
Date Wed, 28 Sep 2005 17:36:39 GMT
Hi,

installing a jar into my local repository as explained at [1]:

/tmp % m2 install:install-file \
-Dfile=/tmp/eXtremeComponents-1.0.2-M1.jar  \
-DgroupId=org.eXtremeComponents  \
-DartifactId=eXtremeComponents  \
-Dversion=1.0.2-M1 \
-Dpackaging=jar

fails with "Cannot execute mojo: install-file. It requires a project,  
but the build is not using one" (full trace below).

This looks like MNG-432 [2], which is supposed to be fixed. Can  
anyone help?

I noticed the install-plugin used is 2.0-beta-1, while m2 itself is  
at 2.0-beta-2. Is that correct?

Thanks,
-Ralph.

[1] http://maven.apache.org/maven2/general.html#importing-jars
[2] http://jira.codehaus.org/browse/MNG-432

/tmp % m2 -v
Maven version: 2.0-beta-2

[DEBUG] maven-install-plugin: resolved to version 2.0-beta-1 from  
repository central
[INFO]  
------------------------------------------------------------------------ 
----
[INFO] Building Maven Default Project
[INFO]    task-segment: [install:install-file]
[INFO]  
------------------------------------------------------------------------ 
----
[INFO]  
------------------------------------------------------------------------ 
----
[INFO] BUILD FAILURE
[INFO]  
------------------------------------------------------------------------ 
----
[INFO] Reason: Cannot execute mojo: install-file. It requires a  
project, but the build is not using one.
[INFO]  
------------------------------------------------------------------------ 
----
[DEBUG] Trace
org.apache.maven.plugin.MojoExecutionException: Cannot execute mojo:  
install-file. It requires a project, but the build is not using one.
         at org.apache.maven.plugin.DefaultPluginManager.executeMojo 
(DefaultPluginManager.java:318)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals 
(DefaultLifecycleExecutor.java:515)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa 
l(DefaultLifecycleExecutor.java:478)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal 
(DefaultLifecycleExecutor.java:460)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( 
DefaultLifecycleExecutor.java:278)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute 
(DefaultLifecycleExecutor.java:136)
         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:216)
         at org.apache.maven.cli.MavenCli.main(MavenCli.java:246)
         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:324)
         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]  
------------------------------------------------------------------------ 
----


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message