> effect. :( Renaming to build.properties looks to have solved this issue.
Yes, or tweak the .releng/build.xml to use a different build.properties.whatever file than the default. > Right.. If I mod JavaSE-1.6, J2SE-1.5, etc.. in my build-custom.properties > file then that should fix it locally, correct? Or do I need to modify > something else? When I use the settings that I sent in other msg, no joy. Yes, whatever you set in your build.xml / build.whatever.properties will override values in common.releng/server.properties and common.releng/build.properties. > My setup is all 64. And you're right, its just installed through update > manager. But as Mac OS doesn't provide libraries in standard way; i.e. > lre/lib/rt.jar, I've modified the JavaSE-1.6 entries, etc.. Instead I'm > using the jars that are specified Cool. If you want those added to the global definitions in server.properties so *everyone* gets them, then send me a patch and I'll review/commit it. > One thing I noted is that the compiler being used is actually Eclipse Java > Compiler 0.A06, 3.6.0 M1, Copyright IBM Corp 2000, 2009. All rights > reserved. Is that 64-bit? If not should I be specifying the Apple javac > somehow? No, to compile osgi stuff (eg., eclipse plugins) AFAIK the eclipse java compiler must be used because it's "smarter" than the pure java compiler w.r.t. dependency resolution and osgi relationships in manifests. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio Release Engineer :: Dash Athena http://nick.divbyzero.com _______________________________________________ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
