maven 配置问题

wisoper 2011-01-19 10:37:52
在eclipse 配置了maven 编译项目时提示一下错误


[INFO] BUILD FAILURE

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

[INFO] Total time: 0.093s

[INFO] Finished at: Wed Jan 19 10:36:06 CST 2011

[INFO] Final Memory: 1M/4M

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

[ERROR] No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]

org.apache.maven.lifecycle.NoGoalSpecifiedException: No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy.

	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:104)

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

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

	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:451)

	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:188)

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

	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] Re-run Maven using the -X switch to enable full debug logging.

[ERROR] 

[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoGoalSpecifiedException


查过教程由说是http://wenku.baidu.com/view/5934b80c844769eae009eded.html
本地仓库位置问题。说让改settings。xml文件。但具体怎么改还不太确定。希望谁有例子发一下。（我就写了一个简单的hello world 程序。谢谢

现在有些乱。如果问题信息不详细我再补充。
...全文
7601 11 打赏 收藏 转发到动态 举报
AI 作业
写回复
用AI写文章
11 条回复
切换为时间正序
请发表友善的回复…
发表回复
wisoper 2011-01-25
  • 打赏
  • 举报
 回复
执行mvn clean test 命令时提示有一个错误
wisoper 2011-01-25
  • 打赏
  • 举报
 回复 


build.plugins.plugin.version' for org.apache.maven.plugins:maven-resources-plugin is missing

现在提示maven-resources-plugin 这个插件没找到，项目构建不成功。


     <plugin>  

       <groupId>org.apache.maven.plugins</groupId>  

       <artifactId>maven-resources-plugin</artifactId>  

            <configuration>  

                 <encoding>UTF-8</encoding>  

             </configuration>  

       </plugin>

这是POM里添加的代码。
javasishen 2011-01-21
  • 打赏
  • 举报
 回复
怎么 交流？。。。你QQ？
wisoper 2011-01-21
  • 打赏
  • 举报
 回复
[Quote=引用 7 楼 javasishen 的回复:]
引用 5 楼 wisoper 的回复:
引用 1 楼 nuoboxgx 的回复:
No goals have been specified for this build.

你执行了啥命令?

好像是 goal 错误

试下: mvn clean test

maven不需要配置本地库地址 默认是在用户名下/.m2/repository下面的.

如果你环境变量和插件安装正……
[/Quote]

我正在解决。楼上方便交流下不
javasishen 2011-01-20
  • 打赏
  • 举报
 回复
[Quote=引用 5 楼 wisoper 的回复:]
引用 1 楼 nuoboxgx 的回复:
No goals have been specified for this build.

你执行了啥命令?

好像是 goal 错误

试下: mvn clean test

maven不需要配置本地库地址 默认是在用户名下/.m2/repository下面的.

如果你环境变量和插件安装正确的话。写完pom.xml直接安装就行了。……
[/Quote]
肯定要先装一个MAVEN插件,然后安装一个本地MAVEN客户端,最后有一个MAVEN服务器,再配置一下setting.xml配置文件,就可以正确的从MAVEN服务器下载依赖和编译项目了.
huntor 2011-01-19
  • 打赏
  • 举报
 回复
You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy.
huntor 2011-01-19
  • 打赏
  • 举报
 回复
clean
install
compile
integration-test
netbeans-freeform:generate-netbeans-project
package
process-resources
deploy
process-sources
site
test
eclipse:add-maven-repo
test-compile
eclipse:clean tomcat:deploy
eclipse:eclipse tomcat:run
generate-resources tomcat:run-war
generate-sources validate
idea:idea verify
ashutc 2011-01-19
  • 打赏
  • 举报
 回复
maven不需要配置本地库地址 默认是在用户名下/.m2/repository下面的.

如果你环境变量和插件安装正确的话。写完pom.xml直接安装就行了。

这个错误没遇到过。呵呵
nuoboxgx 2011-01-19
  • 打赏
  • 举报
 回复
No goals have been specified for this build.

你执行了啥命令?

好像是 goal 错误

试下: mvn clean test
huntor 2011-01-19
  • 打赏
  • 举报
 回复
$HOME/.m2/settings.xml
<?xml version="1.0" encoding="UTF-8"?>



<!--

Licensed to the Apache Software Foundation (ASF) under one

or more contributor license agreements.	 See the NOTICE file

distributed with this work for additional information

regarding copyright ownership.	The ASF licenses this file

to you under the Apache License, Version 2.0 (the

"License"); you may not use this file except in compliance

with the License.  You may obtain a copy of the License at



http://www.apache.org/licenses/LICENSE-2.0



Unless required by applicable law or agreed to in writing,

software distributed under the License is distributed on an

"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY

KIND, either express or implied.  See the License for the

specific language governing permissions and limitations

under the License.

-->



<!--

| This is the configuration file for Maven. It can be specified at two levels:

|

|  1. User Level. This settings.xml file provides configuration for a single user,

|				  and is normally provided in ${user.home}/.m2/settings.xml.

|

|				  NOTE: This location can be overridden with the CLI option:

|

|				  -s /path/to/user/settings.xml

|

|  2. Global Level. This settings.xml file provides configuration for all Maven

|				  users on a machine (assuming they're all using the same Maven

|				  installation). It's normally provided in

|				  ${maven.home}/conf/settings.xml.

|

|				  NOTE: This location can be overridden with the CLI option:

|

|				  -gs /path/to/global/settings.xml

|

| The sections in this sample file are intended to give you a running start at

| getting the most out of your Maven installation. Where appropriate, the default

| values (values used when the setting is not specified) are provided.

|

|-->

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"

		  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

		  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">

  <!-- localRepository

	   | The path to the local repository maven will use to store artifacts.

	   |

	   | Default: ~/.m2/repository

	   <localRepository>/path/to/local/repo</localRepository>

  -->



  <!-- interactiveMode

	   | This will determine whether maven prompts you when it needs input. If set to false,

	   | maven will use a sensible default value, perhaps based on some other setting, for

	   | the parameter in question.

	   |

	   | Default: true

	   <interactiveMode>true</interactiveMode>

  -->



  <!-- offline

	   | Determines whether maven should attempt to connect to the network when executing a build.

	   | This will have an effect on artifact downloads, artifact deployment, and others.

	   |

	   | Default: false

	   <offline>false</offline>

  -->



  <!-- pluginGroups

	   | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.

	   | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers

	   | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.

	   |-->

  <pluginGroups>

	<!-- pluginGroup

		 | Specifies a further group identifier to use for plugin lookup.

		 <pluginGroup>com.your.plugins</pluginGroup>

	-->

  </pluginGroups>



  <!-- proxies

	   | This is a list of proxies which can be used on this machine to connect to the network.

	   | Unless otherwise specified (by system property or command-line switch), the first proxy

	   | specification in this list marked as active will be used.

	   |-->

  <proxies>

	<!-- proxy

		 | Specification for one proxy, to be used in connecting to the network.

		 |

		 <proxy>

		 <id>optional</id>

		 <active>true</active>

		 <protocol>http</protocol>

		 <username>proxyuser</username>

		 <password>proxypass</password>

		 <host>proxy.host.net</host>

		 <port>80</port>

		 <nonProxyHosts>local.net|some.host.com</nonProxyHosts>

		 </proxy>

	-->

  </proxies>



  <!-- servers

	   | This is a list of authentication profiles, keyed by the server-id used within the system.

	   | Authentication profiles can be used whenever maven must make a connection to a remote server.

	   |-->

  <servers>

	<!-- server

		 | Specifies the authentication information to use when connecting to a particular server, identified by

		 | a unique name within the system (referred to by the 'id' attribute below).

		 |

		 | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are

		 |		 used together.

		 |

		 <server>

		 <id>deploymentRepo</id>

		 <username>repouser</username>

		 <password>repopwd</password>

		 </server>

	-->



	<!-- Another sample, using keys to authenticate.

		 <server>

		 <id>siteServer</id>

		 <privateKey>/path/to/private/key</privateKey>

		 <passphrase>optional; leave empty if not used.</passphrase>

		 </server>

	-->

  </servers>



  <!-- mirrors

	   | This is a list of mirrors to be used in downloading artifacts from remote repositories.

	   |

	   | It works like this: a POM may declare a repository to use in resolving certain artifacts.

	   | However, this repository may have problems with heavy traffic at times, so people have mirrored

	   | it to several places.

	   |

	   | That repository definition will have a unique id, so we can create a mirror reference for that

	   | repository, to be used as an alternate download site. The mirror site will be the preferred

	   | server for that repository.

	   |-->

  <mirrors>

	<mirror>

	  <id>uk</id>

	  <mirrorOf>central</mirrorOf>

	  <url>http://uk.maven.org/maven2/</url>

	</mirror>

  </mirrors>



  <!-- profiles

	   | This is a list of profiles which can be activated in a variety of ways, and which can modify

	   | the build process. Profiles provided in the settings.xml are intended to provide local machine-

	   | specific paths and repository locations which allow the build to work in the local environment.

	   |

	   | For example, if you have an integration testing plugin - like cactus - that needs to know where

	   | your Tomcat instance is installed, you can provide a variable here such that the variable is

	   | dereferenced during the build process to configure the cactus plugin.

	   |

	   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles

	   | section of this document (settings.xml) - will be discussed later. Another way essentially

	   | relies on the detection of a system property, either matching a particular value for the property,

	   | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a

	   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.

	   | Finally, the list of active profiles can be specified directly from the command line.

	   |

	   | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact

	   |	   repositories, plugin repositories, and free-form properties to be used as configuration

	   |	   variables for plugins in the POM.

	   |

	   |-->

  <profiles>

	<profile>

	  <id>jboss-public-repository</id>

	  <repositories>

		<repository>

		  <id>jboss-public-repository-group</id>

		  <name>JBoss Public Maven Repository Group</name>

		  <url>https://repository.jboss.org/nexus/content/groups/public-jboss/</url>

		  <layout>default</layout>

		  <releases>

			<enabled>true</enabled>

			<updatePolicy>never</updatePolicy>

		  </releases>

		  <snapshots>

			<enabled>true</enabled>

			<updatePolicy>never</updatePolicy>

		  </snapshots>

		</repository>

	  </repositories>

	  <pluginRepositories>

		<pluginRepository>

		  <id>jboss-public-repository-group</id>

		  <name>JBoss Public Maven Repository Group</name>

		  <url>https://repository.jboss.org/nexus/content/groups/public-jboss/</url>

		  <layout>default</layout>

		  <releases>

			<enabled>true</enabled>

			<updatePolicy>never</updatePolicy>

		  </releases>

		  <snapshots>

			<enabled>true</enabled>

			<updatePolicy>never</updatePolicy>

		  </snapshots>

		</pluginRepository>

	  </pluginRepositories>

	</profile>

  </profiles>

  <activeProfiles>

	<activeProfile>jboss-public-repository</activeProfile>

  </activeProfiles>

</settings>
wisoper 2011-01-19
  • 打赏
  • 举报
 回复
[Quote=引用 1 楼 nuoboxgx 的回复:]
No goals have been specified for this build.

你执行了啥命令?

好像是 goal 错误

试下: mvn clean test

maven不需要配置本地库地址 默认是在用户名下/.m2/repository下面的.

如果你环境变量和插件安装正确的话。写完pom.xml直接安装就行了。

这个错误没遇到过。呵呵
[/Quote]

mvn clean test测试成功了，但还不知道是为什么

maven 的插件还没有安装，在网上找到也有类似说明那个，但是配置方法还不确定
apache-maven-3.1.1
maven本地资源包，下载后直接解压即可使用。 在系统环境变量中配置MAVEN_HOME，路径为maven根目录。 再path下加入bin目录路径，cmd命令窗口中输入mvn -version。 输出版本信息，即配置完成。
一次性解决：IDEA的 maven 配置问题，在新项目中不再担心 maven 的配置问题
Ⅰ、问题描述： 1、是否安装新的 maven 版本： 现在新出的IDEA很可能是maven已经集成了(即：自己自带的有maven环境)，所以在确定是否安装其它版本的 maven 之前，最好确定一下，是否是真的需要安装其它版本的 maven 环境； 2、确定要安装新版本的 maven 环境： A、安装地址可参考官网： B、若参考官网麻烦的话，也可自提： Ⅱ、maven 在电脑上的安装流程： 1、首先拿到 maven 的安装包，解压，傻瓜式安装到想要的路径下； 2、 3、 4、 Ⅲ、 Ⅳ、 Ⅴ ...
关于Maven配置出现的问题
关于Maven配置出现的问题及解决方案。 问题一: 乱码与jdk版本问题 解决方案:在settings.xml配置文件内设置全局jdk和编码类型 问题二: Test单元测试打印乱码问题 解决方案:在设置内设置编码格式 问题三:新建项目需要重新设置maven问题 解决方案:在设置内修改默认目录为maven目录 问题四:idea无法识别本地仓库 注意本地仓库的存放位置
【超全详解】Maven工程配置与常见问题解决指南
Maven工程配置和常见问题的解决指南
idea配置maven步骤及常见问题
将maven下的conf/settings.xml 路径放入，记得勾选后面的 Override否则无法重写目录位置。然后，第一次生成maven项目的话，会在本地仓库中下载依赖，可能大概需要两分钟左右。接下来，我们开始正式对 idea 中进行 maven的配置！现在基本的配置已经改好啦，接下来在idea中更改配置。,一开始选择的是3.8.7的，然后版本不匹配。每次创建idea,需要重新配置maven的问题的解决步骤.最近换了个电脑，重新配置环境中QAQ
Java SE

62,634

社区成员

307,269

社区内容

发帖
与我相关
我的任务
社区描述
Java 2 Standard Edition
社区管理员
  • Java SE
加入社区
  • 近7日
  • 近30日
  • 至今

加载中

查看更多榜单
社区公告
暂无公告

试试用AI创作助手写篇文章吧

+ 用AI写文章