[jira] Commented: (VYSPER-95) Multi-module build for Vysper
[ https://issues.apache.org/jira/browse/VYSPER-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846846#action_12846846 ] Bernd Fondermann commented on VYSPER-95: Niklas, isn't this largely resolved? > Multi-module build for Vysper > - > > Key: VYSPER-95 > URL: https://issues.apache.org/jira/browse/VYSPER-95 > Project: VYSPER > Issue Type: Improvement >Reporter: Niklas Gustavsson >Assignee: Niklas Gustavsson > > The Vysper code base is already quite big and adding new XEPs will only make > it bigger. We should therefore look into breaking Vysper into modules, > possibly with bigger XEPs going into their own module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (VYSPER-95) Multi-module build for Vysper
[ https://issues.apache.org/jira/browse/VYSPER-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733553#action_12733553 ] Bernd Fondermann commented on VYSPER-95: Splitting out every single XEP is a step too far, AFAIAC. For example, ServiceDiscoveryModule and RosterModule are practically core modules, although technically they could be replaced with other implementations. Some other modules are too small to be separate. So, yes, let's separate PubSub, Spec compliance and all the other XEPs into another module. > Multi-module build for Vysper > - > > Key: VYSPER-95 > URL: https://issues.apache.org/jira/browse/VYSPER-95 > Project: VYSPER > Issue Type: Improvement >Reporter: Niklas Gustavsson >Assignee: Niklas Gustavsson > > The Vysper code base is already quite big and adding new XEPs will only make > it bigger. We should therefore look into breaking Vysper into modules, > possibly with bigger XEPs going into their own module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (VYSPER-95) Multi-module build for Vysper
[ https://issues.apache.org/jira/browse/VYSPER-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733221#action_12733221 ] Niklas Gustavsson commented on VYSPER-95: - First step complete (setting up the Maven modularized build). Next step would be to break out modules from core. Spec compliance (per vote) and pubsub would seem obvious. Anything else? Would we even like one module per XEP? We will also have to look into the distribution module to create a nicely packed up runnable distribution of Vysper, but that we can probably do later. > Multi-module build for Vysper > - > > Key: VYSPER-95 > URL: https://issues.apache.org/jira/browse/VYSPER-95 > Project: VYSPER > Issue Type: Improvement >Reporter: Niklas Gustavsson >Assignee: Niklas Gustavsson > > The Vysper code base is already quite big and adding new XEPs will only make > it bigger. We should therefore look into breaking Vysper into modules, > possibly with bigger XEPs going into their own module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (VYSPER-95) Multi-module build for Vysper
[ https://issues.apache.org/jira/browse/VYSPER-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732861#action_12732861 ] Niklas Gustavsson commented on VYSPER-95: - Excellent, that's what I will do. > Multi-module build for Vysper > - > > Key: VYSPER-95 > URL: https://issues.apache.org/jira/browse/VYSPER-95 > Project: VYSPER > Issue Type: Improvement >Reporter: Niklas Gustavsson >Assignee: Niklas Gustavsson > > The Vysper code base is already quite big and adding new XEPs will only make > it bigger. We should therefore look into breaking Vysper into modules, > possibly with bigger XEPs going into their own module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (VYSPER-95) Multi-module build for Vysper
[ https://issues.apache.org/jira/browse/VYSPER-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732844#action_12732844 ] Bernd Fondermann commented on VYSPER-95: The latter example in my last comment then would go to a module like httpbridging/bosh/servlet - or whatever. > Multi-module build for Vysper > - > > Key: VYSPER-95 > URL: https://issues.apache.org/jira/browse/VYSPER-95 > Project: VYSPER > Issue Type: Improvement >Reporter: Niklas Gustavsson >Assignee: Niklas Gustavsson > > The Vysper code base is already quite big and adding new XEPs will only make > it bigger. We should therefore look into breaking Vysper into modules, > possibly with bigger XEPs going into their own module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (VYSPER-95) Multi-module build for Vysper
[ https://issues.apache.org/jira/browse/VYSPER-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732843#action_12732843 ] Bernd Fondermann commented on VYSPER-95: I'd go for server/core. Then we can have server/extension/XEP-, server/extension/googlewave. And we can also have things sitting side-by-side of a server, like for example code providing the bridging between HTTP and XMPP in BOSH, which is part of a WebServer. > Multi-module build for Vysper > - > > Key: VYSPER-95 > URL: https://issues.apache.org/jira/browse/VYSPER-95 > Project: VYSPER > Issue Type: Improvement >Reporter: Niklas Gustavsson >Assignee: Niklas Gustavsson > > The Vysper code base is already quite big and adding new XEPs will only make > it bigger. We should therefore look into breaking Vysper into modules, > possibly with bigger XEPs going into their own module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (VYSPER-95) Multi-module build for Vysper
[ https://issues.apache.org/jira/browse/VYSPER-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732445#action_12732445 ] Niklas Gustavsson commented on VYSPER-95: - I will be away over the weekend, but when I'm back I'll set up a multimodule build. That means current trunk will have to be moved to a submodule, what should we call that? "core"? "server"? Something else? > Multi-module build for Vysper > - > > Key: VYSPER-95 > URL: https://issues.apache.org/jira/browse/VYSPER-95 > Project: VYSPER > Issue Type: Improvement >Reporter: Niklas Gustavsson >Assignee: Niklas Gustavsson > > The Vysper code base is already quite big and adding new XEPs will only make > it bigger. We should therefore look into breaking Vysper into modules, > possibly with bigger XEPs going into their own module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (VYSPER-95) Multi-module build for Vysper
[ https://issues.apache.org/jira/browse/VYSPER-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732427#action_12732427 ] Bernd Fondermann commented on VYSPER-95: +1 > Multi-module build for Vysper > - > > Key: VYSPER-95 > URL: https://issues.apache.org/jira/browse/VYSPER-95 > Project: VYSPER > Issue Type: Improvement >Reporter: Niklas Gustavsson >Assignee: Niklas Gustavsson > > The Vysper code base is already quite big and adding new XEPs will only make > it bigger. We should therefore look into breaking Vysper into modules, > possibly with bigger XEPs going into their own module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
