I tested the build of the eclipse plugin from a fresh checkout. It worked fine on Windows and on Linux. Unfortunately I haven't got a Mac to see what's wrong on OS X...
Cheers, Felix > -----Original Message----- > From: Dan North [mailto:[EMAIL PROTECTED] > Sent: 04 January 2007 19:16 > To: [email protected] > Subject: Re: [jbehave-dev] Re: changed folder layout > > At first glance, it sounds like $JAVA_HOME/bin isn't on your path for > the <javac> task. Could be completely wrong of course :) > > Perhaps the ant script sets up the java environment correctly but > doesn't pass the environment onto the ant tasks. > > Cheers, > Dan > > Mauro Talevi wrote: > > Felix Leipold wrote: > >> > >> > >> Okay there is a fundamental problem. I'll check if I manage to > >> compile it on > >> linux. Then I'll come back to you... > >> > > > > More generally, IMO it would be better to be able to build the eclipse > > plugin in a headless mode, ie without having eclipse installed. > > > > Without having much experience in building eclipse plugins, it would > > seem that all we need is to have the eclipse startup.jar in the > > classpath. So we can just copy the Eclipse 3.2 jar to > > lib/eclipse-startup-3.2.jar and avoid all the issue of the Eclipse > > install dir. > > > > The eclipse build would then produce a plugin update site which can be > > used by any platform. > > > > Thoughts? > > > > Cheers > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
