Uploaded image for project: 'Spring Roo'
  1. Spring Roo
  2. ROO-363

Perform commands do not work in RC3

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.0.RC3
    • Fix Version/s: 1.0.0.RC4
    • Component/s: BUILD
    • Labels:
      None
    • Environment:
      Win XP SP3

      Description

      Just dowloaded RC3.
      Perform commands seem not to work at all. Same behavior in sts and in standalone roo shell.

      Just looks like this:

      roo> perform package
      roo>

      I have Maven 2.10 in my path.

      In previous version (RC2) it did work (besides the known issue in STS ...)

        Issue Links

          Activity

          Hide
          jkuipers Joris Kuipers added a comment -

          Patch committed, also added color output for Maven errors and warnings

          Show
          jkuipers Joris Kuipers added a comment - Patch committed, also added color output for Maven errors and warnings
          Hide
          jkuipers Joris Kuipers added a comment -

          Note: this was fixed in SVN rev 431. Rev 432 contains an additional fix for recognizing the error msg on Windows emitted when mvn.bat cannot be found.

          Show
          jkuipers Joris Kuipers added a comment - Note: this was fixed in SVN rev 431. Rev 432 contains an additional fix for recognizing the error msg on Windows emitted when mvn.bat cannot be found.
          Hide
          ernestv Ernest E Vogelsinger added a comment -

          I hate it to disappoint you but I have the identical problem, running openSUSE 11.1 (see below)

          ErnestV@156:~/roo-test/ten-minutes> cat /etc/SuSE-release
          openSUSE 11.1 (i586)
          VERSION = 11.1
          ErnestV@156:~/roo-test/ten-minutes> roo
          ____ ____ ____
          / __ \/ __ \/ __ \
          / /_/ / / / / / / /
          / , _/ // / /_/ /
          // ||___/___/ 1.0.0.RC3 [rev 401]

          Welcome to Spring Roo. For assistance press TAB or type "hint" then hit ENTER.
          roo> perform tests
          Error: JAVA_HOME is not defined correctly.
          We cannot execute
          roo> exit
          ErnestV@156:~/roo-test/ten-minutes> $JAVA_HOME/bin/java -version
          java version "1.6.0_17"
          Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
          Java HotSpot(TM) Server VM (build 14.3-b01, mixed mode)
          ErnestV@156:~/roo-test/ten-minutes>

          Show
          ernestv Ernest E Vogelsinger added a comment - I hate it to disappoint you but I have the identical problem, running openSUSE 11.1 (see below) ErnestV@156:~/roo-test/ten-minutes> cat /etc/SuSE-release openSUSE 11.1 (i586) VERSION = 11.1 ErnestV@156:~/roo-test/ten-minutes> roo ____ ____ ____ / __ \/ __ \/ __ \ / /_/ / / / / / / / / , _/ / / / /_/ / / / | |___ /_ __/ 1.0.0.RC3 [rev 401] Welcome to Spring Roo. For assistance press TAB or type "hint" then hit ENTER. roo> perform tests Error: JAVA_HOME is not defined correctly. We cannot execute roo> exit ErnestV@156:~/roo-test/ten-minutes> $JAVA_HOME/bin/java -version java version "1.6.0_17" Java(TM) SE Runtime Environment (build 1.6.0_17-b04) Java HotSpot(TM) Server VM (build 14.3-b01, mixed mode) ErnestV@156:~/roo-test/ten-minutes>
          Hide
          jkuipers Joris Kuipers added a comment -

          @ Ernest: that's not disappointing, it's expected. The environment is not passed to the process running maven, so JAVA_HOME is not available to maven even though it's defined in your normal environment.
          I'm not sure why not more people not on Windows are affected by this bug, but I am sure that the patch I committed will fix this issue for you as well. RC 4 is scheduled for the end of this month I believe, but you can easily build Roo from SVN yourself if you want early access to a release that contains this fix.

          Show
          jkuipers Joris Kuipers added a comment - @ Ernest: that's not disappointing, it's expected. The environment is not passed to the process running maven, so JAVA_HOME is not available to maven even though it's defined in your normal environment. I'm not sure why not more people not on Windows are affected by this bug, but I am sure that the patch I committed will fix this issue for you as well. RC 4 is scheduled for the end of this month I believe, but you can easily build Roo from SVN yourself if you want early access to a release that contains this fix.
          Hide
          ernestv Ernest E Vogelsinger added a comment -

          Hi Joris, thanks for your comment, I just had a look into your patch (should have done this before ;->) and indeed this should fix the problem.

          As this fix only affects the addon.maven jar why not post it here so we don't need to build roo completely?

          Show
          ernestv Ernest E Vogelsinger added a comment - Hi Joris, thanks for your comment, I just had a look into your patch (should have done this before ;->) and indeed this should fix the problem. As this fix only affects the addon.maven jar why not post it here so we don't need to build roo completely?

            People

            • Assignee:
              jkuipers Joris Kuipers
              Reporter:
              stefanoc Stefan Ocke
            • Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: