<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto;"><div style="word-wrap:break-word"><div><span style="white-space: pre-wrap;"> </span>1. Create our own library to support MPNS</div><div><span style="white-space:pre-wrap"> </span>2. Support the latest version of this library <a href="https://github.com/notnoop/java-mpns" target="_blank">https://github.com/notnoop/java-mpns</a></div></div></blockquote><div><br></div><div>I think 2) sounds reasonable. However since java-mpns is not maintained, we can start building on-top of that (and do changes, e.g. package change, to that fork), so is close to option 1)</div><div><br></div></div></div></div></blockquote><div><br></div><div>I agree that 2 is almost the same as 1 except that we don’t have to start from scratch. I’ve already cloned and fixed a couple of issues on the java-mpns project see <a href="https://github.com/edewit/java-mpns">https://github.com/edewit/java-mpns</a></div><div><br></div><div>I’ll change the package and then we need to get it in maven central. It’s already on the jboss repository</div><div><br></div><div><br></div><br></div><div><br></div><br></body></html>