The way the modules are laid out, wouldn't running a mvn package from the parent pom generate 2 separate jar files? one in frontend/target and one in backend target?

I'm not sure how to combine those so that the single jar would be able to serve both frontend and backend ( say for docker deployment ). Is there any insight you could provide on how ( or what ) to do to get there?