There's an ant task to create the jar from an existing war file. Add all additional dependencies to ivy.xml and it should work like a charm.

Ivy was needed for a resolver because BuildTool scans module dependencies....
The task has an option to save all dependencies (saved in directory: build/swarmlibs, build/swarmlibs/resolved)

If you have all dependencies, it's also possible to work without ivy (an offline variant)

The solution works for my use-case and isn't production ready

I didn't create an ANT task, it's a simple JUnit test case. The only problem is that all relevant swarm libs and dependencies were collected with a dirty hack in your swarm-plugin. It shouldn't be a problem to get all dependencies automatically becasue maven has this feature. I always start with minimum dependencies because if everything is working as unit test, it's easy to create tool support.

My solution is currently fixed to Alpha4 and I didn't know what's on your roadmap for the final release. So, I didn't create a future-proof solution and it was more a PoC. If you're going to change your BuildTool, everything can be different.
But I'll move my project to github after I found a solution for my dirty code.

But, both thumbs up for your work!

The size of the "fat" jars being generated for WildFly is certainly an area we need to work on, as it is also a concern of ours.

It would be fantastic if you were able to contribute the Ant Task you created for this. As we already support Maven and Gradle it would be great to add Ant as well.

Thanks for the idea of wrapping a WAR with WildFly Swarm. I've linked to your blog from an issue we have covering that topic: https://github.com/wildfly-swarm/wildfly-swarm/issues/5. Any contributions of how you did it, or other ideas on how it could work, would be greatly appreciated.

Thanks again for trying out the not-ready-for-production Alpha release and please check back often for updates.