Move documentEvent and eventHandlerConfig entities to own maven modules

[alechenninger]

This will make versioning / releasing easier

[derek63]

Do you mean a separate GitHub project?

[alechenninger]

Separate maven projects, I meant.

On Tue, Sep 20, 2016, 4:31 AM Derek Haynes notifications@github.com wrote:

Do you mean a separate GitHub project?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#69 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADVab0MHaelifCMPRPpPBgBz4t8gt_wTks5qr5nXgaJpZM4KAoav
.

[dcrissman]

How will it make versioning easier?

[alechenninger]

We generate the metadata for these entities using a version in code. This means there are multiple versions to update when you release: the maven project version, and the entity versions.

There is a feature of the metadata generation that can just use the maven pom version if it is added to the jar manifest. If DocumentEventEntity and EventHandlerConfigEntity where their own maven projects, then they could just inherit the maven project version, and then we could remove a manual, error-prone step from our release process (see the README.md).