Uploaded image for project: 'Apache PLC4X'
  1. Apache PLC4X
  2. PLC4X-307

Permit customized package names for code generation

Details

    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.

      Attachments

        Activity

          People

            ldywicki Łukasz Dywicki
            ldywicki Łukasz Dywicki
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment