buildWLSDockerImage.sh 3rd party jar -o value incorrectly hard coded.
edburns opened this issue · 1 comments
edburns commented
On lines 170 and 173 of buildWLSDockerImage.sh note that the version of the jar file is hard coded in the -o argument, but it is stored in a variable on the actual URL. Both the -o and the URL should be sharing a variable in some way.
This was found by @galiacheng reported to me by @zhengchang907 .
galiacheng commented
Hello @edburns the 3rd party db jar have been updated in marketplace offer, I think we can close this issue now.