Announcement Announcement Module
No announcement yet.
On OS X - roo-dev stopped working for me Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • On OS X - roo-dev stopped working for me

    I have the read-only trunk installed on my machine, and for a while I was able to type roo-dev (before 1.0.0.M2) and have it pull up the development changes to the platform.

    I have been playing with changes and enhancements in the tree as they come available (and verifying that issues I create aren't already fixed in future revisions) so it would be helpful to have this working.

    But recently I see errors in trying to find the bootstrap class. Did the installation procedure of linking to roo-mvn change recently? I am on OS X Leopard running JDK 1.6 64-bit (java full version "1.6.0_13-b03-211"). I do remember to chmod +x the roo-mvn script once I get an update in subversion.

    Here is the output I get. Doesn't see a ROO_CLASSPATH_FILE because I don't create one... So that may be an issue, but I thought this was figured out via the script itself.

    flibbity-floo:trunk krimple$ roo-dev
    WARNING: ROO_CLASSPATH_FILE environment variable is not set (using default 'target/roo_classpath.txt')
    Maven launch; will output 'target/roo_classpath.txt' for future caching
    + Error stacktraces are turned on.
    [INFO] Scanning for projects...
    [INFO] Reactor build order:
    [INFO] Spring Roo - Annotations (ASLv2/GPLv3 Dual Licensed)
    [INFO] Spring Roo
    [INFO] Spring Roo - Support
    [INFO] Spring Roo - Model
    [INFO] Spring Roo - Shell
    [INFO] Spring Roo - Shell (JLine Implementation)
    [INFO] Spring Roo - Metadata
    [INFO] Spring Roo - File Undo
    [INFO] Spring Roo - File Monitor
    [INFO] Spring Roo - File Monitor (Polling Implementation)
    [INFO] Spring Roo - Project
    [INFO] Spring Roo - Process Manager
    [INFO] Spring Roo - Classpath
    [INFO] Spring Roo - Classpath (JavaParser Implementation)
    [INFO] Spring Roo - Addon - Maven
    [INFO] Spring Roo - Addon - Plural Details
    [INFO] Spring Roo - Addon - Property Files
    [INFO] Spring Roo - Addon - JavaBean Information
    [INFO] Spring Roo - Addon - @Configurable Support
    [INFO] Spring Roo - Addon - Email
    [INFO] Spring Roo - Addon - JavaBean Method Manager
    [INFO] Spring Roo - Addon - JPA
    [INFO] Spring Roo - Addon - JMS
    [INFO] Spring Roo - Addon - Entity
    [INFO] Spring Roo - Addon - Finder
    [INFO] Spring Roo - Addon - Logging
    [INFO] Spring Roo - Addon - Property Editor
    [INFO] Spring Roo - Addon - Spring Security
    [INFO] Spring Roo - Addon - toString
    [INFO] Spring Roo - Addon - Web Menu
    [INFO] Spring Roo - Addon - Web MVC Controller
    [INFO] Spring Roo - Addon - Web MVC JSP View
    [INFO] Spring Roo - Addon - Web - Flow
    [INFO] Spring Roo - Addon - Web Selenium Test Generator
    [INFO] Spring Roo - Addon - Test Data On Demand
    [INFO] Spring Roo - Addon - Automated Integration Testing
    [INFO] Spring Roo - Bootstrap
    [INFO] Searching repository for plugin with prefix: 'exec'.
    WAGON_VERSION: 1.0-beta-2
    [INFO] ------------------------------------------------------------------------
    [INFO] Building Spring Roo - Annotations (ASLv2/GPLv3 Dual Licensed)
    [INFO] task-segment: [exec:java]
    [INFO] ------------------------------------------------------------------------
    [INFO] Preparing exec:java
    [INFO] [buildnumber:create {execution: default}]
    [INFO] Checking for local modifications: skipped.
    [INFO] Updating project files from SCM: skipped.
    [INFO] Executing: /bin/sh -c cd /opt/java/spring-roo/trunk/annotations && svn --non-interactive info
    [INFO] Working directory: /opt/java/spring-roo/trunk/annotations
    [INFO] Storing buildNumber: 148 at timestamp: 1246546897349
    [INFO] [exec:java]
    [INFO] ------------------------------------------------------------------------
    [INFO] ------------------------------------------------------------------------
    [INFO] An exception occured while executing the Java class. org.springframework.roo.bootstrap.Bootstrap

    [INFO] ------------------------------------------------------------------------
    [INFO] Trace
    org.apache.maven.lifecycle.LifecycleExecutionExcep tion: An exception occured while executing the Java class. org.springframework.roo.bootstrap.Bootstrap
    at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeGoals(
    at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeStandaloneGoal(DefaultLifecycleExecutor.j ava:513)
    at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeGoal(
    at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeGoalAndHandleFailures(DefaultLifecycleExe
    at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeTaskSegments(DefaultLifecycleExecutor.jav a:292)
    at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.execute(
    at org.apache.maven.DefaultMaven.doExecute(DefaultMav
    at org.apache.maven.DefaultMaven.execute(DefaultMaven .java:129)
    at org.apache.maven.cli.MavenCli.main( 01)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De
    at java.lang.reflect.Method.invoke(
    at org.codehaus.classworlds.Launcher.launchEnhanced(L
    at org.codehaus.classworlds.Launcher.launch(Launcher. java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode (
    at org.codehaus.classworlds.Launcher.main(Launcher.ja va:375)
    Caused by: org.apache.maven.plugin.MojoExecutionException: An exception occured while executing the Java class. org.springframework.roo.bootstrap.Bootstrap
    at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJa
    at org.apache.maven.plugin.DefaultPluginManager.execu teMojo(
    at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeGoals(
    ... 16 more
    Caused by: java.lang.ClassNotFoundException: org.springframework.roo.bootstrap.Bootstrap
    at$ 200)
    at Method)
    at ava:188)
    at java.lang.ClassLoader.loadClass( 19)
    at java.lang.ClassLoader.loadClass( 54)
    at org.codehaus.mojo.exec.ExecJavaMojo$

  • #2
    Hi Ken,

    I have set the ROO_CLASSPATH_FILE in my environment to:


    Then when you do a fresh checkout you need to make sure that the roo_classpath.txt file is re-generated. Here is what I usually do:

    mvn clean eclipse:clean eclipse:eclipse compile
    I have not tested this on a Mac though.



    • #3
      Yep, this works. Thanks.

      I wonder though, does doing this make using the roo command line honor the same classpath as roo-dev? I'd like to have both environments available and thought that it was working that way before.



      • #4
        Well, at least for us the whole point is to keep them seperate . We use the roo shell for testing released versions (such as M2) and roo-dev to work with during development. So I am not sure why you would want to have them both do exactly the same.



        • #5
          No, maybe I was unclear. I was worried that setting this variable would affect the roo shell too. Glad to hear they are still separate.