| Re: [cf-dev] Merging Californium repos |
|
I like the structure. I will now merge the unification branch and start to re-factor accordingly. Okay, cool. Merge it in now and fix possible release/packaging issues later? Two things: 1)
certs will HAVE to go into demo-apps in order to not refer to resources outside of the maven modules’ scope. But that should be ok if we
do not need the certs anywhere else but the demo code. So it is never needed for unit tests in Scandium? 2)
We can merge outstanding pull requests later. The scandium PRs may go into 1.1 which I do not want to start in the old repo anymore … not
sure what you want to do about the content negotiation PR but I think it can also be merged later. FWIW the PR is there since 2014 …. Merging later means you do it manually through rebase? Currently open requests are made for the old repos, aren’t they? The content negotiation PR has more become a “I you need this, this is probably a good way to do it” connection point for contributions. https://github.com/eclipse/californium.core/pull/56 might actually be in order
now, but I currently have no time to check it, I am afraid. Ciao Matthias |