fix sw360populated/Dockerfile

[AtsushiNemoto]

The wildcard in "tomcat-*/webapps/$folder" is not expanded since this folder does not exist yet at this point. Use "tomcat-9.0.17" as like as the sw360empty/Dockerfile.

Signed-off-by: Atsushi Nemoto atsushi.nemoto@sord.co.jp

[maxhbr]

The wildcard works. You got this probably due to an outdated sw360_SW360TomcatVolume volume in docker, which still contains the old Liferay6 content (and thus not the current tomcat and can't expand the wildcard). Please try again with the following cleanup steps before building the images:

• clean generated or downloaded files in ./miscellaneous/prepare-liferay
• clean generated files in ./docker-images/sw360empty
• call ./sw360chores.pl -- down (this removes the state of the setup, e.g. drops all databases)
• remove the volume via docker volume rm sw360b_SW360TomcatVolume

[AtsushiNemoto]

The wildcard works. You got this probably due to an outdated sw360_SW360TomcatVolume volume in docker, which still contains the old Liferay6 content (and thus not the current tomcat and can't expand the wildcard). Please try again with the following cleanup steps before building the images:

* clean generated or downloaded files in `./miscellaneous/prepare-liferay`

* clean generated files in `./docker-images/sw360empty`

* call `./sw360chores.pl -- down` (this removes the state of the setup, e.g. drops all databases)

* remove the volume via `docker volume rm sw360b_SW360TomcatVolume`

I did all these cleanups before building. Without this fix, both "/opt/sw360/tomcat-9.0.17/webapps" and "/opt/sw360/tomcat-*/webapps" will be created in the container.

Please try this:

$ mkdir -p /tmp/tomcat-9.0.17/webapps
$ echo /tmp/tomcat-*/webapps
/tmp/tomcat-9.0.17/webapps
$ echo /tmp/tomcat-*/webapps/foo
/tmp/tomcat-*/webapps/foo

Thus, mkdir with wildcard will not work as expected.