Hi,<br>Does it really needs a complete EAR to run ? Can it not be a simple WAR deployed in an embedded jetty ? <div>Seb</div><div><br><div class="gmail_quote">On Wed, Sep 19, 2012 at 2:59 PM, Matthias Wessendorf <span dir="ltr">&lt;<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Wed, Sep 19, 2012 at 2:41 PM, jose_freitas<br>
&lt;<a href="mailto:joserodolfo.freitas@gmail.com">joserodolfo.freitas@gmail.com</a>&gt; wrote:<br>
&gt; Yesterday I clonned aerogear-ios, aerogear-ios-integration and the TODO<br>
&gt; application. I was able to install those projects but when running the<br>
&gt; aerogear-ios-integration tests, one of the required steps to run it, it&#39;s to<br>
&gt; deploy the todo.ear in a jboss server.<br>
<br>
</div>right - somehow that needs to be automated :)<br>
<br>
Cargo, maven etc - what ever comes to mind;<br>
<br>
Ideally it downloads the EAR file from github (instead of building it<br>
all the time)<br>
and deploys it to JBoss<br>
<div class="im"><br>
<br>
&gt; I was speaking with matzew and it seemed a good idea to integrate the ios<br>
&gt; enviroment to work within arquillian, so maybe we could automate steps like<br>
&gt; those where you need to deploy the server side of the application to execute<br>
&gt; tests.<br>
<br>
</div>should be scriptable, rigth ?<br>
<div class="im HOEnZb"><br>
<br>
&gt;<br>
&gt; What do you think? Do you think it would be useful? Is there anyone (besides<br>
&gt; me) trying to shoot in that direction?<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; View this message in context: <a href="http://aerogear-dev.1069024.n5.nabble.com/Aerogear-ios-and-arquillian-tp270.html" target="_blank">http://aerogear-dev.1069024.n5.nabble.com/Aerogear-ios-and-arquillian-tp270.html</a><br>

&gt; Sent from the aerogear-dev mailing list archive at Nabble.com.<br>
&gt; _______________________________________________<br>
&gt; aerogear-dev mailing list<br>
&gt; <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
&gt; <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
<br>
</div><span class="HOEnZb"><font color="#888888">--<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><br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br></div>