Eclipse questions

Cliff2310 · February 4th, 2012, 02:44 PM

Hi Typo
No it doesn't, but I wanted to make sure it did not need something special like Google maps. I just click on OK and continue. It doesn't make any noise or do anything it just closes with the changes applied. Sometimes it takes Eclipse a moment or two to figure out there has been a change. Try saving a file after you make changes.
I am reading the emails before I read this message board. Someone asked
Btw, where does that Android-9 stuff come from? Could I change something in the project files BEFORE I import them, to change it to Android-10 before Eclipse gets involved with it?
I think in the Manifest file. That is the only place I know of.
Cliff

Typo · February 4th, 2012, 02:59 PM

Thanx for all help!

I've changed the Android manifest to <uses-sdk android:minSdkVersion="10" /> in the XML file *before* I import it. And it works!!! Now I can choose the Project Build Target.

Can't do it with the Notifications project, though. Eclipse has turned that folder to a ghost now, which cannot be deleted or replaced. It doesn't let me import the same project under another name either. This has happened before, and I solved by creating a new Workspace.

Now, this problem has been solved, but is it only me who fights a constant battle with Eclipse about paths and folders? Sometimes it creates an empty folder under my project named res, next to the "real" folder with the same name. And then it stops finding R. And by then there's no saving the situation, it is by then too late to import my.project.name.R so that import statement is always the first thing I type in every new java file. And if one ever deletes a project without selecting "files on disk (cannot undo)" the project becomes a ghost which can neither be deleted nor re-imported. And so on with a patchwork of workarounds I've found out by chance. Is this normal?

Cliff2310 · February 4th, 2012, 03:48 PM

Hi typo

Quote:

Originally Posted by Typo

Thanx for all help!

I've changed the Android manifest to <uses-sdk android:minSdkVersion="10" /> in the XML file *before* I import it. And it works!!! Now I can choose the Project Build Target.

Great!

Quote:

Originally Posted by Typo

Can't do it with the Notifications project, though. Eclipse has turned that folder to a ghost now, which cannot be deleted or replaced. It doesn't let me import the same project under another name either. This has happened before, and I solved by creating a new Workspace.

I usually quit Eclipse and open a window and do the dirty work ( delete, rename, ...). Then start Eclipse. I don't think I've seen a ghost folder.

Quote:

Originally Posted by Typo

Now, this problem has been solved, but is it only me who fights a constant battle with Eclipse about paths and folders? Sometimes it creates an empty folder under my project named res, next to the "real" folder with the same name. And then it stops finding R. And by then there's no saving the situation, it is by then too late to import my.project.name.R so that import statement is always the first thing I type in every new java file. And if one ever deletes a project without selecting "files on disk (cannot undo)" the project becomes a ghost which can neither be deleted nor re-imported. And so on with a patchwork of workarounds I've found out by chance. Is this normal?

Yea, Eclipse is nice but somebody really, really needs to write a "How to use Eclipse" book. I think it would be a best seller.
I have not had it create folders, but I have had it move a file from layout to string. A quick CTRL-Z will usually fix it or just move it back. I keep finding that Eclipse will do things that I had no idea it would do. There is no place to learn about Eclipse, just trial and error. Mostly error.
Cliff

macanucaire · February 9th, 2012, 02:45 PM

I don't know if this is the right place for this question but I'm a complete beginner to Android development and have come across a problem for which I cannot find a solution elsewhere. I've installed Eclipse and the Android SDK. Now I'm trying to install ADT with Eclipse and I get the message
Cannot complete the install because of a conflicting dependency.

Code:

 Software being installed: Android Hierarchy Viewer 16.0.1.v201112150204-238534 (com.android.ide.eclipse.hierarchyviewer.feature.group 16.0.1.v201112150204-238534)
  Software currently installed: Eclipse IDE for Java EE Developers 1.3.1.20100916-1202 (epp.package.jee 1.3.1.20100916-1202)
  Only one of the following can be installed at once: 
    Eclipse UI 3.6.1.M20100826-1330 (org.eclipse.ui 3.6.1.M20100826-1330)
    Eclipse UI 3.6.2.M20110203-1100 (org.eclipse.ui 3.6.2.M20110203-1100)
    Eclipse UI 3.6.0.I20100603-1100 (org.eclipse.ui 3.6.0.I20100603-1100)
  Cannot satisfy dependency:
    From: Android Hierarchy Viewer 16.0.1.v201112150204-238534 (com.android.ide.eclipse.hierarchyviewer.feature.group 16.0.1.v201112150204-238534)
    To: org.eclipse.ui 3.6.2
  Cannot satisfy dependency:
    From: Eclipse IDE for Java EE Developers 1.3.1.20100916-1202 (epp.package.jee 1.3.1.20100916-1202)
    To: org.eclipse.epp.package.jee.feature.feature.group [1.3.1.20100916-1202]
  Cannot satisfy dependency:
    From: Java EE IDE Feature 1.3.1.20100916-1202 (org.eclipse.epp.package.jee.feature.feature.group 1.3.1.20100916-1202)
    To: org.eclipse.platform.feature.group [3.6.1.r361_v20100909-9gF78GrkFqw7GrsZnvz0JWNTeb6fue6896L]
  Cannot satisfy dependency:
    From: Eclipse Platform 3.6.1.r361_v20100909-9gF78GrkFqw7GrsZnvz0JWNTeb6fue6896L (org.eclipse.platform.feature.group 3.6.1.r361_v20100909-9gF78GrkFqw7GrsZnvz0JWNTeb6fue6896L)
    To: org.eclipse.rcp.feature.group [3.6.1.r361_v20100827-9OArFLdFjY-ThSQXmKvKz0_T]
  Cannot satisfy dependency:
    From: Eclipse RCP 3.6.1.r361_v20100827-9OArFLdFjY-ThSQXmKvKz0_T (org.eclipse.rcp.feature.group 3.6.1.r361_v20100827-9OArFLdFjY-ThSQXmKvKz0_T)
    To: org.eclipse.ui [3.6.1.M20100826-1330]

I'm using Windows 7 Home Premium 64-bit and logged with admin rights.
Can anyone help?

Cliff2310 · February 9th, 2012, 07:41 PM

Hi macanucaire
Wow. I have not seen anything like that. It would seen that there is something wrong in Eclipse, but what I have no clue.
At this point your best bet is taking this question to
http://stackoverflow.com/questions/tagged/eclipse
There are people there who know there stuff.
Cliff