Some further digging into the issue and found that the current code builds
successfully with maven 3.5.2 without the need to specify the relativePath and
it breaks on 3.5.3 and requires the relativePath. Seems maven has some changes
to how it searches parents.
Nixon pointed out that there is another thread in the user mailing list on the
same topic, which I missed previously. Sorry for the duplication.
发件人: Nixon Rodrigues <nixon.rodrig...@freestoneinfotech.com>
发送时间: Monday, April 9, 2018 6:26:38 PM
主题: Re: Issues building Atlas
Can you over below suggestion from Madhan on this issue?
*Ashutosh �C this might require addition of ‘relativePath’ in
tools/atlas-migration-exporter/pom.xml, as shown below. Can you please
review and update?*
On Mon, Apr 9, 2018 at 3:47 PM, Justin Shen <justins...@outlook.com> wrote:
> I am trying to follow the “Build & Install” guide and encountered the
> following error when building the project:
> Non-resolvable parent POM for org.apache.atlas:atlas-
> migration-exporter:[unknown-version]: Could not find artifact
> org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM @ line 24, column 13 ->
> [Help 2]
> Modify the POM of atlas_:atlas-migration-exporter to add a relativePath
> seems solve the problem:
> Is this required? Should the code be changed? Or is there any settings.xml
> that I should use?
> Thx, -Justin