This problem will not be solved in a JBDS build, but it must be resolved in time for the JBDS 6.0.1 release.
The issue is that the archetypes didn't get properly checked for EAP 6.0.1. As a result they are still using versions of the BOM which aren't in the EAP 6.0.1 Maven repo.