Blank eclipse project (WTP) puts runtime scoped libraries in wrong directory.

[yoshikawaa]

Description

terasoluna-gfw-web-blank/unmaven-project.sh

Lines 26 to 37 in a70e632

	##-------------------------
	## download jars
	##-------------------------
	download_jars() {
	rm -rf $WEBINFLIB $LIBSRC $TESTLIB
	mvn dependency:copy-dependencies -DoutputDirectory=$WEBINFLIB -DincludeScope=compile -DexcludeScope=provided -DexcludeTypes=pom
	mvn dependency:copy-dependencies -DoutputDirectory=$LIBSRC -DincludeScope=compile -DexcludeScope=provided -DexcludeTypes=pom -Dclassifier=sources
	mvn dependency:copy-dependencies -DoutputDirectory=$TESTLIB -DexcludeScope=compile -DexcludeTypes=pom
	mvn dependency:copy-dependencies -DoutputDirectory=$LIBSRC -DexcludeScope=compile -DexcludeTypes=pom -Dclassifier=sources
	echo $? > /dev/null
	}

WEB-INF/lib, libsrc directory must contain compile and runtime scoped jars, but does not actually include runtime scoped jars.
Conversely, the testlib directory should not contain compile and runtime scoped jars, but actually contains runtime scoped jars.

Note:
This issue is not affect multi-module projects, because it is not provide the Blank eclipse project (WTP).

Possible Solution

Please write ideas or candidates of solutions for the problem if you have.
If it is an example, please enter a description such as "For example".

Affect versions

Version in which the problem occurs. Current version if not known.
If there is a feature suggestion, please delete it.

• 5.5.1.RELEASE and earlier all versions.

Fix repositories

Repositories to fix with this issue.

• terasoluna-gfw-web-blank

Issue links

Links to related issues.

• #xx

[yoshikawaa]

Please close after considering whether to need or not backport.

[takahashihrzg]

The scope of the backport will be determined in future discussions.

[yoshikawaa]

The scope of the backport will be determined in future discussions.

In terms of quality, it's better to backport to all maintenance versions since 1.0.x due to a fatal non-bootable bug.
In terms of release, it is unknown which version is subject to normal maintenance, emergency maintenance, or EOL, and it is necessary to consider it.

I've given the backport label so that we can see that it's needed to backport after selecting a release target.