-
1. Re: wildfly how to build full-profile?
lafr Dec 13, 2014 6:16 PM (in response to 88jgh)Complete server output (JBOSS_HOME) is under dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT.
-
2. Re: wildfly how to build full-profile?
88jgh Dec 14, 2014 4:23 AM (in response to lafr)Yes, but its size is only 12Mb, and also:
[jgh88@localhost wildfly-9.0.0.Alpha2-SNAPSHOT]$ find . -name "*.jar"
./jboss-modules.jar
./bin/client/jboss-cli-client.jar
./bin/client/jboss-client.jar
./bin/wildfly-launcher.jar
./modules/system/layers/base/org/apache/cxf/impl/main/cxf-rt-security-3.0.2-jandex.jar
./modules/system/layers/base/org/apache/cxf/impl/main/cxf-rt-ws-security-3.0.2-jandex.jar
./modules/system/layers/base/org/jboss/integration/ext-content/main/bundled/jboss-seam-int.jar
./modules/system/layers/base/org/jboss/as/version/main/jboss-as-version-9.0.0.Alpha2-SNAPSHOT.jar
Total: only 8 jars!!
While in jboss 6.0
[jgh88@localhost jboss]$ find . -name "*.jar" | wc -l
353
So, 353 jars there. In wildfly target directory i have empty dirs, for ex, weld has no jar, ejb has no jar....only 1 file: module.xml there! Where are all implementations of EE? Such as weld Hibernate etc...?
I still have a feeling I'm building "clean" wildfly server, without EE stuff...
Thanks in advance.
-
3. Re: wildfly how to build full-profile?
88jgh Dec 14, 2014 4:34 AM (in response to 88jgh)Oh, I think I know why is that...wildfly gets these stuff at runtime from .m2 repository! However can I include these jars into wildfly at compile time, so I can use it in the envirioment without maven? I suppose there should be a special parameter to build tool...Help plz!
-
4. Re: wildfly how to build full-profile?
88jgh Dec 14, 2014 5:26 AM (in response to 88jgh)Frank Langelage, Thank you man! I didn't notice dist directory )))
-
5. Re: wildfly how to build full-profile?
ctomc Dec 15, 2014 9:31 AM (in response to 88jgh)If you need proper release than you should build with -Drelease
so mvn clean install -Drelease
you can even add -DskipTests if you just want to get distro fast.
distro result will be in "dist" folder together with zip & tar.gz distribution.
as for general question about "inflated" distribution vs slim as we do by default goes.
it is controlled by parameter copy-module-artifacts="false|true" in server-provisioning.xml