[hibernate-issues] [Hibernate-JIRA] Commented: (HBX-589) Null Pointer Exception while generationg code

[Dan Madoni (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HBX-589?page=comments#action_23925 ] 

Dan Madoni commented on HBX-589:
--------------------------------

Yes sorry, I forgot to mention that the directory already exists and had always exised, so I ignored that early on thinking it was attributable to pre-release dialog box behavior. :)

I clicked on the Browse button to select the directory and the selection changed the Output directory setting from...

C:\workspace\hibenate-tools-test\src

...to a directory that is relative to the Eclipse workspace...

\hibenate-tools-test\src

...which made the error icon go away.

I then ran the tool again and it worked! Thanks!

So, I guess that in addition to the fact that I shouldn't so easily dismiss the error icon, the real problem here was that I used a full path, but it won't  work unless I have a path that is relative to my Eclipse workspace?

If this is by design, then there may be a doc bug, as the following passage appears in http://www.hibernate.org/hib_docs/tools/reference/en/html/plugins.html#d0e258 in describing what to specify for Output Directory:

"Path to a directory into where all output will be written by default. Be aware that existing files will be overwritten, so be sure to specify the correct directory."

I didn't see anything about a relative directory, so I apologize if I missed it. And of course, sorry for not having clicked the Browse button until you pointed out that error icon. :)

Thanks for your prompt attention!

> Null Pointer Exception while generationg code
> ---------------------------------------------
>
>          Key: HBX-589
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-589
>      Project: Hibernate Tools
>         Type: Bug

>     Versions: 3.1beta4
>     Reporter: Markus Junginger
>  Attachments: Neues Bild.jpg, scrnshot_launcher.jpg
>
>
> It was not possible to generate any artifacts. The given information does not explain anything.
> There should be more information about the exception - no stacktrace, etc. See attachment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira