Announcement Announcement Module
Collapse
No announcement yet.
Unable to build fresh roo project Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Unable to build fresh roo project

    Hi all,
    I'm currently unable to build a fresh roo (1.2.2.RELEASE) project due to missing maven deps, no difference if created under STS or shell directly. Have I messed something up in my environment? Worked like a charm yesterday.

    br
    Svante

    -----C:\dev\java\workspace_3.0.0\rootest>roo
    ____ ____ ____
    / __ \/ __ \/ __ \
    / /_/ / / / / / / /
    / _, _/ /_/ / /_/ /
    /_/ |_|\____/\____/ 1.2.2.RELEASE [rev 7d75659]


    Welcome to Spring Roo. For assistance press TAB or type "hint" then hit ENTER.
    roo> project --topLevelPackage
    project --topLevelPackage
    required --topLevelPackage: The uppermost package name (this becomes the <groupId> in Maven and also the '~' value when using Roo's shell); no
    default value
    roo> project --topLevelPackage com.foo.test --

    project --topLevelPackage com.foo.test --java project --topLevelPackage com.foo.test --packaging
    project --topLevelPackage com.foo.test --parent project --topLevelPackage com.foo.test --projectName

    roo> project --topLevelPackage com.foo.test --pa

    project --topLevelPackage com.foo.test --packaging project --topLevelPackage com.foo.test --parent

    roo> project --topLevelPackage com.foo.test --packaging war
    Created ROOT\pom.xml
    Created ROOT\src\main\resources
    Created ROOT\src\main\resources\log4j.properties
    Created SPRING_CONFIG_ROOT
    Created SPRING_CONFIG_ROOT\applicationContext.xml
    roo>

    ------

    C:\dev\java\workspace_3.0.0\rootest>mvn clean install
    [INFO] Scanning for projects...
    [INFO]
    [INFO] ------------------------------------------------------------------------
    [INFO] Building test 0.1.0.BUILD-SNAPSHOT
    [INFO] ------------------------------------------------------------------------
    [WARNING] The POM for org.aspectj:aspectjrt:jar:1.7.0.RC1 is missing, no dependency information available
    [WARNING] The POM for org.aspectj:aspectjweaver:jar:1.7.0.RC1 is missing, no dependency information available
    [WARNING] The POM for org.springframework.roo:org.springframework.roo.an notations:jar:1.2.2.RELEASE is missing, no dependency information avai
    lable
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 0.717s
    [INFO] Finished at: Fri Sep 07 12:00:43 CEST 2012
    [INFO] Final Memory: 19M/742M
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal on project test: Could not resolve dependencies for project com.foo.test:test:war:0.1.0.BUILD-SNAPSHOT: The fol
    lowing artifacts could not be resolved: org.aspectj:aspectjrt:jar:1.7.0.RC1, org.aspectj:aspectjweaver:jar:1.7.0.RC1, org.springframework.roo:
    org.springframework.roo.annotations:jar:1.2.2.RELE ASE: Failure to find org.aspectj:aspectjrt:jar:1.7.0.RC1 in http://artifactory.cramo.interna
    l/artifactory/repo was cached in the local repository, resolution will not be reattempted until the update interval of artifactory has elapsed
    or updates are forced -> [Help 1]
    [ERROR]
    [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    [ERROR]
    [ERROR] For more information about the errors and possible solutions, please read the following articles:
    [ERROR] [Help 1] http://cwiki.apache.org/confluence/d...utionException
    C:\dev\java\workspace_3.0.0\rootest>

  • #2
    Test next:

    Change in pom.xml:

    <aspectj.version>1.7.0.RC1</aspectj.version>

    With:

    <aspectj.version>1.7.0</aspectj.version>

    Regards !

    Comment


    • #3
      Hi,
      Thanks, that one combined with adding the Roo repo to our repo manager did the trick!

      br
      Svante

      Comment

      Working...
      X