Split components in separate composer packages

[broadway]

Split components in separate composer packages

[haampie]

Another reason; the filter query used in the ElasticSearch repository is deprecated in ElasticSearch 2.3+

https://www.elastic.co/guide/en/elasticsearch/reference/2.3/breaking_20_query_dsl_changes.html#_literal_filtered_literal_query_and_literal_query_literal_filter_deprecated

[asm89]

We fully agree and splitting up the repository in separate components has always been the plan. For now we'd like to keep things in one repository and once things stabilize some more we'll probably split out each component to a separate repository.

[asm89]

We'd like to split out the Symfony bundle on a shorter term.

[GazEdge]

agree with splitting things out. I've just forked the project and really like what I'm seeing, but really only want the event store and handlers.

Going through the process now of looking to see how easy it is to decouple those elements from the whole framework

[harikt]

@asm89 split to make the other repos accept PR's . So people don't need to bother about other code.

[asm89]

@cboden linked me the scripts the react project was using previously: https://github.com/reactphp/react/tree/17044db0ab6a9c145fb1ac40822c5c17d045dc36/scripts

[ruudk]

+1

I really want to only use the Event Store for now...

[asm89]

If anyone has concrete ideas about how to do this, I'd be happy to look into it. As said before, we'd like to stabilize the components a bit more before doing a final split into separate repositories. We could go the subtree split way, but that can be quite cumbersome as well?

[harikt]

The recent zf3 will be splitting to repos which can accepts PR . If you are still with the subtree split, may be you should ping Fabien, Taylor, Beau or Stof for the same.

[haampie]

Some inactivity here, but there are some solid reasons I encountered to proceed. The doctrine/mongodb package is currently problematic when using PHP7, since the doctrine package relies on the old ext-mongo extension, while PHP7 is (only?) shipped with ext-mongodb. See doctrine/mongodb#239 which runs since December 2015.

Of course I can simply remove the mongodb dev dependency, but it would be reassuring to run all of the project tests rather than excluding some.

It shouldn't be too much of a hassle to split specific implementations (DBal / ElasticSearch / MongoDB) from interfaces, right? Except for InMemory implementations maybe :)

edit: well, splitting is somewhat harder than expected... ;)

[othillo]

Closing this, because at the moment we have split the

• Symfony bundle: https://github.com/broadway/broadway-bundle
• Saga: https://github.com/broadway/broadway-saga
• DBAL event store: https://github.com/broadway/event-store-dbal (PR: https://github.com/broadway/event-store-dbal/pull/1/files)
• Elasticsearch read models: https://github.com/broadway/read-model-elasticsearch (PR: broadway/read-model-elasticsearch#1)

Some still need to be merged but then we have split at least the all the implementations.

[harikt]

no composer.json ?

[othillo]

@harikt these PR's are still open:

• broadway/event-store-dbal#1
• broadway/read-model-elasticsearch#1

[harikt]

@othillo any reason it is still waiting ?

[othillo]

it needs code review and merge, /cc @broadway/broadway ;)