Hello Martin,
Thank you for the suggestions. It's a great help.
> Is there a way to run the JUnit tests in an Android environment?
It is possible to run JUnit tests for Android apps. But not sure about
libraries. I think we will have to couple up with an app to run tests.
I will look into this.
> Would it be possible to maintain a document
I will add README in both of the branches(Android2 and Android26)
> I suggest that you remove completely javax.naming usage on the Android
> branch. It is currently used for only one purpose: getting a
> javax.sql.DataSource for a connection to the EPSG database. I presume
> that on Android, the way to connect to a database is different. What is
> the usual way on Android?
Android provides SQLiteOpenHelper abstract class to help to get
connection to the database. Reference to the database can be retrieved
by instantiating the subclass of SQLiteOpenHelper.
> An alternative would be to replace java.awt usage by something
> equivalent on Android platform if available, or something rewritten on
> Android branch otherwise. I suggest that you post the java.awt
> dependency that you found (or maybe better, create a task on JIRA or
> GitHub) so we can suggest replacements. Usage of AWT in SIS should be
> much easier to replace than usage of JAXB.
Apart from SIS, com.sun.xml.bind:jaxb-impl package (which is added as
a dependency for JAXB) requires java.awt package. The usage of
java.awt is found in only two classes in jaxb-impl package and not
sure if they actually do anything in our situation.
Sisinda
