Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't build the latest FlowDroid 2.6 SNAPSHOT #66

Closed
zhanghan177 opened this issue Sep 6, 2018 · 4 comments
Closed

Can't build the latest FlowDroid 2.6 SNAPSHOT #66

zhanghan177 opened this issue Sep 6, 2018 · 4 comments

Comments

@zhanghan177
Copy link
Contributor

I tried to build by mvn install the latest 2.6 SNAPSHOT from both develop and master branches. They both failed.

The error message is

[INFO] Reactor Summary:
[INFO]
[INFO] soot-infoflow ...................................... FAILURE [ 20.968 s]
[INFO] soot-infoflow-android .............................. SKIPPED
[INFO] StubDroid .......................................... SKIPPED
[INFO] FlowDroid Command Line Util ........................ SKIPPED
[INFO] FlowDroid Parent Module ............................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 21.184 s
[INFO] Finished at: 2018-09-06T22:02:18Z
[INFO] Final Memory: 25M/267M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project soot-infoflow: Compilation failure
[ERROR] /home/hanzhang/FlowDroid/soot-infoflow/src/soot/jimple/infoflow/solver/fastSolver/InfoflowSolver.java:[117,37] cannot find symbol
[ERROR] symbol: method invalidate()
[ERROR] location: variable ffCache of type heros.FlowFunctionCache<N,D,soot.SootMethod>
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

It looks like @StevenArzt added an invalidate() method to Heros (soot-oss/heros@c740e6b) fairly recently (15 days ago).

During mvn install, it tries to retrieve Heros-1.0.1-SNAPSHOT from soot-release (https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/heros/heros/1.0.1-SNAPSHOT) and soot-snapshot (https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/heros/heros/1.0.1-SNAPSHOT).

From soot-snapshot, the latest Heros-1.0.1-SNAPSHOT is from April (https://soot-build.cs.uni-paderborn.de/nexus/#browse/browse/components:soot-snapshot:36e3dec8de528c9b26d8dfec9104f3e7), which doesn't reflect the change. As this log message shows:

Downloading from soot-snapshot: https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/heros/heros/1.0.1-SNAPSHOT/heros-1.0.1-20180418.125229-1.pom

From soot-release, I received the error message as

[WARNING] Could not transfer metadata heros:heros:1.0.1-SNAPSHOT/maven-metadata.xml from/to soot-release (https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/): Failed to transfer file: https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/heros/heros/1.0.1-SNAPSHOT/maven-metadata.xml. Return code is: 400 , ReasonPhrase:Repository version policy: RELEASE does not allow metadata in path: heros/heros/1.0.1-SNAPSHOT/maven-metadata.xml.

Would there be any suggestions on how to fix this error?

@StevenArzt
Copy link
Member

Apparently, the build server for Heros is broken. The best possibility for a quick fix would be to check out Heros from git and build it locally. Using "mvn install", you should get a copy in your local Maven cache and there should not be any need for Maven to download it anymore.

@mbenz89 Can you please have a look whether we have a working build system for Heros at the moment and whether the Heros artifacts are correctly uploaded to the Nexus repository?

@mbenz89
Copy link
Member

mbenz89 commented Sep 7, 2018

Everything should be up and working again. Thanks for reporting!

@StevenArzt
Copy link
Member

Thanks for the fix, Manuel!

@zhanghan177
Copy link
Contributor Author

Thanks the issue is now fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants