search

esbtools / event-handler

Notification in, document out.
GNU General Public License v3.0
3 stars 6 forks source link

Move documentEvent and eventHandlerConfig entities to own maven modules #69

Open alechenninger opened 8 years ago

alechenninger commented 8 years ago

This will make versioning / releasing easier

derek63 commented 8 years ago

Do you mean a separate GitHub project?

alechenninger commented 8 years ago

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 https://github.com/esbtools/event-handler/issues/69#issuecomment-248238260, or mute the thread https://github.com/notifications/unsubscribe-auth/ADVab0MHaelifCMPRPpPBgBz4t8gt_wTks5qr5nXgaJpZM4KAoav .

dcrissman commented 7 years ago

How will it make versioning easier?

alechenninger commented 7 years ago

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).