Skip to content

Is using an alternate PARENT_PACKAGE currently supported? #1

Description

@darach

Hi folk,

Perhaps this is user error, but using an alternate PARENT_PACKAGE in the codec
generation results in failing acceptance tests after mopping up any obvious import
issues:

@@ -190,6 +194,9 @@ project(':fix-44-codecs') {
         main = 'uk.co.real_logic.artio.dictionary.CodecGenerationTool'
         classpath = sourceSets.main.runtimeClasspath
         args generatedDir, '../../quickfixj/quickfixj-messages/quickfixj-messages-fix44/src/main/resources/FIX44.xml'
+        systemProperties = [
+            PARENT_PACKAGE: "foo.bar"
+        ]

         outputs.dir generatedDir
     }

It seems logical to use different parent packages for different FIX dialects but it looks like a uk.co.real_logic.artio parent package is assumed at least at the moment, or is it a missing
configuration step, for example, or do some artio packages like Session need to be tweaked
to use different Header Encoders etc..?

Cheers,

Darach.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions