devel/sonar-scanner-cli: Update to 6.2.1.

devel/sonar-scanner-cli: Update to 6.2.0.

devel/sonar-scanner-cli: Update to 6.1.0.

devel/sonar-scanner-cli: Update to 6.0.0.

devel/sonar-scanner-cli: update to 5.0.1

nodejs: Bump PORTREVISION for dependency change

USES=nodejs defaults to www/node20 now.

devel/sonar-scanner-cli: Switch to openjdk 17+

Framework: Rewrite nodejs.mk and reorganize www/{node,npm,yarn}

The current USES=nodejs has the following issues:
- www/node is not the default version while www/node16 is.
- It also means inconsistent naming of node ports.
- www/npm duplicates with www/npm-node16.
- www/yarn duplicates with www/yarn-node16.

The notable changes are introduced to fix the above issues:
- Rewrite Mk/Uses/nodejs.mk.
- Add new LTS version of nodejs (www/noe18).
- Add new current version of nodejs (www/node19).
- Change default nodejs version from 16 to 18 (latest LTS).
- Use consistent naming for all supported node versions.
- Convert www/node, www/npm and www/yarn to meta ports.

After this commit:
- All supported node versions are named as node{14,16,18,19}
- www/node is a meta port which depends on the default version (e.g. www/node18)
- www/npm is a meta port which depends on the default version (e.g.
www/npm-node18)
- www/yarn is a meta port which depends on the default version (e.g.
www/yarn-node18)
- Bump PORTREVISION of dependent ports for dependency change (from www/node16 to
www/node18)

Discussed with:	jrm, otis, pizzamig

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.

*/*: use new nodejs USES flag

Simply define which nodejs version is required using the nodejs USES flag.

PR:                     259783
Differential Revision:	https://reviews.freebsd.org/D32790

devel/sonar-scanner-cli: fix CPE product

One more small cleanup, forgotten yesterday.
Reported by:	lwhsu

all: Remove all other $FreeBSD keywords.

Remove # $FreeBSD$ from Makefiles.

Update to 4.4.0.2170.

Update sonarqube ports to the most revent version:
 - sonarqube-community: 8.2
 - sonarqube-ant-task: 2.7.0.1612
 - sonar-scanner-cli: 4.3.0.2102

Take over as maintainer.

Approved by:	maintainer

Clean up after java/openjdk6 and java/openjdk6-jre removal

java/openjdk6 support was removed from Mk/bsd.java.mk (r512662) and
java/openjdk6 and java/openjdk6-jre were removed from the ports tree
(r512663).  Now this patch completely removes remaining stuff from the
ports tree.

PR:			241953 (exp-run)
Reviewed by:		glewis
Approved by:		portmgr (antoine)
Differential Revision:	https://reviews.freebsd.org/D22342

Mark a few ports BROKEN, unfetchable

Convert to UCL & cleanup pkg-message (categories d)

devel/sonar-scanner-cli: Fix build as non-root

PR:             220115
Submitted by:   Du<C5><A1>an Vejnovi<C4><8D> <freebsd@dussan.org> (maintainer)
Approved by:    mat (co-mentor)
Differential Revision:  https://reviews.freebsd.org/D11438

Add sonar-scanner-cli

The SonarQube Scanner is recommended as the default launcher to analyze a
project with SonarQube. The SonarQube Scanner allows you to perform source code
analyzes without using tools such as Ant or Maven. The SonarQube platform is an
open source quality management platform, dedicated to continuously analyzing
and measuring the technical quality of source code, from project portfolio down
to the method level. With the SonarQube Scanner, and also a tool like Jenkins,
everyone can analyze all kinds of languages, not just Java.

WWW:	http://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner
PR:	208667