For now, at least, if you want to use the Grails feature, then you
must use M1 (that comes with STS), but if you are not using Grails
(ie- not installed), then you can add the update site as in regular
eclipse and perform a standard update.

We are working on making groovy with grails updatable to snapshots not
included with STS.

On Wed, Oct 28, 2009 at 12:09 PM, Burt Beckwith <burt@(protected):
> What's the best way to use a snapshot build in STS, or is STS limited to more formal releases? Should we just create an update site like in regular Eclipse - would that replace the M1 version that comes with STS?
>
> Burt
>
> On Wednesday 28 October 2009 3:04:23 pm Andrew Eisenberg wrote:
>> Hi all,
>>
>> The latest groovy-eclipse snapshot contains a few new features that
>> you might be interested in and I would like some feedback on.
>>
>> 1. Inferencing search:
>> Find references and other kinds of Java search now uses inferencing to
>> find Groovy elements.  For example, in the following code,
>> CTRL-Shift-G (find references) will properly locate all uses of the
>> x1() method, but will distinguish between First.x1() and Second.x1():
>>
>> class First {
>>     def x1 () { x1() }
>> }
>> class Second {
>>     def x1 () { x1() }
>> }
>> def val = new First()
>> val.x1()
>> val = new Second()
>> val.x1()
>>
>> This functionality is basic, but will be expanded on soon.  Next, I
>> will include category search, and also provide extension points so
>> that Grails (and other DSLs) can provide their own inferencing.  Also,
>> this functionality will become the foundation of all inferencing
>> throughout Groovy-Eclipse and will replace the current inferencing for
>> content assist and open type, so I need to get this right.  :)
>>
>> 2. Type content assist.
>> Content assist in scripts and closures now include type proposals.  I
>> had to disable JDT's type proposals (which only worked inside of
>> methods and classes) and replace it with a custom implementation that
>> will work anywhere.
>>
>> Import statements will be properly generated if required, and fully
>> qualified names will be used if necessary.  However, aliasing is not
>> fully supported.
>>
>> 3. Organize imports
>> Organize imports now is cognizant of generic types and type
>> parameters.  Also, aliasing is supported.
>>
>> Please provide feedback and I will continue to improve on functionality.
>>
>> --a
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

  http://xircles.codehaus.org/manage_email