Use LMP for copyDeps in package

[scottkurz]

Fixes #41.

Might be better just to bind the 'create' goal to prepare-package. At least we don't have to duplicate the copyDeps config in the dependency-plugin.

This overlaps the discussion in OpenLiberty/ci.maven#739

Obviously the doc would need to be updated, just wanted to raise the suggestion as a first step.

[gkwan-ibm]

hi @scottkurz

Your PR may work, although I didn't try it yet. For CI/CD automation, I compared the current way and your way:

1. cd finish
2. mvn clean package
3. mvn verify

For step 2, war file was built and

• the current way only downloaded the postgresql library
• beside the postgresql library, your way downloaded and installed kernel Liberty that is an overhead and is not necessary.

[scottkurz]

For step 2, war file was built and

* the current way only downloaded the postgresql library

* beside the postgresql library, your way downloaded and installed kernel Liberty that is an overhead and is not necessary.

Yes, that's true there is an additional cost to download the kernel runtime.

It would be nice if we could get around to improving LMP here. Note that besides the OpenLiberty/ci.maven#739 issue I mentioned we could also consider something like:
OpenLiberty/ci.maven#1094 to do a create without an install.

But IMO, it's worth to have the extra overhead for the simpler developer experience and not having to have the extra plugin config in the pom.xml. I usually develop from a workstation, where I only have to download a new kernel once a month. If this is primarily going to run in some kind of container/cloud env, however, it might happen every time. Still it's only about ~10M download, so not much.