前言

執行Maven → "son-project-1" → Lifecycle → package,
總會有警告資訊,

'dependencies.dependency.version' for org.testng:testng:jar is either LATEST or RELEASE (both of them are being deprecated)

找到提示的專案的pom.xml,

<dependency>
	<groupId>org.testng</groupId>
	<artifactId>testng</artifactId>
	<version>RELEASE</version>
	<scope>test</scope>
</dependency>

 

找到原因

搜尋相關錯誤資訊,找到Stackoverflow上關於此的一些資訊↓

We had a similar situation: We have parent poms that are used by hundreds of projects by dozens of developers. In Ant, we had an approach similar to the RELEASE one, but now we have explicit version numbers.

Every developer needs to run versions:update-parent to get the new version, otherwise he/she stays with the old one. The disadvantage is that several versions of the parent pom are in use, the advantage is build stability because the "parent pom people" cannot destroy the builds by a wrong configuration that is drawn implicitly.

In your case, I would advice you to think whether you really need everybody to use the same version. If you really need this, you probably have to use version ranges as [1.0.0,)

根據我的英語水平 + 谷歌翻譯後,
我理解的就是不能直接指定版本為"RELEASE",
而應該指定一個確定的版本號 . . .

解決方案

開啟該專案的pom.xml,將滑鼠移至RELEASE上,
等待顯示該釋出版本的具體資訊,
( 我這裡的釋出版本其實就是7.4.0 )

將RELEASE修改為7.4.0

<dependency>
	<groupId>org.testng</groupId>
	<artifactId>testng</artifactId>
	<version>7.4.0</version>
	<scope>test</scope>
</dependency>

再次執行Maven → "son-project-1" → Lifecycle → package ,
不報警告了 . . .

完美؏؏☝ᖗ乛◡乛ᖘ☝؏؏

摘抄文件

• [X] Stackoverflow.Version RELEASE or LATEST for parent pom