Note that there are some explanatory texts on larger screens.

plurals
  1. POPractice for ensuring Android projects build right after SVN checkout in Eclipse
    primarykey
    data
    text
    <p>Problem:</p> <p>When a project is checked into SVN, and someone else checks it out, there is an exclamation mark on it and build path errors need to be resolved. How to fix it?</p> <p>As an example, I have a project and following is it's structure:</p> <p>It has 3 libraries in libs folder:</p> <pre><code>* android-support-v4.jar * bugsense3.2.2.jar * gcm.jar </code></pre> <p>Android Dependencies folder has:</p> <pre><code>* annotations.jar </code></pre> <p>Referenced Libraries has:</p> <pre><code>* gcm.jar </code></pre> <p>Android Private Libraries has:</p> <pre><code>* bugsense3.2.2.jar * gcm.jar * android-support-v4.jar </code></pre> <p>Google APIs [Android 2.2] has:</p> <pre><code>* android.jar * maps.jar </code></pre> <p>So it seems like that whatever we place in the libs folder is automatically added to the Android Private Libraries, is that accurate? So they can be checked in to SVN and when someone else checks it out and builds it, the .jars in Android Private Libraries will simply point to his local workspace so that's not an issue.</p> <p>However, annotations.jar in Android Dependencies and android.jar and maps.jar in Google API are referencing the android-sdk folder on my C:. So when someone else checks out my entire project, they have build issues that they have to resolve via the Java Build Path. </p> <p>What is the standard practice to have all the libraries kinda stored in SVN in such a way that when a new developer comes in and checks out the project, he simply builds without fiddling around with the settings? I suspect we're going in the territory of using a build management system, continuous integration, build server, etc etc. So I know of it slightly but have never actually used it in practicality as I've never worked in a large enough team. If anyone would be so kind to give me exactly what they use (the actual tools like Maven, Gradle, etc), then it would be much much appreciated!</p> <p>Thank you,</p> <p>-V</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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