Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Maven Integration (M2E) » Unable to package project(m2e no longer able to run package configuration)
Unable to package project [message #631471] Thu, 07 October 2010 15:46 Go to next message
Travis Woolworth is currently offline Travis WoolworthFriend
Messages: 2
Registered: October 2010
Junior Member
I'm trying to package my project so that I can release it live in our production environment and am currently having trouble, the weird part is this used to work until one day I came in and it just stopped, there hasn't really been any code changes since the transition of it working to not working but obviously something had to of changed for it to break. This is my first maven project so I'm a beginning and I've been unsuccessful in finding references to any of the lines given in the stack trace.

If someone could point me in the right direction of what might possibly be going wrong I'd much appreciate it. Here is the full error console when I attempt to package my application (this is not a web application).

Apache Maven 3.0-SNAPSHOT (r910004; 2010-02-18 16:19:44-0700)
Java version: 1.6.0_18
Java home: C:\Program Files\Java\jdk1.6.0_18\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7" version: "6.1" arch: "x86" Family: "windows"
[INFO] Error stacktraces are turned on.
[DEBUG] Reading user settings from C:\Users\twoolworth\.m2\settings.xml
[DEBUG] Reading global settings from EMBEDDED\conf\settings.xml
[DEBUG] Using local repository at C:\Users\twoolworth\.m2\repository
[INFO] Scanning for projects...
[DEBUG] Extension realms for project com.homesmart:smartrets:jar:1.0.1-SNAPSHOT: (none)
[DEBUG] Looking up lifecyle mappings for packaging jar from ClassRealm[plexus.core, parent
: null]
[DEBUG] Resolving plugin prefix package from [org.apache.maven.plugins, org.codehaus.mojo]
2010-10-07 08:37:40.523:INFO::Logging to StdErrLog::DEBUG=false via org.eclipse.jetty.util
.log.StdErrLog
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metadata.xml
9 KB downloaded at 31.0 KB/sec
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metadata.xml
9 KB downloaded at 56.3 KB/sec
Downloading: http://repo1.maven.org/maven2/org/codehaus/mojo/maven-metadata.xml
17 KB downloaded at 105.3 KB/sec
Downloading: http://repo1.maven.org/maven2/org/codehaus/mojo/maven-metadata.xml
17 KB downloaded at 109.5 KB/sec
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.910s
[INFO] Finished at: Thu Oct 07 08:37:44 MST 2010
[INFO] Final Memory: 4M/15M
[INFO] ------------------------------------------------------------------------
[ERROR] No plugin found for prefix 'package' in the current project and in the plugin grou
ps [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (C
:\Users\twoolworth\.m2\repository), central (http://repo1.maven.org/maven2)] -> [Help 1]
org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin found for prefix
 'package' in the current project and in the plugin groups [org.apache.maven.plugins, org.
codehaus.mojo] available from the repositories [local (C:\Users\twoolworth\.m2\repository)
, central (http://repo1.maven.org/maven2)]
	at org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPlu
ginPrefixResolver.java:82)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findPluginForPrefix(DefaultLifecyc
leExecutor.java:1795)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycle
Executor.java:1533)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.calculateTaskSegments(DefaultLifec
ycleExecutor.java:862)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.calculateProjectBuilds(DefaultLife
cycleExecutor.java:752)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.j
ava:251)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:247)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:104)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:427)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:157)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:121)
	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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
[ERROR] 
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the foll
owing articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixEx
ception
Re: Unable to package project [message #631755 is a reply to message #631471] Fri, 08 October 2010 15:49 Go to previous message
Travis Woolworth is currently offline Travis WoolworthFriend
Messages: 2
Registered: October 2010
Junior Member
I was never able to get this solved but doing it via a different menu item of right click on project, Run As, Maven package seems to work, and did give me info on some errors I had in the configuration files. The run configuration way though I was never able to solve.
Previous Topic:Maven view in eclipse
Next Topic:How to install Maven-Nar plugin?
Goto Forum:
  


Current Time: Fri Apr 26 01:11:27 GMT 2024

Powered by FUDForum. Page generated in 0.04068 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top