In WFMP-269 we introduced a way for dependencies to be included as additional deployments for the package goal. We did his by using the MavenProject.getArtifacts()} and filtering the artifacts. However, there are a few issues with this.

One is it brings in transitive dependencies. We don't really want those.

Another is it doesn't include all scopes. The reason why is the package goal explicitly requires compile and runtime dependency resolution.

What we really should be doing is MavenProject.getDependencies() and filtering those. I was not able to find something equivalent to the org.apache.maven.artifact.resolver.filter.ArtifactFilter for dependencies. There is a change we need to either create one and find a way to convert a dependency to an artifact.