[
http://jira.codehaus.org/browse/ARCHETYPE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237441#action_237441
]
Jesse Glick commented on ARCHETYPE-331:
---------------------------------------
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?
> "No archetype repository found. ..." should not be a warning
> ------------------------------------------------------------
>
> Key: ARCHETYPE-331
> URL: http://jira.codehaus.org/browse/ARCHETYPE-331
> Project: Maven Archetype
> Issue Type: Bug
> Affects Versions: 2.0-alpha-4
> Environment: Maven 3.0 RC3
> Reporter: Jesse Glick
> Priority: Minor
> Fix For: 2.0
>
>
> When creating a project from an archetype in Central, if you do not
> explicitly specify the repository URL, you get a warning:
> {noformat}
> No archetype repository found. Falling back to central repository
> (http://repo1.maven.org/maven2).
> Use -DarchetypeRepository=<your repository> if archetype's repository is
> elsewhere.
> {noformat}
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
