I did think about using the maven dependency plugin combined with unpack to solve this issue however I was thinking I might not be the only one confronted with this situation. If you provide a jar with those classes it might promote reuse and avoid people having to reimplement the same solution over and over again. Then again I have a hard time estimating if there would be many in this situation. I'm in this situation because we are migrating from jee5 to jee6.
In jee5 there is no validation so we bundle it but in jee there is so javax validation is now of provided scope in maven. ==> Hibernate annotations are not known.
|
