Uploaded image for project: 'Forge'
  1. Forge
  2. FORGE-2243

Programmatically added maven archetype catalog does not work with new-project

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.15.0.Final
    • 2.14.0.Final
    • None
    • None

      See also FORGE-2242

      When using the new-project command it doesnt work with catalogs that has been added from java code.

      I have added an archetype catalog named "central", eg see FORGE-2242, and when I use it in project-new it fails, as the last output.

      [forge-distribution-2.14.0.Final]$ project-new
      ***INFO*** Required inputs not satisfied, entering interactive mode
      ? Project name:  mydemo2
      ? Top level package [org.mydemo2]:
      ? Version [1.0.0-SNAPSHOT]:
      ? Final name:
      ? Project location [/opt/forge-distribution-2.14.0.Final]:
      
      [0] (x) war
      [1] ( ) jar
      [2] ( ) parent
      [3] ( ) addon
      [4] ( ) resource-jar
      [5] ( ) ear
      [6] ( ) from-archetype
      [7] ( ) from-archetype-catalog
      
      Press <ENTER> to confirm, or <CTRL>+C to cancel.
      ? Project type: [0-7] 7
      
      [0] (x) Maven
      
      Press <ENTER> to confirm, or <CTRL>+C to cancel.
      ? Build system: [0]
      
      [0] ( ) central
      
      Press <ENTER> to confirm, or <CTRL>+C to cancel.
      ? Catalog: [0]
      ***ERROR*** Catalog must be specified.
      ***ERROR*** Archetype must be specified.
      [forge-distribution-2.14.0.Final]$
      

      But if I add an archetype catalog using archetype-add from the forge shell then it works with project-new, even though they both load the same set of archetypes from maven central.

              rhn-support-ggastald George Gastaldi
              cibsen@redhat.com Claus Ibsen
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: