jhoward-lm

@nscuro Here's a working example; I just threw everything into `hyades-apiserver` under `org.dependencytrack.model` because it was easier to manage. A few highlights: - `PermissionGeneric` is just a placeholder name to...

On a somewhat related note, a similar inheritance pattern could be applied to the 3 user models (minus the use of generics). Using `InheritanceStrategy.SUPERCLASS_TABLE` with a discriminator column could theoretically...

> Oh nice, that sounds promising! @nscuro Here's a [gist](https://gist.github.com/jhoward-lm/39ae80d40ad3ad3b40fe7f17f79e7243) with a rough example of that if you're interested. If you end up creating an issue for consolidating user tables...

@nscuro I don't really have any strong opinions about it; if implementing `resource` as a `String` is easier to work with and provides better typing support then that makes perfect...

@nscuro Within the context of hyades-apiserver with Alpine now ingested, does that change your thoughts on using an enum for `resource`? I think the generic enum type would no longer...