Absolutely. Once the work is merged back into master the generic-java branch will have served its purpose and will no longer need to be maintained.
There are a few additional builds that are done on the generic-java branch that are not currently done on the master branch. When time comes to merge the change in we will have to talk about moving the Java related builds over to the master build or we can decide to turn on the generic-java build for all Linux builds. George -----Original Message----- From: Trevor Bramwell [mailto:[email protected]] Sent: Friday, November 11, 2016 2:56 PM To: Nash, George <george.nash at intel.com> Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Generic Java Bindings [IOT-1089] Hi George, On Fri, Nov 11, 2016 at 09:37:49PM +0000, Nash, George wrote: > We are almost ready to merge the changes back in with master. As > stated in the earlier email we wanted to get this change in shortly > after the 1.2.0 release so it can be used by as many developers as > possible before the next release. Once this has been merged back in, can we look into removing the generic-java branch? Since the work is being merged back in master, I'm not sure there is much benefit in maintaining a non-divergent branch. Regards, Trevor Bramwell
