Fix bad java import practices #452

	name: Java CI

	# Trigger workflow on push or pull_request
	# Note - the first pull_request from a forked repo will need to be given approval to run
	on: [push, pull_request]

	jobs:
	build:
	runs-on: ubuntu-latest

	steps:
	- uses: actions/checkout@v2
	- name: Set up JDK
	uses: actions/setup-java@v2
	with:
	java-version: '17'
	distribution: 'adopt'

	- name: Cache Maven Repo
	uses: actions/cache@v2
	with:
	path: ~/.m2
	key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }}
	restore-keys: ${{ runner.os }}-m2

	- name: Set up test browser
	uses: browser-actions/setup-firefox@latest
	- name: Build Test and Verify
	run: mvn -B -U clean install -Dmaven.javadoc.skip=true -Dpmd.verbose=false -DskipOptionalQA=true -PskipCoreOptionalTests
	env:
	MOZ_HEADLESS: 1
	# Why comment these out? Browsers are now so standard compliant issues are much rarer.
	# The saucelabs tests are relatively slow and flaky.
	# SAUCE_USERNAME: ${{ secrets.SAUCE_USERNAME }}
	# SAUCE_ACCESS_KEY: ${{ secrets.SAUCE_ACCESS_KEY }}

	- name: SonarCloud Scan
	run: \|
	if ["$SONAR_TOKEN" == ""]; then
	echo "Sonar secure variables NOT available"
	else
	echo "Sonar secure variables ARE available"
	mvn -B sonar:sonar -Dsonar.projectKey="bordertech-wcomponents" -Dsonar.organization="bordertech-github" -Dsonar.host.url="https://sonarcloud.io"
	fi
	env:
	GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
	SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}

Provide feedback