[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293855#comment-13293855 ] Thomas Mueller commented on OAK-138: Some ideas about possible projects we could create:

[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293842#comment-13293842 ] Thomas Mueller commented on OAK-138: I'm wondering why we have so many Maven projects (an

[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293787#comment-13293787 ] Jukka Zitting commented on OAK-138: --- > oak-mk contains one specific implementation of the M

[jira] [Assigned] (OAK-133) Session.refresh(true) should allow for manual conflict reconciliation

[ https://issues.apache.org/jira/browse/OAK-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig reassigned OAK-133: - Assignee: Michael Dürig > Session.refresh(true) should allow for manual conflict reconciliation

[jira] [Commented] (OAK-133) Session.refresh(true) should allow for manual conflict reconciliation

[ https://issues.apache.org/jira/browse/OAK-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293701#comment-13293701 ] Michael Dürig commented on OAK-133: --- On a second thought, it might be better to use a mixin

[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293679#comment-13293679 ] Thomas Mueller commented on OAK-138: Angela, so you would create 3 projects? mk-remote-c

[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293674#comment-13293674 ] angela commented on OAK-138: +1 for a separate module for the mk-remoting. in my experience the r

[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293673#comment-13293673 ] Thomas Mueller commented on OAK-138: I don't personally believe a separate Maven project

[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293623#comment-13293623 ] Jukka Zitting commented on OAK-138: --- I'd rather just put the code to oak-mk as it's tightly

[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293559#comment-13293559 ] Dominique Pfister commented on OAK-138: --- -1 to merging as well: I prefer having an oak-

[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293542#comment-13293542 ] Thomas Mueller commented on OAK-138: I know Felix, you would create a separate Maven proj

[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293525#comment-13293525 ] Felix Meschberger commented on OAK-138: --- +1 to creating a separate module for remoting

[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293499#comment-13293499 ] Thomas Mueller commented on OAK-138: The log wrapper is a somewhat similar implementation

[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293483#comment-13293483 ] Stefan Guggisberg commented on OAK-138: --- +1 > Move client/server packa

[jira] [Updated] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominique Pfister updated OAK-138: -- Description: As a further cleanup step in OAK-13, I'd like to move the packages o.a.j.mk.client a

[jira] [Created] (OAK-138) Move client/server package in oak-mk to separate project

Dominique Pfister created OAK-138: - Summary: Move client/server package in oak-mk to separate project Key: OAK-138 URL: https://issues.apache.org/jira/browse/OAK-138 Project: Jackrabbit Oak I