gsergiu wrote:
-- From this text I unserstand that I have to checkout the HibernateExt and to run the build.bat, ... but this is not working because of classpath problems.
Can you elaborate on problems?
I was doing a copy paste of the information from the build hibernate tools webpage
http://www.hibernate.org/268.html , that says that after chacking out the HibernateExt folder you should run the build.bat command. But running this script fails becuse of classpath problems.
It seems that hibernate tools are dependent on libraries found in hibernate/lib folder.
gsergiu wrote:
-- from this text I understand that building hibernate is optional, that is right ... but the tools project needs libraries from hibernate, I asume (anyway this was my solution)
Using the hibernate.jar file found at
http://download.jboss.org/jbosside/builds/nightly/gsergiu wrote:
2. there is a javaCompile methos in TestHelper class that usses com.sun.tools.javac.Main.compile() method, that will still not be in the classpath (tools.jar exists in jdk, but not in jre I asume).
Anyway the method is never used (except in the case of beeing used over refactoring, that I doubt),
Are you running the tests? If not, you don't need this. If so, the dep is under testLibs.
Even if I run the tests or not, Eclipse is placing the tests, eclipse identifies the tests folder as a source folder and after compilation I get an error (in Eclipse), and that makes me angry.
So .. I propose to remove that method, since it is not used, or to place some documentation that the tools.jar needs to be added to classpath.
gsergiu wrote:
3 Is it possible to use some defaults so that the code is compilable even without running the tests?. It doesn't look very attractive for me the following code:
/**
* @author max
* NOTE: this file cannot compile without the tests being run since its dependent on its output.
*/
public interface HelloWorld extends generated.BaseHelloWorld {
}
The tools are compilable w/out running tests. The interface you don't find attractive is a part of the tests, this is why it was put in a folder called testoutputdependent .
It stiill generates a compilation error.
If the generated.BaseHelloWorld is replaced with BaseHelloWorld, the error is removed ...
PS: I don't know how do you feel, but I hate when my Eclipse errors, specially when they are missconfigurations