How to build an extension that depends on an addon

[Owen Mooney]

Hi all,

Since the spider component has been changed to work as an addon, what is the suggested way to build an extension that needs to interact with it?

I've hacked together a solution where I copy the spider addon .zap file into my project directory, and that seems to work fine, but is there a more idiomatic way to do this? I noticed that in the extensions repo, the spider addon has the property zap.maven.publish set to true, but there is no corresponding package in the maven repos, is there a plan to publish it at some stage?

Cheers,

Owen M.

[thc...@gmail.com]

Hi.

Currently the add-ons are only released to Maven Central if and when needed.

We'll make sure the Spider add-on is available soon.


Just curiosity:
- How are you building your add-on?
- Could you provide details about your use case?


Best regards.

[Owen Mooney]

Hi,

Great to hear that the Spider add-on will be available on Maven, I'll keep an eye out.

We're building the addon based on the old simpleextension example (I think that's what it was called). We just updated the gradle build file to suit.

The functionality it includes is a bunch of API endpoints to retrieve large volumes of data in a more efficient way, mainly sitemap/crawl data across multiple scans (hence the dependence on the spider component/addon)

Cheers,

Owen M.

[thc...@gmail.com]

Thank you for the answers!


The Spider is now available with the following coordinates:
org.zaproxy.addon:spider:0.6.0

Let us know if it works fine for you (it's possible we might need to
release other add-ons that the Spider depends on…).

Bet regards.