On Fri, Dec 12, 2014 at 10:20 PM, Bruno Oliveira <bruno(a)abstractj.org>
Hi Matthias, I guess the issue is related with AGPUSH-1134, right?
No, the delay of 1.0.3 is related to AGPUSH-1135 and AGPUSH-1136 (related
to KC 1.0.x).
AGPUSH-1134 is related to using the KC 1.1.beta2. I got the stack-trace
when deploying the server to WF 8.2. I will take a look at it again next
week, and provide detailed steps on the JIRA.
Could you please provide the exact steps to reproduce the issue? Here I
1. git clone firstname.lastname@example.org:aerogear/aerogear-parent.git && cd
aerogear-parent && mvn clean install
2. changed UPS pom.xml:
3. On master branch: cd aerogear-unifiedpush-server && cp
4. cp servers/auth-server/target/auth-server.war
5. cp servers/ups-wildfly/target/ag-push.war
I'm running on WildFly 8.1 and everything is working like expected. A
more detailed information would help to reproduce the issue like which
database and the steps to reproduce.
Thanks in advance.
On 2014-12-12, Matthias Wessendorf wrote:
> Hi team,
> due to an issue with migration of Keycloak and our own models, the 1.0.3
> release (see ) is delayed and will not happen in 2014. It's planed to
> have the release out in mid (late?) January 2015.
> Note: the 1.0.3 release will be (most-likely) the last release on the
> series :-)
> In 2015 the focus, for the Unified Push Server, will be on the 1.1.0
> release. A first alpha, supporting Windows Phone, has been released
> (see ).
> In addition I have also updated our roadmap, see .
> Any thoughts or feedback is more than welcome!
>  https://issues.jboss.org/browse/AGPUSH/fixforversion/12325082
>  https://github.com/aerogear/aerogear.org/pull/441
> Matthias Wessendorf
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> aerogear-dev mailing list
aerogear-dev mailing list