RVM
  1. RVM
  2. RVM-896

Ready-To-Eclipse-Import needed

    Details

    • Type: Wish Wish
    • Status: Closed Closed
    • Priority: Blocker Blocker
    • Resolution: Won't Fix
    • Affects Version/s: 3.1.1
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      Ubuntu 64 bits
    • Number of attachments :
      2

      Description

      Hi everyone !

      Being a Java project, JikesRVM should not exclude non Linux world developpers with discouraging task they don't understand anything from, especially when they don't work fine.

      Eclipse being simple and widely used, it's correct I think, as you did to bring an import way, but a working one, which is not the case for me for example who don't know much from Linux.

      I so suggest you, in order to allow the newbies like me to that project, to keep focused and concentrated on that Virtual Machin business logic, to put under SVN a ready-to-Eclipse-import version of the code.

      Thank you.

      (check the attached file to see the reason why I suggest this please)

      1. newbie_failure_log.txt
        4 kB
        Boy D'Poy
      2. newbie fail 2.txt
        2 kB
        Boy D'Poy

        Activity

        Hide
        Boy D'Poy added a comment -

        I tried to correctly run the buildit command with these options : sudo bin/buildit --clear-cache --eclipse localhost -j /usr/lib/jvm/java-6-openjdk/

        After a long log I failed anew.

        I retried without clearing the cache to go faster, but ils still the same result; the attached failure log.

        I still don't understand the usefulness in asking a developper to run such command in order to have an eclipse project, while it could have been done for him, avoiding him these troubles, I still dont understand

        Show
        Boy D'Poy added a comment - I tried to correctly run the buildit command with these options : sudo bin/buildit --clear-cache --eclipse localhost -j /usr/lib/jvm/java-6-openjdk/ After a long log I failed anew. I retried without clearing the cache to go faster, but ils still the same result; the attached failure log. I still don't understand the usefulness in asking a developper to run such command in order to have an eclipse project, while it could have been done for him, avoiding him these troubles, I still dont understand
        Hide
        Erik Brangs added a comment -

        Perphaps the build failures are caused by missing programs/packages. "patch" would be a candidate for the first one, and "bison" for the second (because the build script can't seem to find it). If this is not the case, I advise you to ask on the researchers mailing list, which is the main mailing list for users of Jikes RVM. You can find more information about the mailing lists at http://docs.codehaus.org/display/RVM/Mailing+Lists.

        Show
        Erik Brangs added a comment - Perphaps the build failures are caused by missing programs/packages. "patch" would be a candidate for the first one, and "bison" for the second (because the build script can't seem to find it). If this is not the case, I advise you to ask on the researchers mailing list, which is the main mailing list for users of Jikes RVM. You can find more information about the mailing lists at http://docs.codehaus.org/display/RVM/Mailing+Lists .
        Hide
        Steve Blackburn added a comment -

        You're raising two distinct questions:

        1. Why is your build failing?

        2. Why don't we ship a pre-compiled eclipse configuration?

        As Erik says, the answer to the first question is most likely something to do with your environment, and the right place to ask is on the mailing list.

        As to the second question, there are a few answers: a) if you can't build the eclipse files, then you can't build, period, so the source code is not very useful to you :-/ b) the generated eclipse project files will depend not only on the state of the code (ie subject to your edits), but also on what platform you're building for (PPC or IA32?, etc). When you change targets, you need to recreate the generated files. So to ship a specific set of project files could be confusing/misleading since it would be specific to just one particular setup.

        So, in short I recommend Erik's suggestion of raising your build issue on the mailing list and you may find that someone else with a similar setup to yours can shed some light on it.

        Show
        Steve Blackburn added a comment - You're raising two distinct questions: 1. Why is your build failing? 2. Why don't we ship a pre-compiled eclipse configuration? As Erik says, the answer to the first question is most likely something to do with your environment, and the right place to ask is on the mailing list. As to the second question, there are a few answers: a) if you can't build the eclipse files, then you can't build, period, so the source code is not very useful to you :-/ b) the generated eclipse project files will depend not only on the state of the code (ie subject to your edits), but also on what platform you're building for (PPC or IA32?, etc). When you change targets, you need to recreate the generated files. So to ship a specific set of project files could be confusing/misleading since it would be specific to just one particular setup. So, in short I recommend Erik's suggestion of raising your build issue on the mailing list and you may find that someone else with a similar setup to yours can shed some light on it.
        Hide
        David Grove added a comment -

        bulk close of all resolved issues in preparation for 3.1.3 release.

        Show
        David Grove added a comment - bulk close of all resolved issues in preparation for 3.1.3 release.

          People

          • Assignee:
            Unassigned
            Reporter:
            Boy D'Poy
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: