[
https://issues.apache.org/jira/browse/PLC4X-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17389310#comment-17389310
]
Christofer Dutz commented on PLC4X-307:
---------------------------------------
And as this would have an effect on the build-tools repository (That's where
the maven plugin is located), we should at least add the extension to the maven
plugin as soon as possible, as we were already tinking of releasing this. Would
be a shame to have to re-do that soon after.
> Permit customized package names for code generation
> ---------------------------------------------------
>
> Key: PLC4X-307
> URL: https://issues.apache.org/jira/browse/PLC4X-307
> Project: Apache PLC4X
> Issue Type: New Feature
> Components: Code-Generation
> Affects Versions: 0.9.0
> Reporter: Łukasz Dywicki
> Priority: Major
> Labels: low-hanging-fruit
>
> Currently code generation assumes static naming convention. For example Java
> templates always put generated code in
> {{org.apache.plc4x.<language=java>,<protocol>,<flavor=readwrite>}}, where
> protocol is defined via SPI provider.
> This assumption works fine for our own drivers, however it also leads to
> several assumptions in other places. For example a test framework does
> silently assume that types used for serialization/deserialization are always
> in above.
> While use can customize language templates or "helper" SPI he can not easily
> adjust ser/deser test framework internals. A better handling of user defined
> packages might promote wider use of tools developed by project.
> Currently issue is mainly specific to Java (not sure about Go). Other
> languages and their test frameworks might require adjustments as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
