This seems to have been addressed on the an email thread , but I don't see a formal issue.
summary: scm-manager bundles jersey 1.18 which conflicts with GF 4.1, which is a 2.10.4. On restart, the webapp classloader 'wins' and provides the v1.18 javax.ws.rs.core.UriBuilder causing a AbstractMethodException.
In your thread, you mentioned "the only way seems to be an update to jersey 2.x and this is not possible until the guice integration is not ready", linking to the still open JERSEY-1950 , this is blocked by a lack of functionality in Guice (which seems to be by design in some regard) and hasn't received very much attention . There does not seem to be an end in sight for the standoff that started in 2013.
So, as it stands, scm-manager cannot be deployed on GF 4.1...but I believe it's fair to say it can quite possibly have the same problems when deploying on any JAX-RS 2 (JavaEE7) container? Doing some quick searches in the forum for WildFly issues seems to turn up similar issues - some hackery (implementation specific tricks) can be employed to get it working...though it seems other related issues has stifled things again.
IMO, waiting on Jersey or Guice to budge is going to make scm-manager look bad as EE7 becomes the standard in production environments -- and I really like this project. What can I do to help? I would be glad to help refactor the guice components to use CDI - with the benefit that you least you know it plays nice with EE. If not, is there anything else I can help with to get this resolved?