Hey Sidney,
You should build with -P-eap,wildfly This will disable the eap/as7 distro and enable the WildFly distro (which is currently not enabled by default). The zips for the WildFly distro can be found in ./jboss-as7/wildfly/dist. To install, you should be able to simply unzip the switchyard-<version>-WildFly.zip over top your WildFly installation (I think).
Hope that helps,
Rob
Not sure if I specified the profiles correctly (I went with mvn -Peap,wildfly clean package) but I've got Wildfly objects now. I guess I was expecting to see some EAP targets.
Will report on how the WildFly install and initial tests go sometime next week.
Thanks!
./jboss-as7/bundle/target/switchyard-as7-bundle.zip
./jboss-as7/modules/target/switchyard.deployer.zip
./jboss-as7/wildfly/bundle/target/switchyard-wildfly-bundle.zip
./jboss-as7/wildfly/dist/target/switchyard-2.0.0-SNAPSHOT-WildFly.zip
./jboss-as7/wildfly/modules/target/switchyard.wildfly.deployer.zip
Rob,
You only need to build with -P wildfly, this builds all the AS7 extension, modules and bundles and then the overridden wildfly stuff.
There is now a Jenkins job for the SwitchYard distribution for WildFly.
Here's the job: SwitchYard-Release-WildFly [Jenkins]
Here's the link to the all-in-one zip: http://hudson.jboss.org/hudson/job/SwitchYard-Release-WildFly/lastSuccessfulBuild/artifact/jboss-as7/wildfly/dist/target…
Best,
Rob