AFAIK the build app server is not supposed to refer to Maven in the
final output. Maybe our build process has gotten munged up somehow? Or
else that translation now happens during distribution only?
On 06/17/2015 09:26 AM, John O'Hara wrote:
When I build WF10 in a build env. and move the built app server to a
different env. I am unable to start WF10. This is due to the modules
now resolving jars from the local maven repo. The build process
downloads and installs the required jars to local maven repo. that are
not available on the target environment.
Is there a way to either
a) build WF10 and package all the module jars into the build so that it
is portable,
or b) for the WF10 bootstrap process to download missing packages from a
remote maven repo on startup where any modules are missing in the local
repo?
Thanks
--
- DML