security/zaproxy2.17.0_4

security/zaproxy: Fix JAVA_VERSION to 17 and 20

- Bump PORTREVISION

PR:		294176
Reported by:	ronald

security/zaproxy: Update JAVA_VERSION to 17+

- JAVA 22 will be removed soon so 17+ shows us the current java versions
  supported by zaproxy
- Bump PORTREVISION

PR:		294176
Reported by:	ronald

*/*: bump portrevision after java_default=25 update

Included all ports that have USES=java.

PR:	293559

*/*: bump portrevision after java_default=21 update

PR:	272855

security/zaproxy: Update to 2.17.0

ChangeLog at:   https://www.zaproxy.org/docs/desktop/releases/2.17.0/

security/zaproxy: Update to 2.16.1

ChangeLoag at:  https://www.zaproxy.org/docs/desktop/releases/2.16.1/

security/zaproxy: Fix build

- Latest version of gradle break security/zaproxy. Now it depends of
  devel/gradle8
- Update JAVA to 22
- Re-generate cache files
- Bump PORTREVISION

Reported by:	pkg-fallout

security/zaproxy: Update to 2.16.0

- Update java dependecy to 17
- Add pkg-message with some entries about selenium, web browsers and
  py-zaproxy

ChangeLog at:	https://www.zaproxy.org/docs/desktop/releases/2.16.0/

Mk/**java.mk: Convert bsd.java.mk to USES

The following features have been added or changed:
- Instead of USE_JAVA use USES=java. This defaults to
  USES=java:build,run if NO_BUILD is undefined. Else it defaults to
  USES=java:run
- Instead of USE_ANT=yes use USES=java:ant which also implies
  USES=java:build
- Instead of JAVA_BUILD=yes use USES=java:build. Does not imply run or
  extract
- Instead of JAVA_EXTRACT=yes use USES=java:extract does not imply
  build or run
- Instead of JAVA_RUN=yes use USES=java:run does not imply extract or
  build
- Instead of USE_JAVA=<version> use USES=java and JAVA_VERSION=<version>

Approved by: mat (portmgr), glewis
Differential Revision:  https://reviews.freebsd.org/D48201

security/zaproxy: Update cache files because gradle was updated

- Fix open options menu
PR:		276730
Reported by:	salvadore

security/zaproxy: Update to 2.14.0

ChangeLog at:	https://www.zaproxy.org/docs/desktop/releases/2.14.0/

security/zaproxy: Fix issues with latest version of gradle

- Re-generate plugins and deps package with latest version of gradle
- Fix issues in zap.sh [1]
- Bump PORTREVISION
Reported by:	Mateusz Kocielski <shm _at_ digitalsun.pl> [1]

security/zaproxy: Update to 2.13.0

ChangeLog at:	https://www.zaproxy.org/docs/desktop/releases/2.13.0/

security/zaproxy: Fix build after of gradle update to 8.1

- Bump PORTREVISION
Reported by:	pkg-fallout

security/zaproxy: Fix build after of gradle update to 7.6

- Fix  way to generate plugins distfile
- Bump PORTREVISION

security/zaproxy: update to 2.12.0

ChangeLog at:	https://www.zaproxy.org/docs/desktop/releases/2.12.0/

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.

There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.

The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.

Approved by:		portmgr (tcberner)

security/zaproxy: mark BROKEN

* What went wrong:
Plugin [id: 'org.gradle.kotlin.kotlin-dsl', version: '2.3.3'] was not found in any of the following sources:

- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Plugin Repositories (could not resolve plugin artifact 'org.gradle.kotlin.kotlin-dsl:org.gradle.kotlin.kotlin-dsl.gradle.plugin:2.3.3')
  Searched in the following repositories:
    Gradle Central Plugin Repository

Approved by:	portmgr blanket
Reported by:	pkg-fallout

security/zaproxy: update to 2.11.1

ChangeLog at:	https://www.zaproxy.org/docs/desktop/releases/2.11.1/

security/zaproxy: Fix typo

Reported by:	olgeni

security/zaproxy: New port: The OWASP zed attack proxy

The OWASP Zed Attack Proxy (ZAP) is one of the world’s most popular fr
security tools and is actively maintained by a dedicated international team
of volunteers. It can help you automatically find security vulnerabilities in
your web applications while you are developing and testing your applications.
It's also a great tool for experienced pentesters to use for manual security
testing.

WWW: https://www.zaproxy.org/