Re: Pre-processing during build
От | Mark Rotteveel |
---|---|
Тема | Re: Pre-processing during build |
Дата | |
Msg-id | ba57c14862b915a79a69de9089df736e@imap.procolix.com обсуждение исходный текст |
Ответ на | Re: Pre-processing during build (Dave Cramer <pg@fastcrypt.com>) |
Ответы |
Re: Pre-processing during build
Re: Pre-processing during build |
Список | pgsql-jdbc |
On Wed, 17 Jun 2015 06:15:47 -0400, Dave Cramer <pg@fastcrypt.com> wrote: > On 17 June 2015 at 03:07, Mark Rotteveel <mark@lawinegevaar.nl> wrote: > >> On Wed, 17 Jun 2015 00:02:40 +0300, Vladimir Sitnikov >> <sitnikov.vladimir@gmail.com> wrote: >> > 2015-06-16 22:30 GMT+03:00 Markus KARG <markus@headcrashing.eu>: >> >> The answer is pretty simple: Try it out. :-) >> >> >> >> Just compile a JRE 8 class down to byte code level 6 and load it on >> Java >> >> level 7. That's what I proposed. Nothing else. It really bet will work >> >> unless you try to INSTANTIATE JRE-only classes, but it should LOAD. >> >> And >> >> nothing more we need. >> > >> > Markus, can you please be more explicit in your suggestion? >> > >> > I did try a simple "Hello, world" and it does not run in stock JDKs of >> > MacOS: https://gist.github.com/vlsi/aeeb4a61d9c2b67ad213 >> > Even if you manage to make that fly, that would be built on sand. >> >> Good example: it demonstrates at least that using reflection (eg >> getDeclaredMethods; or in this case privateGetDeclaredMethods) will lead >> to >> a NoClassDefFoundError. >> >> > I'm not sure this is a great example as Optional itself is a java 8 > construct. Yes, and so is java.sql.SQLType. So if this doesn't work for Optional, it also won't work for SQLType. > Either way Spring is able to do this, as are others? Spring uses a lot of reflection, proxies, byte code generation, etc to get things done. I am not sure if you want to go that way. Mark
В списке pgsql-jdbc по дате отправления: