GitHub user splatch added a comment to the discussion: Adding "Test-Containers" to the extras repo?
Test containers have support for on-demand creation of containers, so they can be built on the fly as test goes. It slows down process, but avoids necessity to release containers prior test. Obviously it locks down container to just one language and limits its portability, but if container is for our own use during test phase, it doesn't have get public. That's as far I remember trouble with Milo stuff, that we should abstain from re-publish non EPL stuff. GitHub link: https://github.com/apache/plc4x/discussions/1521#discussioncomment-9098393 ---- This is an automatically sent email for dev@plc4x.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@plc4x.apache.org
