...
Also briefly looked at the dev forum posting on the shared library. We're all in agreement that Darius' point about DTOs being published by the Service that owns the resource makes the most sense. We also talked about more pure utility classes that aren't owned by a single Service (e.g. Message, ValidationMessageException, etc) that would still likely live in the shared library (which sparked the discussion). We agreed that Service's publishing their DTOs to Maven may not be on the critical path for 3.0, however it'd be a nice to have and it's likely not a huge lift to get there (e.g. we have a pattern we've worked on in the Example service). A ticket should be added to properly track this work.
Action items
- Paweł Gesek to add a ticket for service's publishing their DTOs to Maven
- Josh Zamor to post to dev forum seeking agenda items and volunteer for moderator for Feb 7 meeting