Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Trivial Trivial
    • Resolution: Duplicate
    • Affects Version/s: 2.0-beta-5
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      Linux
    • Number of attachments :
      0

      Description

      This bug is about the importance of Maven's first impression. I'm a new user trying to follow the procedure in the book (better builds with maven) . I had two issues that made me wonder about the stability of the product. I love the ideas behind maven and I would hate to see the progress of the product slowed due to a bad first impression.

      #1) When issuing the archetype command it stopped in the middle of the procedure without an error message. I re-issued the command and it worked the second time around.

      $ mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app

      #2) When issuing the command "mvn site" there are ERROR messages that appear on the screen, again making me wonder about the stability of the product. See section of output below:

      [INFO] Velocimacro : initialization starting.
      [INFO] Velocimacro : adding VMs from VM library template : VM_global_library.vm
      [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader.
      [INFO] Velocimacro : error using VM library template VM_global_library.vm : org.apache.velocity.exception.ResourceNotFoundException: Unable to find resource 'VM_global_library.vm'
      [INFO] Velocimacro : VM library template macro registration complete.
      [INFO] Velocimacro : allowInline = true : VMs can be defined inline in templates
      [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may NOT replace previous VM definitions
      [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be global in scope if allowed.
      [INFO] Velocimacro : initialization complete.
      [INFO] Velocity successfully started.
      [INFO] [site:site]
      [INFO] Generate "Continuous Integration" report.
      [ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0
      [ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0
      [INFO] Generate "Dependencies" report.

        Issue Links

          Activity

          Hide
          Mike Perham added a comment -

          Marked as a bug because there are previous issues on this which were supposedly resolved.

          Show
          Mike Perham added a comment - Marked as a bug because there are previous issues on this which were supposedly resolved.
          Hide
          Mike Perham added a comment -

          Frank, it is recommended that you open a new issue for each different error. Don't report multiple bugs in a single JIRA issue because then it is hard to categorize and track each individual problem. I'm not sure there's enough context for the archetype problem to be resolved.

          Show
          Mike Perham added a comment - Frank, it is recommended that you open a new issue for each different error. Don't report multiple bugs in a single JIRA issue because then it is hard to categorize and track each individual problem. I'm not sure there's enough context for the archetype problem to be resolved.

            People

            • Assignee:
              Unassigned
              Reporter:
              Frank Gutierrez
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: