The mystery: Android Studio's Project Structure and Build System I don't know if this is because of the Gradle Build System (I'd wager it is), but I'll tell you what I've understood so far. Update 4: 2014/09/11 Added Cheat Sheet for BuildTypes, Flavors and Variants(I finally feel confident to write this :D) Update 3: 2014/09/11 Updated the comparison workspaces and projects to be precise Update 2: 2014/04/17 Added more detail to AS project structure Update 1: 2013/07/29 Added IntelliJ Project Structure The IntelliJ's Project structure (shown at the end) is for IntelliJ with the android plugin. The Android Studio, however, has a project structure divided like so: Structure: Projects and Modules module in Android Studio is like a project in Eclipse project in Android Studio is like a

While migrating your project from Eclipse to Android Studio, no change have been done on project structure. The only that have changed are new .iml and .gradle files. Your java code stays in project/src/ folder, and has not been moved in project/src/main/java folder (like in a new created project from AndroidStudio). Your AndroidManifest file also stays in the project/ folder and has not been moved in project/src/main/ folder (like in a new created project from AndroidStudio). At migration, the build.gradle file is customized in order to be able to compile with the old structure is described in the gradle documentation : Configuring the Structure For a new created project in AndroidStudio, the sourceSets part of the build.gradle file : sourceSets { main.java.srcDirs = ['src/java']

Mac OS is probably hiding the folder. You can either disable file hiding by entering defaults write com.apple.Finder AppleShowAllFiles TRUE into terminal and then using force quit to restart finder, or you can use eclipse to export your project to something like a .jar file and save yourself the headache. Good luck

If the library is a .jar file, you can simply paste it into the libs folder of your app. Android should automatically add it to the build path. As far as pushing/pulling from BitBucket goes, as long as you add the .jar file in git the library will be committed like any other file.

As the others say, a full import is not possible, but just try a manual 'import'. The key files for an Android project are the Java sourcecode (src directory), the resource XML files and the Manifest. Just create a new Android project in Eclipse and simply copy these files over. You may have to create a new package structure, so construct the necessary packages and copy each sourcefile over and refactor the package name if necessary. If you use any additional libraries, you may have to manually import them as well.

The eclipse project files (.project and .classpath) are not part of the github repository so you can't just import it into Eclipse. Easiest way to fix that is probably to create a new Android project yourself and then copy the files from the github repo into it.

I think that you should check the error log...probably Eclipse won't let you import it, with a message "Some projects cannot be imported because they already exist in the workspace". If this is the case, using/creating another workspace should fix the problem. If you don't want to change workspace, you may want to check this post.

Checkout Integration ZXing library directly into my Android application question and answers on Embed Zxing library without using Barcode Scanner app question. I'm quoting the answer of Sean Owen, one of the author's of Zxing library from this answer: " The complete source code is available from the ZXing project. You want to build core.jar from core/ and put it in your Android lib/ folder to include the core decoder in your app. You do not want to include javase. You can look to the code in android/ as it is the source to Barcode Scanner, but as the authors we'd suggest you not just copy and paste it." Hope this helps.

Your build.gradle is trying to use Android SDK tools 8 which isn't installed on your machine. If you look at your build.gradle file you probably have this line buildToolsVersion "8". You want your build.gradle file to point to the Android SDK tools that you currently have installed (preferably the latest). Just open the Android SDK manager and see which tools you have installed and change the buildToolsVersion "8" to the right version.

If you want to "Create project from existing source", you need to create a new directory and then put the project directory tree into that new directory. Then point to the new directory when importing. For me this worked the best solution ! File->Import->General->Existing Projects into Workspace, Next Select root directory: /path/to/project Projects->Select All UNCHECK both "Copy projects into workspace" and "Add project to working sets" Finish More info also in this LINK

I came across this problem yesterday. I had recently updated the ADT plugin without updating the Android SDK Tools and Platform-tools. So make sure all of the above are up-to-date.

After recently working on a new application project, it came to a stage where I had to download the project at home on my personal machine. So of course I logged into our SVN and grabbed a copy. After getting the project there was an error in the project: Cannot nest 'Project/src/main/java' inside library 'Project/src I knew previously that this error wasn’t occuring. As far as the project classpath is concerned there was only one src path which correctly pointed at the folder Project/src/main/java After searching through the project I found out the issue – in the .settings folder there is a file named: org.eclipse.wst.common.component You should find you have a line similar to the following: <wb-resource deploy-path="/WEB-INF/classes" source-path="/src"/> To f

You can't install two apps with the same package name: package="com.jungle.main" Change one of them and you'll be fine. See also: http://developer.android.com/guide/topics/manifest/manifest-element.html#package

RightClickon Project --> Select Properties ---> Select Resource You can locate see ur Project Location

whoa! Solved! It was really a weird behaviour from cmake: I had three files conf.c that must be merged into a static library. When cmake run the AR program to create the library, it executed a command that was like: ar cr dir1/source1.c dir1/source2.c ... dft/conf.c rdft/conf.c ar r reodft/conf.c dir2/source3.c so, maybe due to the huge number of object files that were to be linked, cmake splitted ar commands in two command, BUT second command overwrited one of the two file conf.c that were added with the first command, so symbols defined with the first ar command were lost! This is clearly a bug in ar because even if the source file is the same, maybe the content may vary, thus symbols are not to be deleted. Thanks to all! Your suggestions brought me to the right solution!

That shouldn't be the case usually. You can try the auto import of the library needed instead of manually inserting the library one by one by ctrl+shift+O. Another common problem is that you included the library but it still cannot reference it correctly. Something like cannot reference R.id.xxx, that can be solved by making sure that you don't have import android.R in your code. Hope that helps :)

The problem was that the commit had additional information which broke eclipse. I created a new project from the sources, cleared the repo and made the commit based on this tutorial on the main list.

Did you add the jar to the library as an external jar? That would be the path it stores, then. Use a variable instead if you have to add it manually: http://help.eclipse.org/juno/topic/org.eclipse.jdt.doc.user/reference/preferences/java/buildpath/ref-preferences-classpath-variables.htm?cp=1_4_2_0_1_0 . It's possible, though, that if this is part of Java 7, you just need the latest version of Eclipse--it supports Java 7 explicitly.

On the screen indicated by your screenshot, you can rename each "MainActivity" to something more unique and relevant by clicking in each text field under "New Project Name". It's not immediately apparent that this field is editable, but it is.

Note sure of your Eclipse version. In 4.2, Select Window>Open Perspective>Other... and then CVS Repository Exploring. In the "CVS Repositories View", right click and select New>Repository Location.... Connection Type: pserver User: anonymous Host: tolven.cvs.sourceforge.net Repository Path: /cvsroot/tolven Use default port Click on OK. You should see something like this: You're going to want this to be an Eclipse Java Project. So create a Java project with separate source and binary folders. In the "CVS Repositories View", right click on the stuff you want to edit in Eclipse and select Check Out As.... Select ...into an existing project, then Next>. Now select the source folder of the Java project you just created. and Finish. You're probably going to want to move the non-Java files

You can use eclipse plugin for maven Eclipse plugins for Maven and also check this out here and this answer will help you much: http://stackoverflow.com/a/2061645/1932105

Create a new maven project in eclipse, notice that you have an src/main/java/ folder Go to your netbeans java project, right-click on 'Source Pakages', click on properties and copy the location of this folder Go to your files explorer and paste the location, copy all folders under src/ return to your maven project in eclipse and paste the folders (actually your java packages) under the src/main/java folder if you used jar libraries just add them to dependencies in the pom.xml

The problem is that the generated sources folder has many other class definitions which are also needed by the RegistryResourceImpl class. You need to add the generated source folder as a source code location in the maven pom. A similar question has a decent answer. Appropriated from that answer: <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>build-helper-maven-plugin</artifactId> <executions> <execution> <id>add-source</id> <phase>generate-sources</phase> <goals> <goal>add-source</goal> </goals> <configuration> <sources> <source>${project.

I automated setting up eclipse, including importing existing maven projects. First run mvn eclipse:eclipse on the project mvn eclipse:eclipse: Next grab an eclipse plugin that will perform the headless import of projects into the workspace: wget https://github.com/snowch/test.myapp/raw/master/test.myapp_1.0.0.jar Copy the above jar to your /eclipse/dropins/ folder. Next find all the directories that can be imported into eclipse and append them with '-import' IMPORTS=$(find . -type f -name .project) # Although it is possible to import multiple directories with one # invocation of the test.myapp.App, this fails if one of the imports # was not successful. Using a for loop is slower, but more robust for item in ${IMPORTS[*]}; do IMPORT="$(dirname $item)/" echo "Import

To share code between the two projects create a Portable Class Library (PCL) project and reference it in the two projects. Make sure you choose the right .Net framework (for compatibility with WCF project).

OK, i will answer my question myself. Basically this situation can be solved by creating a new dynamic web project with the required structure and then using Linked folder functionality of eclipse.

This is not possible in Java, the runtime system always looks for a/b/c as directory structure for a specific class in package a.b.c. See http://docs.oracle.com/javase/specs/jls/se7/html/jls-7.html#jls-7.4

You probably have your own urllib2 python file in your system path, perhaps in the local directory. Don't do that, as it breaks werkzeug (and other python code). To be compatible with both python 2 and 3, werkzeug uses constructs like: try: from urllib2 import parse_http_list as _parse_list_header except ImportError: # pragma: no cover from urllib.request import parse_http_list as _parse_list_header The from urllib2 import parse_http_list as _parse_list_header line could throw a ImportError exception if you have a local urllib2.py module or urllib2/__init__.py package that masks the standard library file. Because the first import throws an ImportError, the second line is executed, which also fails because the urllib.request package is only available on Python 3. From your pro

OK on OS X - you might be getting hit with the specific file encoding, often there are magic comments at the top of the file or the file itself is set to an encoding. You can alter your file encoding on Mac OS X like so: iconv -f ISO-8859-1 -t UTF-8 File.txt > File.txt.utf8 And for a bunch of files: find /path/to/Workspace -name *.txt -type f | (while read file; do iconv -f ISO-8859-1 -t UTF-8 "$file" > "${file%.txt}.utf8"; done); This will convert all txt files, change *.txt to get different file types.

First, I think it's easier to start with Maven, create a WAR project, and use that to generate the Eclipse project files, which you can then import. This has the advantage of allowing Maven to not only create the correct folder structure, but also let it manage your dependencies. There are plugins for Eclipse that help you work with Maven, and you should be able to find lots of How-Tos using Google. Otherwise, you would have to create a project type that generates the WAR, one of which I believe is a Web Project, and layout the folder structure manually. After you have the proper folder layout, you will need to setup your web.xml to enable Spring, add your Java classes and view files (html, jsps, whatever), and build a WAR. The final step would be to deploy that WAR to a web container

I had same issue with the latest Android Studio () today, and I finally found that configuring a https proxy for Gradle can solve the issue. I only set a http proxy at the beginning. Gradle needs to sync some files via HTTPS. Use IP address instead if hostname of proxy can't work.

I faced the same problem, this is what i did. Hope it helps you too. Remove all the libraries in your project.(Properties->javaBuildPath->library(tab)->select dependancy folder->remove) Now go to libs and remove the library.(your project will show some errors, never mind) Finally import the library that contains the sub library.

This is Rachel from Dynamsoft. I'm afraid currently SourceAnywhere Eclipse plugin doesn't support importing project from source control server directly. I will forward your request to our R&D team for future consideration. Currently, you can perform Get from SourceAnywhere GUI client (Windows/Java/Mac) and then open the project in Eclipse. Thank you for using SourceAnywhere.

I got the same error after installing "WebSphere® Application Server V8.5 Tools for Juno". Updating to the latest "m2e-wtp - Maven Integration for WTP" in the eclipse marketplace solved the problem. I'm not sure if this was your problem but might help other people facing this scenario.

First of all - I believe Java Web Project will not work with any of Android specific classes due to many reasons. If your MonitoringModel contains some Java code that you want to share between Android and Web application you can extract it to separate Java project and use a Link Source option in Properties->Build Path to link it to both projects.

I had this same issue recently and so, although outdated, here is the answer for anyone else. It is related to your build order. I found that the build order in VS did not always correspond to the actual build order. I suggest looking through the output window after a failed build and see which projects are built first and last (you need these to configure Crypto). Obviously, don't forget to ignore any projects that are setup projects or projects not being built in release mode. All that is required, is to reconfigure crypto with the correct first and last projects, reload your solution and it will build.

I have found this: http://mojo.codehaus.org/javascript-maven-tools/javascript-ria-archetype/index.html This might be an answer to parts of the question. Now I only have to figure out how to use it with dojo.

First error looks like you are running in Linux?? Have you successfully installed LuaSockets? Its written in C so you need a compiler to install it. That can be found in Microsoft developer tools. You can also use cygwin. Alternatively if you have mingw installed you can first download: https://github.com/pkulchenko/ZeroBraneStudio/blob/master/build/build-win32.sh Then you can run: bash ./build-win32.sh lua luasocket

You may want to review the steps this link. It goes through the steps of adding it to your Android project, regardless of your IDE. Eclipse will work just fine. These steps take some time and effort, but I have successfully done this before.

You should look at the multiproject example for the layout attached in the doc. http://tools.android.com/tech-docs/new-build-system http://docs.google.com/viewer?a=v&pid=sites&srcid=YW5kcm9pZC5jb218dG9vbHN8Z3g6NDYzNTVjMjNmM2YwMjhhNA Essentially you want a top level settings.gradle that tie all the pieces together. Ideally they should be in one single git repo to make your life easier. However you probably can use symlink to tie them into a common build repo that contain your top level settings.gradle.