Hi Darren, I agree that the missing / might be a bit cumbersome for new users. How about trying to load the file "as is", and if that fails, re-try loading it by prepending a / ? That should be reasonable and backwards-compatible... I'll implement this for jOOQ 3.3: https://github.com/jOOQ/jOOQ/issues/2932
Thanks for the suggestion! Lukas 2014/1/7 Darren S <[email protected]> > Just donned on my that that change would not really be backwards > compatible. To make it be backwards compatible you'd have to strip leading > /'s as ClassLoader.getResourceAsStream() will not accept a leading / > > Darren > > > On Monday, January 6, 2014 12:14:43 PM UTC-7, Darren S wrote: >> >> This is a random thing I came across. Obviously people have hit the >> issue of not putting a "/" in the beginning of the path for the codegen XML >> configuration and I see the code has a nice error message about this. If >> you change >> >> GenerationTool.class.getResourceAsStream(args[0]); >> >> to >> >> GenerationTool.class.getClassLoader().getResourceAsStream(args[0]); >> >> You shouldn't have that issue anymore. The classloader will just by >> default look in the classpath. This does mean that you won't be able to >> find XML files with paths relative to GenerationTool.class, but I'm not >> sure why anyone would want to do that. >> >> Darren >> >> >> -- > You received this message because you are subscribed to the Google Groups > "jOOQ User Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
