Hello,

this is the change, that makes it incompatible:
https://github.com/aerogear/aerogear-unifiedpush-server/commit/bb1a086427511139201b7b2df06adb9a89c37d33

Background: WF10 comes with a new/different JMS component, hence our JMS config had to change for WF 10.x.
Since this change is, unfortunately, not backwards compatible, we went for 1.2.0 line updates only.

That said, perhaps you can tweak the above changes into your own fork, and do a manual build?

On the other hand, the 1.2.0 line is alpha, yes. but it's really same as 1.1.x, but some more changes for being modern (e.g. WF10, Java8 etc)

-M



On Mon, Sep 26, 2016 at 10:57 AM, Sachidananda Patra <sachidananda.patra@hp.com> wrote:
I have tried with jboss-wildfly-10.1.0 with
aerogear-unifiedpush-server-1.1.3.Final-dist.



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Failed-to-process-phase-PARSE-of-deployment-unifiedpush-server-wildfly-war-tp902p904.html
Sent from the aerogear-users mailing list archive at Nabble.com.
_______________________________________________
Aerogear-users mailing list
Aerogear-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-users



--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf