[
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.
