我从Maven开始,在一本书之后。我在 Ubuntu 上使用 3.2.1。我已经运行了以下命令:
mvn archetype:generate -DgroupId=org.sonatype.mavenbook.ch03 -DartifactId=simple -DpackageName=org.sonatype.mavenbook
MVN 安装
然后我得到一个豆茎错误。从本质上讲,我没有亚马逊凭据。我了解围绕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
你可能使用了elasticbeanstalk
原型。一个简短的原因(因为您似乎只是在学习Maven)是编辑您的pom并删除br.com.ingenieux
groupId的<plugin/>
部分。
希望对你有帮助
对于那些关心为什么失败的小细节的人
自 1.3.x 版(几周前)以来,我们放弃了 aws.accessKey
和 aws.secretKey
的使用。事实上,警告已经存在了两年多:)
原因:github 上的许多项目都泄露了 AWS 密钥
相反,将它们设置为环境变量 (AWS_ACCESS_KEY_ID) 和 (AWS_SECRET_ACCESS_KEY) 或使用加密 - 有关概述,请参阅此文档