Maven安装beanstalk错误

时间:2014-02-25 16:14:35

标签: maven

我开始跟Maven一起读完一本书。我在Ubuntu上使用3.2.1。我运行了以下命令:

mvn archetype:generate -DgroupId = org.sonatype.mavenbook.ch03 -DartifactId = simple -DpackageName = org.sonatype.mavenbook

mvn install

然后我得到一个beanstalk错误。基本上,我没有亚马逊凭证。我理解围绕Maven的概念。如果我不想使用亚马逊服务怎么办?这真的有必要吗? [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for org.sonatype.mavenbook.ch03:simple:war:1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 143, column 12 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO]
[INFO] ------------------------------------------------------------------------ [INFO] Building simple 1.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- beanstalk-maven-plugin:0.2.8:expose-security-credentials (expose-security-credentials) @ simple --- [WARNING] FAILURE java.lang.IllegalArgumentException: Settings for serverId ('aws.amazon.com') not found. See http://beanstalker.ingenieux.com.br/beanstalk-maven-plugin/security.html for more information

1 个答案:

答案 0 :(得分:0)

您可能使用了elasticbeanstalk原型。一个简短的原因(因为您似乎只是在学习Maven)是编辑您的pom并删除<plugin/> groupId的br.com.ingenieux部分。

希望有所帮助

对于那些关心为什么失败的小细节的人

自1.3.x版(几周前)发布以来,我们放弃了aws.accessKeyaws.secretKey的使用。这些警告事实上是两年多了:)

原因:github上的许多项目泄漏了AWS Keys

相反,将它们设置为环境变量(AWS_ACCESS_KEY_ID)和(AWS_SECRET_ACCESS_KEY)或使用加密 - 请参阅this doc以获取概述