Hello Sisinda
I created an "Android" branch on Apache SIS source code repository. For
now, I ported only your work on the pom.xml files; I did not yet ported
any work on Java files (they will be the topic of another commit later).
Consequently, if you want to merge the "Android" branch into your GitHub
clone, you may have some conflicts to resolve in pom.xml files but not
in other places (normally).
The main change that I did in the pom.xml files compared to the files on
your GitHub clone was to avoid repetition:
* Build configuration in the root pom.xml file instead then repeated
in child pom.xml files.
* Dependencies declared in sis-utility omitted since they were
declared in the parent pom.xml file.
* Maven scope of JavaEE dependencies left to "provided" (I omitted the
change to "compile").
I could not test yet if those changes work since since Maven reports a
missing core/sis-utility/src/main/AndroidManifest.xml file. Maybe it was
forgotten from previous commits?
I also have a question: the following dependencies looks like for
testing purpose (judging by their name), but have a "provided" or
"compile" scope instead then "test". Is it intentional?
* android-test
* com.android.support.test
Thanks,
Martin
