Max, I've posted jira HBX-228.
The root cause of some of my trouble is: confusion and ignorance, but that's not to say all the trouble is gone. If you could just take a look at the patch files in the jira issue and resolve, then I'll be happier.
Sorry for the confusion. John
Max Rydahl Andersen wrote:
On Fri, 15 Apr 2005 21:25:03 +0200, John Franey <[EMAIL PROTECTED]> wrote:
Max, and all,
I've got the autobuild running to a very minimal level.
Nice
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?
Yes please. Add them as *patches*, not just complete files as otherwise I have
no good chance of detecting what the changes are.
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.
hmm - ok these should not but needed, except org.objectweb.asm which sounds reasonable.
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.
It looks like you are using 3.1M5 and not 3.1M6 ? These changes were done do comply with the new improvements in the M6 runtime engine.
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.
Hmm...again need to see that patch to truly follow this.
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.
yes - please just use a recent I-build from WTP and it should work now.
-max
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
------------------------------------------------------- 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
