Haus Chores

Update Groovy-Eclipse buikder

Details

  • Type: Improvement Improvement
  • Status: In Progress In Progress
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: short-term
  • Fix Version/s: None
  • Component/s: Bamboo
  • Labels:
    None
  • Number of attachments :
    0

Description

I've tried to avoid this for too long. We have been building groovy-eclipse using Eclipse 3.4. It is very, very old. Until now, things have been working fine, but now that we are trying to build an Eclipse 4.2 based groovy-eclipse, things are just not working. I need to update the builder to Eclipse 3.7.

Here are the steps to do it:

1. unzip /opt/eclipse/src/eclipse-SDK-3.7RC4-linux-gtk-x86_64.tar.gz to the proper location as described here: https://docs.codehaus.org/display/DESPOTS/CI+-+Eclipse Please keep the old zip file as it is still being used in other builds.

2. Install groovy-eclipse into the unzipped Eclipse, using the p2 director application:

http://wiki.eclipse.org/Equinox_p2_director_application/Examples/Install_into_eclipse_using_SDKProfile
./eclipse/eclipse -consoleLog -clean -data /tmp/workspace \
   -application org.eclipse.equinox.p2.director \
   -repository http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.7/ \
   -installIU org.codehaus.groovy.eclipse.feature.feature.group

3a. Validate by checking that groovy-eclipse is installed

./eclipse/eclipse -consoleLog -clean -data /tmpt/workspace -console

3b. when the osgi console appears, type: start org.codehaus.groovy.eclipse.ui and you should get no errors.

If you are getting errors during the install because of firewall/network issues, you can use a zipped version of groovy eclipse.

  1. Download the most recent zip from http://ci.repository.codehaus.org/greclipse/snapshot/e37/old
  2. Upload it to the bamboo server and unzip. Replace the {[http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.7/}} url with a url to the unzipped update site (eg- file:/tmp/greclipse_update_site

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ben Walding added a comment -

I'll take care of this later this week - getting smashed by other projects at the moment.

If only it were a one liner!

Show
Ben Walding added a comment - I'll take care of this later this week - getting smashed by other projects at the moment. If only it were a one liner!
Hide
Permalink
Andrew Eisenberg added a comment -

Any progress on this issue?

Wish it were easier to do. I'd do it myself if I could.

Show
Andrew Eisenberg added a comment - Any progress on this issue? Wish it were easier to do. I'd do it myself if I could.
Hide
Permalink
Ben Walding added a comment -

Done - I hope.

Please check and let me know.

(I have coded it as a Chef recipe; so upgrades are relatively straight forward now)

[root@codehaus04 eclipse-SDK-3.7RC4-linux-gtk]# ./eclipse -clean -console

osgi> ss org.codehaus.groovy

Framework is launched.

id  State       Bundle
1 RESOLVED    org.codehaus.groovy.frameworkadapter_2.6.1.xx-20120221-1800-e37
              Master=0
16  <<LAZY>>    org.codehaus.groovy_1.7.10.xx-20120221-1800-e37
17  RESOLVED    org.codehaus.groovy.eclipse_2.6.1.xx-20120221-1800-e37
18  <<LAZY>>    org.codehaus.groovy.eclipse.ant_2.6.1.xx-20120221-1800-e37
19  <<LAZY>>    org.codehaus.groovy.eclipse.astviews_2.6.1.xx-20120221-1800-e37
20  <<LAZY>>    org.codehaus.groovy.eclipse.codeassist.completion_2.6.1.xx-20120221-1800-e37
21  <<LAZY>>    org.codehaus.groovy.eclipse.codebrowsing_2.6.1.xx-20120221-1800-e37
22  <<LAZY>>    org.codehaus.groovy.eclipse.core_2.6.1.xx-20120221-1800-e37
23  <<LAZY>>    org.codehaus.groovy.eclipse.dsl_2.6.1.xx-20120221-1800-e37
24  <<LAZY>>    org.codehaus.groovy.eclipse.quickfix_2.6.1.xx-20120221-1800-e37
25  <<LAZY>>    org.codehaus.groovy.eclipse.refactoring_2.6.1.xx-20120221-1800-e37
26  <<LAZY>>    org.codehaus.groovy.eclipse.ui_2.6.1.xx-20120221-1800-e37

osgi>
Show
Ben Walding added a comment - Done - I hope. Please check and let me know. (I have coded it as a Chef recipe; so upgrades are relatively straight forward now) [root@codehaus04 eclipse-SDK-3.7RC4-linux-gtk]# ./eclipse -clean -console osgi> ss org.codehaus.groovy Framework is launched. id State Bundle 1 RESOLVED org.codehaus.groovy.frameworkadapter_2.6.1.xx-20120221-1800-e37 Master=0 16 <<LAZY>> org.codehaus.groovy_1.7.10.xx-20120221-1800-e37 17 RESOLVED org.codehaus.groovy.eclipse_2.6.1.xx-20120221-1800-e37 18 <<LAZY>> org.codehaus.groovy.eclipse.ant_2.6.1.xx-20120221-1800-e37 19 <<LAZY>> org.codehaus.groovy.eclipse.astviews_2.6.1.xx-20120221-1800-e37 20 <<LAZY>> org.codehaus.groovy.eclipse.codeassist.completion_2.6.1.xx-20120221-1800-e37 21 <<LAZY>> org.codehaus.groovy.eclipse.codebrowsing_2.6.1.xx-20120221-1800-e37 22 <<LAZY>> org.codehaus.groovy.eclipse.core_2.6.1.xx-20120221-1800-e37 23 <<LAZY>> org.codehaus.groovy.eclipse.dsl_2.6.1.xx-20120221-1800-e37 24 <<LAZY>> org.codehaus.groovy.eclipse.quickfix_2.6.1.xx-20120221-1800-e37 25 <<LAZY>> org.codehaus.groovy.eclipse.refactoring_2.6.1.xx-20120221-1800-e37 26 <<LAZY>> org.codehaus.groovy.eclipse.ui_2.6.1.xx-20120221-1800-e37 osgi>
Ben Walding made changes -
Field Original Value New Value
Status Open [ 1 ] With Customer [ 10004 ]
Assignee Ben Walding [ bwalding ] Andrew Eisenberg [ werdna ]
Hide
Permalink
Andrew Eisenberg added a comment -

Thanks. I am going to try it out now.

Show
Andrew Eisenberg added a comment - Thanks. I am going to try it out now.
Andrew Eisenberg made changes -
Status With Customer [ 10004 ] In Progress [ 3 ]
Hide
Permalink
Andrew Eisenberg added a comment -

As we've been discussing over email, the build is now consuming too much memory. I am not exactly sure why, but here is something we can try.

Before, I had asked you to install the org.codehaus.groovy.eclipse.feature.feature.group, but there is a headless version of Groovy-Eclipse that we can install instead that may consume less memory. Here's how to do it.

First uninstall org.codehaus.groovy.eclipse.feature.feature.group (the same command as before, except use -uninstallIU instead of -installIU:

./eclipse/eclipse -consoleLog -clean -data /tmp/workspace \
   -application org.eclipse.equinox.p2.director \
   -repository http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.7/ \
   -uninstallIU org.codehaus.groovy.eclipse.feature.feature.group

Next, install the headless version instead:

./eclipse/eclipse -consoleLog -clean -data /tmp/workspace \
   -application org.eclipse.equinox.p2.director \
   -repository http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.7/ \
   -installIU org.codehaus.groovy.headless.feature.feature.group
Show
Andrew Eisenberg added a comment - As we've been discussing over email, the build is now consuming too much memory. I am not exactly sure why, but here is something we can try. Before, I had asked you to install the org.codehaus.groovy.eclipse.feature.feature.group , but there is a headless version of Groovy-Eclipse that we can install instead that may consume less memory. Here's how to do it. First uninstall org.codehaus.groovy.eclipse.feature.feature.group (the same command as before, except use -uninstallIU instead of -installIU: ./eclipse/eclipse -consoleLog -clean -data /tmp/workspace \ -application org.eclipse.equinox.p2.director \ -repository http: //dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.7/ \ -uninstallIU org.codehaus.groovy.eclipse.feature.feature.group Next, install the headless version instead: ./eclipse/eclipse -consoleLog -clean -data /tmp/workspace \ -application org.eclipse.equinox.p2.director \ -repository http: //dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.7/ \ -installIU org.codehaus.groovy.headless.feature.feature.group
Hide
Permalink
Andrew Eisenberg added a comment -

Hmmm...looking at the logs, I'm guessing that the problem is not coming from Groovy-Eclipse running in the build. The OOME happens while copying jar files before compilation actually begins. So, I don't think that doing the step described in the comment will affect anything.

There is nothing particularly strange about this Eclipse headless build, so I don't know where the leak might be coming from.

Show
Andrew Eisenberg added a comment - Hmmm...looking at the logs, I'm guessing that the problem is not coming from Groovy-Eclipse running in the build. The OOME happens while copying jar files before compilation actually begins. So, I don't think that doing the step described in the comment will affect anything. There is nothing particularly strange about this Eclipse headless build, so I don't know where the leak might be coming from.

People

  • Assignee:
    Andrew Eisenberg
    Reporter:
    Andrew Eisenberg
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: