Maven Archetype
  1. Maven Archetype
  2. ARCHETYPE-331

"No archetype repository found. ..." should not be a warning

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0-alpha-4
    • Fix Version/s: 2.0
    • Component/s: None
    • Labels:
      None
    • Environment:
      Maven 3.0 RC3
    • Number of attachments :
      0

      Description

      When creating a project from an archetype in Central, if you do not explicitly specify the repository URL, you get a warning:

      No archetype repository found. Falling back to central repository (http://repo1.maven.org/maven2). 
      Use -DarchetypeRepository=<your repository> if archetype's repository is elsewhere.
      

      This information is probably irrelevant if the archetype was in fact found. It is just noise, and the presence of a warning line can distract the user from real issues. DefaultArchetypeSelector.selectArchetype should print this at info level or even below.

        Activity

        Hide
        Herve Boutemy added a comment -

        do you have an example giving this warning?
        see DefaultArchetypeSelector: this warning is sent only when no repository is defined by user and archetype not found in any catalog
        perhaps the message should be more explicit about the precise cause
        WDYT?

        Show
        Herve Boutemy added a comment - do you have an example giving this warning? see DefaultArchetypeSelector: this warning is sent only when no repository is defined by user and archetype not found in any catalog perhaps the message should be more explicit about the precise cause WDYT?
        Hide
        Jesse Glick added a comment -

        Hmm, now I can no longer reproduce it. It was happening every time I used mojo-archetypes/* archetypes; maybe had something to do with them not using maven-archetype packaging so being present in local repo without being in the catalog?

        Show
        Jesse Glick added a comment - Hmm, now I can no longer reproduce it. It was happening every time I used mojo-archetypes/* archetypes; maybe had something to do with them not using maven-archetype packaging so being present in local repo without being in the catalog?
        Hide
        Herve Boutemy added a comment -

        warning message improved in r1004817

        Show
        Herve Boutemy added a comment - warning message improved in r1004817

          People

          • Assignee:
            Herve Boutemy
            Reporter:
            Jesse Glick
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: