For reference, you can get around the banned dependency issue by telling the build tooling to exempt the artifact from the bans, as shown below in the POM. This won’t actually help with the mywork dependency, because you actually need to access the version of the package within Confluence. So, even though this type of change would fix the compile-time error, it still wouldn’t do what you want in this case. (It’s still useful if you need to use packages that aren’t part of the Confluence core though.)
I note in passing that there seems to be a REST API for the mywork package. I have no experience with it though.
<plugin>
<groupId>com.atlassian.maven.plugins</groupId>
<artifactId>confluence-maven-plugin</artifactId>
<!-- ... -->
<configuration>
<banningExcludes>
<exclude>com.google.code.gson:gson</exclude>
<exclude>commons-io:commons-io</exclude>
<!-- ... -->
</banningExcludes>