[PLC4X-307] Permit customized package names for code generation

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.9.0
• Fix Version/s: 0.9.0
• Component/s: Code-Generation
• Labels: low-hanging-fruit

Language

Java

• Assignee: Łukasz Dywicki
• Reporter: Łukasz Dywicki
• Created: 28/Jul/21 16:56
• Updated: 09/Aug/21 11:04
• Resolved: 09/Aug/21 11:04

Description

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.

Issue Links

• links to: GitHub Pull Request #6
• links to: GitHub Pull Request #263