I kinda feel like this might be paving the cow path, but I wonder if we might want some special treatment in the TC eclipse plugin for TIMs that have compile time APIs. Seems like specially tagged TIMs could be auto-added to the classpath of the project.
What about something similar in the tc-maven-plugin? > -----Original Message----- > From: tc-dev-boun...@lists.terracotta.org [mailto:tc-dev- > boun...@lists.terracotta.org] On Behalf Of Geert Bevin > Sent: Friday, January 30, 2009 2:07 AM > To: tc-dev@lists.terracotta.org > 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? > > -- > Geert Bevin > Terracotta - http://www.terracotta.org > Uwyn "Use what you need" - http://uwyn.com > RIFE Java application framework - http://rifers.org > Flytecase Band - http://flytecase.be > Music and words - http://gbevin.com > > _______________________________________________ > 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
