But it is happening as John said.
I've just tested, renaming my maven repository in a way that wildlfy could not reach it and I've got:


 ./standalone.sh 
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: .... /Wildfly/Neutral/wildfly-10.0.0.Alpha3-SNAPSHOT

  JAVA: /Library/Java/JavaVirtualMachines/jdk1.8.0_05.jdk/Contents/Home//bin/java

  JAVA_OPTS:  -server -XX:+UseCompressedOops  -server -XX:+UseCompressedOops -Xms64m -Xmx512m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

Exception in thread "main" org.jboss.modules.ModuleLoadException: Error loading module from /Users/eduardo/Applications/Dev/Servers/Wildfly/Neutral/wildfly-10.0.0.Alpha3-SNAPSHOT/modules/system/layers/base/org/apache/xerces/main/module.xml
at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:150)
at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:127)
at org.jboss.modules.LocalModuleFinder$1.run(LocalModuleFinder.java:150)
at org.jboss.modules.LocalModuleFinder$1.run(LocalModuleFinder.java:144)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.modules.LocalModuleFinder.findModule(LocalModuleFinder.java:144)
at org.jboss.modules.ModuleLoader.findModule(ModuleLoader.java:452)
at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:355)
at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:302)
at org.jboss.modules.Module.addPaths(Module.java:1028)
at org.jboss.modules.Module.link(Module.java:1398)
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1426)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:238)
at org.jboss.modules.Main.main(Main.java:384)
Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to resolve artifact 'xerces:xercesImpl:2.11.0.SP3' (position: END_TAG seen ...resources>\n        <artifact name="xerces:xercesImpl:2.11.0.SP3"/>... @28:56) 
at org.jboss.modules.ModuleXmlParser.parseArtifact(ModuleXmlParser.java:756)
at org.jboss.modules.ModuleXmlParser.parseResources(ModuleXmlParser.java:650)
at org.jboss.modules.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:446)
at org.jboss.modules.ModuleXmlParser.parseDocument(ModuleXmlParser.java:261)
at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:148)
... 13 more


On Jun 17, 2015, at 11:26 AM, John O'Hara <johara@redhat.com> 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

--
John O'Hara
johara@redhat.com

JBoss, by Red Hat
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom.
Registered in UK and Wales under Company Registration No. 3798903 Directors: Michael Cunningham (USA), Charlie Peters (USA), Matt Parsons (USA) and Michael O'Neill (Ireland).

_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev