mirror of https://github.com/tasks/tasks
Reverting change to .classpath, bumping version number and deleting the drop
database call on unsupported migration. Instead we show a user popup indicating the database might be corrupted (which is really the most often case an end-user sees this message). Hopefully this is another step in preventing permanent data loss? Although if the database is corrupted it's unclear what we should do.pull/14/head
parent
74ab94f6fb
commit
a29e5de53f
@ -1,13 +1,10 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<classpath>
|
||||
<classpathentry excluding="javax/xml/validation/|javax/xml/transform/dom/|javax/xml/parsers/|org/jaxp/transform/dom/|org/jaxp/transform/sax/|org/jaxp/transform/stax/|org/jaxp/transform/stream/|org/jaxp/stream/events/|org/jaxp/stream/util/|org/jaxp/parsers/|org/jaxp/stream/|org/jaxp/validation/" kind="src" path="src"/>
|
||||
<classpathentry kind="src" path="gen"/>
|
||||
<classpathentry kind="lib" path="lib/commons-codec-1.3.jar"/>
|
||||
<classpathentry kind="con" path="com.android.ide.eclipse.adt.ANDROID_FRAMEWORK"/>
|
||||
<classpathentry kind="src" path="gen"/>
|
||||
<classpathentry kind="lib" path="lib/locale_platform.jar"/>
|
||||
<classpathentry kind="lib" path="lib/FlurryAgent.jar"/>
|
||||
<classpathentry kind="con" path="org.eclipse.jdt.USER_LIBRARY/Android 1.6"/>
|
||||
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
|
||||
<classpathentry kind="con" path="org.eclipse.jdt.USER_LIBRARY/Python 2.6.4 interpreter library"/>
|
||||
<classpathentry kind="con" path="org.eclipse.jdt.USER_LIBRARY/Android 1.6"/>
|
||||
<classpathentry kind="output" path="out/production/astrid-2.x"/>
|
||||
<classpathentry kind="output" path="ecbuild"/>
|
||||
</classpath>
|
||||
|
||||
Loading…
Reference in New Issue