| Groovy support, Eclipse 3.6 [message #536287] |
Thu, 27 May 2010 10:24  |
Eclipse User |
|
|
|
Hello people
I was wondering what the state is at the moment regarding Groovy compilation
within a headless Buckminster?
If it is possible, will I need to migrate my RCP app to Eclipse 3.6, and be
using Buckminster 3.6 in order to setup an automated headless build with
components that are written in Groovy?
Thanks
"Old" Greg
|
|
|
|
| Re: Groovy support, Eclipse 3.6 [message #536479 is a reply to message #536365] |
Fri, 28 May 2010 08:29  |
| Eclipse User |
|
|
|
Greg,
Good news. I just retried installing the Groovy-Eclipse plugins and ran a
few tests. It seems that the UI dependency issues have been resolved. You
can try it out with this command *after* you have performed a regular
Buckminster headless (3.6) install:
../director/director -r
http://dist.codehaus.org/groovy/distributions/greclipse/snap shot/e3.6/ \
-d /path/to/your/buckminster/installation \
-p Buckminster \
-i org.codehaus.groovy \
-i org.eclipse.jdt.core \
-i org.eclipse.jdt.groovy.core \
-i org.codehaus.groovy.eclipse.codebrowsing
With this setup I was able to compile Groovy code simply by invoking the
Buckminster "build" command, which invokes the regular Groovy Eclipse
builder. I could also run a launch config that executes a Groovy script
class' "main()" method. Finally, I could successfully run Groovy JUnit
tests.
Cheers,
Achim
Achim Demelt wrote:
> Hi Greg,
>
> It turned out that there are only some UI-dependencies left to fix in the
> Groovy-Eclipse plug-ins. Once these are sorted out, Groovy support should
> be ready for prime time. To make installation easier, Andrew may provide a
> headless feature if he can find the time to do it. But it's also possible
> to install individual bundles into Buckminster, so even without that
> feature we're good to go once the UI dependencies are fixed. You can
> follow our discussion here: http://jira.codehaus.org/browse/GRECLIPSE-716
>
> As to your second question: Your headless Buckminster will definitely have
> to be based on 3.6. However, you can still target your RCP app on 3.5.
>
> Achim
>
> geejay wrote:
>
>> Hello people
>>
>> I was wondering what the state is at the moment regarding Groovy
>> compilation within a headless Buckminster?
>>
>> If it is possible, will I need to migrate my RCP app to Eclipse 3.6, and
>> be using Buckminster 3.6 in order to setup an automated headless build
>> with components that are written in Groovy?
>>
>> Thanks
>>
>> "Old" Greg
|
|
|
| Re: Groovy support, Eclipse 3.6 [message #543198 is a reply to message #536479] |
Mon, 28 June 2010 12:33 |
| Eclipse User |
|
|
|
Works like a charm.
Thanks
Greg
"Achim Demelt" <a.demelt@exxcellent.de> wrote in message
news:htodju$5ra$1@build.eclipse.org...
> Greg,
>
> Good news. I just retried installing the Groovy-Eclipse plugins and ran a
> few tests. It seems that the UI dependency issues have been resolved. You
> can try it out with this command *after* you have performed a regular
> Buckminster headless (3.6) install:
>
> ./director/director -r
> http://dist.codehaus.org/groovy/distributions/greclipse/snap shot/e3.6/ \
> -d /path/to/your/buckminster/installation \
> -p Buckminster \
> -i org.codehaus.groovy \
> -i org.eclipse.jdt.core \
> -i org.eclipse.jdt.groovy.core \
> -i org.codehaus.groovy.eclipse.codebrowsing
>
> With this setup I was able to compile Groovy code simply by invoking the
> Buckminster "build" command, which invokes the regular Groovy Eclipse
> builder. I could also run a launch config that executes a Groovy script
> class' "main()" method. Finally, I could successfully run Groovy JUnit
> tests.
>
> Cheers,
> Achim
>
> Achim Demelt wrote:
>
>> Hi Greg,
>>
>> It turned out that there are only some UI-dependencies left to fix in the
>> Groovy-Eclipse plug-ins. Once these are sorted out, Groovy support should
>> be ready for prime time. To make installation easier, Andrew may provide
>> a
>> headless feature if he can find the time to do it. But it's also possible
>> to install individual bundles into Buckminster, so even without that
>> feature we're good to go once the UI dependencies are fixed. You can
>> follow our discussion here: http://jira.codehaus.org/browse/GRECLIPSE-716
>>
>> As to your second question: Your headless Buckminster will definitely
>> have
>> to be based on 3.6. However, you can still target your RCP app on 3.5.
>>
>> Achim
>>
>> geejay wrote:
>>
>>> Hello people
>>>
>>> I was wondering what the state is at the moment regarding Groovy
>>> compilation within a headless Buckminster?
>>>
>>> If it is possible, will I need to migrate my RCP app to Eclipse 3.6, and
>>> be using Buckminster 3.6 in order to setup an automated headless build
>>> with components that are written in Groovy?
>>>
>>> Thanks
>>>
>>> "Old" Greg
>
|
|
|
Powered by
FUDForum. Page generated in 0.04611 seconds
Home