I see, discoverability is a good point. The DTDs don't seem a blocker to me. It's doable to create a clean room implementation for those DTDs based on the existing body of Hibernate configuration XML files.
We are also in talks with them to see if they could relicense the DTDs. The big problem is the Hibernate JARs which we will not be able to distribute under Apache. So, we might be able to provide some Hibernate "configuration" (via the DTDs) out of the box but no Hibernate execution. --emi On Wed, May 31, 2017 at 2:07 PM, Neil C Smith <[email protected] > wrote: > Hi, > > On Wed, May 31, 2017 at 10:38 AM Emilian Bold <[email protected]> > wrote: > > > There is an older thread about the Plugin Portal which will be handled > > outside Apache. > > > > You could revive that thread or start another one. > > > > Sorry, I wasn't intending that question to be entirely devoid of the > context of this thread. I probably agree with Geertjan with moving this > out into a plugin outside of Apache, but hey I've never used it! :-) In > general, moving support for third-party libraries into plugins might make > sense, but I'm also concerned at us adding barriers for end users. > Therefore ease of discovery of previously built-in features, how the plugin > portal works longer term, UI changes to support that, etc. feel relevant to > me in making decisions on this sort of thing. > > I think approaching Hibernate and asking for clarification / relicensing of > the DTDs makes sense anyway, and useful even if this becomes a plugin. And > it seems odd to license DTDs in that way. If relicensing is an option, > then it might be easier/better to look at this again later. > > Incidentally, given that this would be running on the JDK anyway, how > feasible is doing the build of these classes on first run rather than at > build time? > > Best wishes, > > Neil > -- > Neil C Smith > Artist & Technologist > www.neilcsmith.net > > Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org >
