Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>can you please let me know if you figured out how to accomplish this? (An actual working method)</p> <p>I found a work-around, by simply taking the classes.zip file and manually placing it in the jetty/webapps/console/WEB-INF/lib folder. This is because I figured that the "Zipping the classes.dex file" mentioned in Nick's link was not working because I could not find the classes.zip file anywhere in the application.</p> <p>So after copying it myself, my error 503 message went away and the webapp was deployed successfully. However I'm not too pleased with this solution because it's not feasible to ask people who want to install my application from the playstore to go to a website, download the classes.zip file, and copy it into the correct folder.</p> <p><strong>EDIT:</strong></p> <p>Hahaha! No sooner did I write this answer that I figured out how to correctly create the classes.zip file (deploying the webapp from within the application will work now!).</p> <p>So basically as the official i-jetty website says, you need to include the 3 things in your pom.xml listen in the site <a href="https://code.google.com/p/i-jetty/wiki/DownloadableWebapps" rel="nofollow">https://code.google.com/p/i-jetty/wiki/DownloadableWebapps</a>. Now the problem you will face by only including those three is that on newer Android releases (the android-maven-plugin), you will face issues with the part. So you need to add the Following to enable correct execution (add it AFTER closing the plugins element, and BEFORE closing the build element ( &lt;./plugin> ADD IT HERE &lt;./build> , without the dots):</p> <pre><code>&lt;pluginManagement&gt; &lt;plugins&gt; &lt;plugin&gt; &lt;groupId&gt;org.eclipse.m2e&lt;/groupId&gt; &lt;artifactId&gt;lifecycle-mapping&lt;/artifactId&gt; &lt;version&gt;1.0.0&lt;/version&gt; &lt;configuration&gt; &lt;lifecycleMappingMetadata&gt; &lt;pluginExecutions&gt; &lt;pluginExecution&gt; &lt;pluginExecutionFilter&gt; &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-dependency-plugin&lt;/artifactId&gt; &lt;versionRange&gt;[2.0,)&lt;/versionRange&gt; &lt;goals&gt; &lt;goal&gt;copy-dependencies&lt;/goal&gt; &lt;/goals&gt; &lt;/pluginExecutionFilter&gt; &lt;action&gt; &lt;execute /&gt; &lt;/action&gt; &lt;/pluginExecution&gt; &lt;/pluginExecutions&gt; &lt;/lifecycleMappingMetadata&gt; &lt;/configuration&gt; &lt;/plugin&gt; &lt;/plugins&gt; &lt;/pluginManagement&gt; </code></pre> <p>Now when you run the maven build, you will generate the your_webapp.war file you need in the your_application/target/res-overlay/raw folder. Copy the your_webapp.war file into the your_application/res/raw folder. Now run the maven build again. There you have it!! The webapp can be built correctly now :) Thanks a lot for getting me thinking and thus leading me to the solution!!</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload