Max, and all,
I've got the autobuild running to a very minimal level. Its properly configured, it checks-out source and tries to generate build.xml scripts in each plugin. Unfortunately, at the time I was running this, there are failures when it tries to generate build.xml scripts for each plugin. I would have gone farther, but I'm requesting some checkins to the extenstions cvs tree. Once these are in then I'll go back in and write the prebuild callouts that would copy needed libraries into org.hibernate.eclise/lib.
The following problems with the source at HEAD of cvs tree were verified using the eclipse ui and then corrected in my local copy. For each affected file, I put the revision that was HEAD during the time I was truing to get this to work (week of 10 April). Should I put these in JIRA?
1) in org.hibernate.eclipse: META-INF/MANIFEST.MF (cvs r 1.1) names packages that are not present in jar files copied in by 'hibernate-build.xml update': org.hibernate.tool.cfg2hbm, org.hibernate.tool.test.jdbc2cfg, org.objectweb.asm, persistentclasses. Removing these from the file resolves this build problem, and pushes the issue to runtime.
2) In org.hibernate.ecplise.console: plugin.xml (cvs r 1.11) does not have id, version, and name attributes. Restoring values from r 1.10 resolves this build problem. Also, plugin.xml does not have any dependencies. Restoring dependency list from r 1.10 resolves this build problem. In addtion to r1.10, these plugins are new dependencies: org.eclipse.ui.editors, org.eclipse.jdt.ui.
3) In org.hibernate.eclipse.console.test: plugin.xml (cvs r1.2) does not have id, version and name. Restoring values from r1.1 resolves this build problem. Also, plugin.xml has no dependencies. Adding org.junit resolves build problem.
4) org.hibernate.eclipse.mapper: I found this tree was moving underneath me on 15-april, so I stopped trying to make it work. But, the plugin.xml is incomplete: it also lacks that id, version and name attributes.
As a matter of status: I tried to patch these locally and continue the build process. but the PDE Build was unable to resolve a plugin in wst 1.0M3 (needed by hibernate's mapper plugin). It complained of a corrupt file in the wst plugin. I have not yet isolated the problem, but since you are upgrading to M4 soon, and the HEAD in mapper on 15-april indicate dependency on M4, I'll move up to M4 too.
John
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
