Skip to content

Resolve the fixed version number in the Maven POMs #75

@Zarquan

Description

@Zarquan

At the moment we have a fixed version number in the Maven POMs for the generated code:

<version>1.0.3-SNAPSHOT</version>

and
<version>1.0.3-SNAPSHOT</version>

Ideally we want the POM version to reflect the version number in the OpenAPI specification.

If we refactor the Java builds to use the POM generated by the code generator, then we can set the version number as a parameter to the generator. Alternatively, we could add a prepare step that starts with a template-pom.xml file, and generates the actual pom.xml file used by the Maven build step.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions