search

protofire / AIP-011-Ownable

0 stars 2 forks source link

Build warnings -- dependencies #2

Open fulldecent opened 5 years ago

fulldecent commented 5 years ago

I am getting the following warnings on build.

mvn aion4j:init

[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for com.altoros.aion:aion-ownable:jar:1.0-SNAPSHOT
[WARNING] 'dependencies.dependency.systemPath' for org.aion:avm-api:jar refers to a non-existing file /Users/williamentriken/Desktop/tmp5/AIP-011-Ownable/lib/org-aion-avm-api.jar @ line 28, column 25
[WARNING] 'dependencies.dependency.systemPath' for org.aion:avm-userlib:jar refers to a non-existing file /Users/williamentriken/Desktop/tmp5/AIP-011-Ownable/lib/org-aion-avm-userlib.jar @ line 35, column 25
[WARNING] 'dependencies.dependency.systemPath' for org.aion:avm-tooling:jar refers to a non-existing file /Users/williamentriken/Desktop/tmp5/AIP-011-Ownable/lib/org-aion-avm-tooling.jar @ line 42, column 25
[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]

To ensure documentation is correct and builds are reproducible, please use Travis CI for builds.

xiwix commented 5 years ago

This warning tells that project is not initialized yet. Message is gone after first run of mvn aion4j:init or mvn initialize command.

fulldecent commented 5 years ago

Deleted folder, recloned and ran mvn initialize. Receiving these warnings:

[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for com.altoros.aion:aion-ownable:jar:1.0-SNAPSHOT
[WARNING] 'dependencies.dependency.systemPath' for org.aion:avm-api:jar refers to a non-existing file /Users/williamentriken/Desktop/tmp5/AIP-011-Ownable/lib/org-aion-avm-api.jar @ line 28, column 25
[WARNING] 'dependencies.dependency.systemPath' for org.aion:avm-userlib:jar refers to a non-existing file /Users/williamentriken/Desktop/tmp5/AIP-011-Ownable/lib/org-aion-avm-userlib.jar @ line 35, column 25
[WARNING] 'dependencies.dependency.systemPath' for org.aion:avm-tooling:jar refers to a non-existing file /Users/williamentriken/Desktop/tmp5/AIP-011-Ownable/lib/org-aion-avm-tooling.jar @ line 42, column 25
[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]

Is there another command would should be run beforehand so that this step can run the first time without warnings?

If not, can this issue please be documented and reported upstream?

xiwix commented 5 years ago

There is no way to mute this warning for first run only. But you can try this approach: https://stackoverflow.com/questions/32682374/how-to-disable-specific-warning-during-maven-execution

fulldecent commented 5 years ago

Thank you. Adding an additional step may be best practice for deploying dependencies (e.g. using Nexus) I am investigating.

fulldecent commented 5 years ago

I'm not exactly sure what causes the problem here, but we are experiencing perfectly clean builds here https://travis-ci.com/fulldecent/aion-aip010

If testing is set up here and Travis CI is enabled and passing I might be able to check out if I can fix it here too.