I do this all the time for annotations - I build a maven project and then use:
$ mvn eclipse:eclipse which generates the eclipse project with the proper compile and build classpath. Annotations is just one example of a TIM that is a compile time dependency. ----- Original Message ----- From: "Walter Harley" <whar...@terracottatech.com> To: tc-dev@lists.terracotta.org Sent: Friday, January 30, 2009 9:42:27 AM GMT -08:00 US/Canada Pacific Subject: Re: [tc-dev] ConcurrentStringMap and eclipse Sorry, my rant was mis-targeted, I thought Steve was talking about getting source, not binary. If you're talking about getting the binaries of a TIM onto the build path of a non-Maven project, yeah, just include the .jar. For a Maven project, I assume you'd want to put the TIM into your Maven dependencies. On Jan 30, 2009, at 9:35 AM, Walter Harley wrote: > Has anyone who thinks this should work actually seen it working? This > is Maven we're talking about... > > The Eclipse Maven classpath container does not seem to do a very good > job with source dependencies. A lot of the time it wants to resolve > to the binaries in the repository, rather than to the source. I > believe we would need to export source jars for our various Maven > modules for this to work correctly. I have NOT been able to get > source dependencies working for Terracotta itself nor for things like > ehcache or Hibernate; it does work for some dependent TIMs, sometimes. > > If there's a way to make this work reliably I'd love to learn it. I > spent some time searching the web and didn't find anything useful. > > > On Jan 30, 2009, at 6:11 AM, Alex Miller wrote: > >> Either of those should work. It's treated just like a normal java >> library so anything like that will apply. >> >> >> ----- Original Message ----- >> From: "Geert Bevin" <gbe...@terracottatech.com> >> To: tc-dev@lists.terracotta.org >> Sent: Friday, January 30, 2009 4:06:49 AM GMT -06:00 US/Canada >> Central >> Subject: Re: [tc-dev] ConcurrentStringMap and eclipse >> >> If you set it up as a Maven dependency and use the project as a Maven >> project in Eclipse, it should automatically be added to your build >> path. Otherwise, the manual method should work just fine. >> >> On 30 Jan 2009, at 11:03, Steven Harris wrote: >> >>> When using a tim that has an api to it, what is the proper way in >>> eclipse to have that api in your build path. >>> Is it just the old standby add external jar (which I did and worked) >>> or is their something simpler? > _______________________________________________ > tc-dev mailing list > tc-dev@lists.terracotta.org > http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
_______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
