Hello Sisinda
Yes, the sis-utility module would be the first one to do. But before
doing so, I think there is some project configuration to do. On your branch:
* In all pom.xml files, search for all occurrences of "0.8-SNAPSHOT"
and replace them by "0.8-android-SNAPSHOT" (or something else if you
have alternative proposal for the "0.8-android" part).
* Delete the "sis-build-helper" module (delete completely the
directory and remove the <module>sis-build-helper</module>
declaration in the parent pom.xml file. I don't think that we need
to port this module to Android; we can use the one from trunk instead.
* In all other pom.xml files (other than the one we deleted in
previous step), search all occurrences of "sis-build-helper" and
keep "0.8-SNAPSHOT" as their version number (do not make the change
to "0.8-android-SNAPSHOT" for them). That way, the build will
continue to use the plugin for trunk. This is okay because this
plugin is used only at build time; it will not be deployed on any
Android device.
* Delete the "sis-console", "sis-webapp" and "sis-openoffice" modules
in the same way as we did for "sis-build-helper", because I don't
think that those modules make sense on Android. I'm not quite sure
about "sis-javafx"; I think there is a project for running JavaFX on
Android, so we may keep that module for now.
After this cleanup, you can start with sis-utility module. I suggest to
begin with any package except "org.apache.sis.xml" and
"org.apache.sis.internal.jaxb.*". Those packages will be the hard ones,
so let keep them for the end of sis-utility.
Martin
Le 05/05/2017 à 15:11, Sisinda Dinusha a écrit :
> Hello Martin,
> Yes it is a good idea to start coding now because of the coming exams in
> next month. I will fork the repo and send commits as pull requests. I
> thought to start with the sis-utility package and I am open for suggestions
> in this one.
