<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><div>On Jul 3, 2013, at 8:56 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 1, 2013 at 1:32 PM, Christos Vasilakis <span dir="ltr"><<a href="mailto:cvasilak@gmail.com" target="_blank">cvasilak@gmail.com</a>></span> wrote:<br>
<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">Hi Tommy,<div><br></div>
<div>nice guide! </div><div><br></div><div>did some formatting fixes on it and pushed on a branch here [1].</div><div><br></div><div>Further, had some issues following the "Configure the Build" for eclipse section. In particular:</div>
<div><br></div><div><b>>> PushEEDemo relies upon “aerogear-android”, so we must enable the two to work in tandem on the build path. In Eclipse </b></div><div><b>>> ADT, right click “aerogear-android”, choose “Properties”, then choose “Android”, and check “Is Library”.</b></div>
<div><br></div><div>Apart from the 'Is library' checkbox, in the same form the user should select a build target >= 4.0 otherwise there will be errors of missing import statements of "android.app.Fragment'.</div>
</div></blockquote><div><br></div><div><br></div><div style="">I *think* the "Android support library" fixes that, see [1]</div></div></div></div></blockquote><div><br></div><div>unfortunately no 'Android Support lib' will resolve the 'android.support.v4.app.*' imports problem only.</div><div>The Build target >= 4.0 is needed otherwise imports of 'android.app.Fragment' won't work</div><div><br></div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div style=""><br></div><div> </div><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">
<div style="word-wrap:break-word"><div><br></div><div><b>>> Now, right click >>“MainActivity” of PushEEDemo, and choose “Properties” again. Click “Java Build Path”, and check the box >> next to “aerogear->android”. This will include the necessary resources needed for AeroGear.<br>
</b><br>Unfortunately I couldn't find that but I solved the issue by selecting 'Android' from the left hand side of the Properties dialog, and on the "Library section I clicked 'Add' and added the dependency to 'aerogear-android' (found on the instructions suggested by the eclipse aerogear guide <a href="http://aerogear.org/docs/guides/GetStartedAndroidEclipse/" target="_blank">here</a>)</div>
</div></blockquote><div><br></div><div style="">yes, that should be the right way.</div><div><br></div><div> </div><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">
<div style="word-wrap:break-word"><div><br></div><div><b>>> Finally, we also need to add a few Android and Google resources to the build path of PushEEDemo….</b></div><div><b><br></b></div><div>Once the libraries were added on PushEEDemo and tried to run eclipse complained "Your project contains errors, please fix them before running your application", mainly cause aerogear-android has missing dependencies. To fix that the libraries should be added to the 'aerogear-android' project and not on 'PushEEDemo'. Further the user should ensure on the "Order and Export Tab the libraries are checked otherwise the dependent ant project "PushEEDemo" will complain. Once this is setup, the project run fluently :)</div>
<div><br></div><div>(As a side note ADT tools provides a feature to add the support library, that is right clicking on the aerogear-android project and selecting "Android Tools->Add Support library…" will download the missing support library so probably for this, we can instruct the user to do that).</div>
<div><br></div><div><br></div><div>My big cumbersome was downloading and configuring the missing libraries. I know that since aerogear-android uses maven </div><div>(and with the Maven SDK Deployer installed) we can do:</div>
<div><br></div><div>mvn dependency:copy (after we git clone the project)</div><div><br></div><div>that will install the missing libraries in the /libs folder of aerogear-android and then be auto picked up by eclipse when we import the project (adding only the support library using the ADT eclipse feature 'Add Support Library' and the google-play services.jar). I tried that too and worked fluenty.</div>
<div><br></div><div>I think for the purpose of the guide it can use the method you describe e.g manually adding the dependencies but probably add a comment in the like that "you can skip the manual process of downloading the libraries by using the maven sdk deployer plugin that aerogear-android uses, for more information see the installation instructions in the project's web site <a href="https://github.com/aerogear/aerogear-android" target="_blank">here</a>)</div>
<div><br></div><div>I think Summers and Passos can comment better on this one.</div></div></blockquote><div><br></div><div style="">yep.</div><div style=""><br></div><div style="">I also had issues with Eclipse, and Summers already commented on some of the issues there (see [1]). </div>
<div> </div><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"><div style="word-wrap:break-word"><div><br></div>
<div>Nice work! </div></div></blockquote><div><br></div><div><br></div><div>+1</div><div><br></div><div><br></div><div>[1] <a href="http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-Eclipse-issue-with-the-quot-Push-quot-td3475.html">http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-Eclipse-issue-with-the-quot-Push-quot-td3475.html</a> </div>
<div><br></div><div><br></div><div><br></div><div> </div><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"><div style="word-wrap:break-word">
<div><br></div><div>Thanks,</div><div>Christos</div><div><br></div><div><br></div><div><br></div><div>[1] <a href="https://github.com/cvasilak/aerogear.org/commits/initial.review" target="_blank">https://github.com/cvasilak/aerogear.org/commits/initial.review</a></div>
<div><br>Depending upon your configuration, you may need to also reference the following external JARs (followed by location) in your aerogear-android project:<br><br><div><br></div></div><div><div class="h5"><div>On Jun 26, 2013, at 10:52 PM, Tommy McCarthy <<a href="mailto:tomccart@redhat.com" target="_blank">tomccart@redhat.com</a>> wrote:</div>
<div><div><br><blockquote type="cite">Hey everyone,<br><br>I just pushed out the first iteration of the Android Push tutorial, similar to the iOS tutorial, to my GitHub account. I'm looking for some feedback on what I have so far (including style, content, depth, etc.) <br>
<br><a href="https://github.com/tmccarthy9/aerogear.org/tree/master/docs/guides/aerogear-push-android" target="_blank">https://github.com/tmccarthy9/aerogear.org/tree/master/docs/guides/aerogear-push-android</a><br><br>Of course, I will be both finishing and polishing it up before I submit a pull request, but I'd like to know what everyone thinks so far.<br>
<br>Thanks for your help!<br>Tommy McCarthy<br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div></div></div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev</blockquote></div><br></body></html>