I have a single Github repo that contains 5 Android projects. Say one of the projects is named ToysGift and I want to change that project name to ToyDrive. How do I do that?
I am using Android Studio. Can I just change the name of the project in Android Studio and then push to Github? Git always proves challenging for me that's why I am asking first before trying different things because once I break what I have, I won't know how to get back to a good git state.
Did a quick test, Just changing the project name in android studio and then pushing should work, just make sure you have everything pulled so there aren't any conflicts.
Related
I am trying to incorporate push notification in my Ionic app (on ionic 1.3.1) using plugin phonegap-plugin-push.
Once I add the Android app to Firebase it tells me to update the build.gradle files in two places.
I find two build.gradle files in my Ionic project (another one is part of another plugin so ignoring that)
./platforms/android/build.gradle
./platforms/android/CordovaLib/build.gradle
I have played with making changes in different files, put the first change in first file, second change in second one, but I am not sure what I am doing here as it gives compilation errors when I run ionic build android. All the articles I have come across in my research point to using Android Studio which I am not using. And I am not sure what to do with the Synch now as instructed by FireBase.
I have placed the google-services.json for android from Firebase under platforms/android in my directory structure which I understand is the right place.
Look forward to any guidance on which build.gradle change goes where and what, if anything, I need to do with "sync now" in the context of Ionic App and get this up and running.
Thanks,
Sanjay.
It make sense that two changes happen in two files.
But for the app level one, you may write at the wrong one.
Please make sure you edit these two file.
enter image description here
I followed the recommendation in this article https://github.com/fechanique/cordova-plugin-fcm/issues/83
I removed all changes to my build.gradle files as they are supposed to synch automatically and it compiles fine.
That said, I am using the phonegap-plugin-push plugin (instead of cordova-plugin-fcm as in the article above) and my app crashes after it tries to init PushNotification but that is a separate problem I need to handle.
I am working on an android project that have later to be translated to many other languages and some changes have to do in design.
Now I want to know is there any way to make one project and keep it on git and later having changes should change the git project accordingly. So is it possible to create multiple apps for Android project. If yes, is it possible with Eclipse and git or someone has any other idea?
For the time being I am saving project in local directory and copy that project to make changes for next app.
This sounds that you should give git-subtrees a try. There, you create one repo with your base project and then import this repo into your specific app project. If you want to propagate your changes to the API, you push the changes to the base repo. We use this for component development.
But from my experience: do not use eclipse for working with git. It has some major drawbacks and might corrupt the repos. Use the CLI or another tool.
Just a quick question I did not find a good answer on. We are currently working on an APP created with Eclipse ADT Bundle. I recently started exploring Android Studio, and like it. Is it possible to still collaborate with my mates using Eclipse with a shared GitHub repo?
I noticed Android Studio converts the project to its own file structure, so I guess this does not go well with Eclipse, and the repo.
Is there any solutions for this? So I can keep developing in Android Studio, push to GitHub, while the rest of the team use Eclipse?
I think you can do it, you'll just have to explicitly define a sourceSet that matches the Eclipse structure. If you use any other build variants, they can't have any sourceSets because you wouldn't be able to check those files in to source control. However, there are several useful things you can do with build variants just with the build file. I think you can check in the build.gradle and other gradle stuff and it won't mess up your coworkers.
I want to fork an Android project (a normal application) from the official repository. After I clone the project and import it into Eclipse, I still have loads of different missing references to some other projects that prevent me from even looking at the layout ressources (as it tells me to fix the Java errors first).
Is there a way to fix those references, without using repo or cloning the whole repository (with all its projects)? After all I’m only interested in a single standard application there.
If it is using anything that is not the official SDK, you'll have to fetch it to get it compile. You can import in Eclipse if you have the whole thing.
BTW, cloning the whole repository is worthed, because you can grep to search for things, even if you don't intend to compile it.
For changing an App that is based on the whole Android repo, you really have to have the whole repo with you. Then you can just change that App and make that App, for example using "make Email". That will only build the Email.apk and not the whole ROM.
I have a bunch of code in Surround SCM, which I would like to get into a workspace in Eclipse. I will need to be able to work off of two branches. One for bug fixes, and one for new features, which can then be merged into my main branch. What is the best way to do this?
Disclaimer: I work for Seapine but I wasn't involved with anything to do with Eclipse.
What we do here internally is have a separate Java project for each branch in a single Eclipse workspace. To do so create a workspace somewhere and do:
File->New Project...->Java Project
This brings up the new project dialog. You can then point the project at the existing source path for the first branch, in my case the mainline branch, using the "Create project existing source" radio. I think I might have an older version of Eclipse installed but it should be the same or similar in new ones.
Clicking Next will take you to the next screen.
Here you can set up specific settings for this branch, like packages to exclude or things like that.
Click Finish and your project will be set up. Just repeat the same steps for a different branch using a different disk location.
Once you make changes to your branch code you can just check it into Surround SCM, promote it to the mainline, then do a get bring down the changes locally to your other directory.