Closed aoli-al closed 1 year ago
Thank you for the issue report. We did not uploaded the parent POM for our previous releases, because Maven doesn't need it. In pure Maven, you can reference the individual modules (soot-infoflow
, soot-infoflow-android
, etc.). If Gradle needs the parent POM, that's a perfectly valid argument to change this policy.
We will deploy the parent POM in future releases. I have changed the build and release pipeline. However, since this required changes, we can't simple deploy it for the old version without nasty tricks. We can't easily run the pipeline on old tags, merge in the changes I have done to the POM, and then get this published on Maven Central somehow. We will just run the adapted pipeline for the next release, and then you'll have a parent POM.
Thanks for the quick fix!
Hi developers,
I'm trying to use FlowDroid in my gradle project:
Unfortunately, gradle cannot resolve soot-infoflow properly:
The error is that gradle cannot find soot-infoflow-parent, which is referenced in https://github.com/secure-software-engineering/FlowDroid/blob/fe240f90debf5836fba484c5f618b2c3b26a4418/soot-infoflow/pom.xml#L13 but not published in maven central: https://repo.maven.apache.org/maven2/de/fraunhofer/sit/sse/flowdroid/
Note that I'm able to build and compile my project if I download FlowDroid and install the packages in my local repository. Could you please also upload the missing package to maven central?
Thanks