maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (ARCHETYPE-519) archetype:generate with specified remote archetypeCatalog falls back to internal catalog
Date Wed, 15 Feb 2017 20:05:41 GMT

     [ https://issues.apache.org/jira/browse/ARCHETYPE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Scholte closed ARCHETYPE-519.
------------------------------------
       Resolution: Fixed
         Assignee: Robert Scholte
    Fix Version/s: 3.0.1

I've just verified that -DarchetypeCatalog=<remote-catalog-url-from-our-nexus> will
indeed fall back to internal catalog as expected, because none of the catalogs could be resolved.
Removing  {{-DarchetypeCatalog}} will go to central or its mirror.
To prevent confusion I've decided to throw an IllegalArgumentException in case of unknown
archetypeCatalog values.
Fixed in [9e828c30482d0ed38b84f35e86d0eca166f094f6|http://git-wip-us.apache.org/repos/asf/maven-archetype/commit/9e828c30]

> archetype:generate with specified remote archetypeCatalog falls back to internal catalog
> ----------------------------------------------------------------------------------------
>
>                 Key: ARCHETYPE-519
>                 URL: https://issues.apache.org/jira/browse/ARCHETYPE-519
>             Project: Maven Archetype
>          Issue Type: Bug
>          Components: Generator
>    Affects Versions: 3.0.0
>         Environment: Mac OS X 10.11.6, Apache Maven 3.2.3
>            Reporter: Philip Mundt
>            Assignee: Robert Scholte
>             Fix For: 3.0.1
>
>
> We were surprised to find out that our archetype was "suddenly" not working anymore.
It turns out it was the release of {{org.apache.maven.plugins:maven-archetype-plugin:3.0.0}}
from 12/Feb/17 that was the culprit.
> When running:
> {{mvn org.apache.maven.plugins:maven-archetype-plugin:3.0.0:generate -DarchetypeCatalog=<remote-catalog-url-from-our-nexus>}}
we end up with the plugin falling back to the internal catalog:
> {code}
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Maven Stub Project (No POM) 1
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] >>> maven-archetype-plugin:3.0.0:generate (default-cli) > generate-sources
@ standalone-pom >>>
> [INFO]
> [INFO] <<< maven-archetype-plugin:3.0.0:generate (default-cli) < generate-sources
@ standalone-pom <<<
> [INFO]
> [INFO] --- maven-archetype-plugin:3.0.0:generate (default-cli) @ standalone-pom ---
> [INFO] Generating project in Interactive mode
> [INFO] No catalog defined. Using internal catalog
> [INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0)
> Choose archetype:
> 1: internal -> org.apache.maven.archetypes:maven-archetype-archetype (An archetype
which contains a sample archetype.)
> 2: internal -> org.apache.maven.archetypes:maven-archetype-j2ee-simple (An archetype
which contains a simplifed sample J2EE application.)
> 3: internal -> org.apache.maven.archetypes:maven-archetype-plugin (An archetype which
contains a sample Maven plugin.)
> 4: internal -> org.apache.maven.archetypes:maven-archetype-plugin-site (An archetype
which contains a sample Maven plugin site.
>       This archetype can be layered upon an existing Maven plugin project.)
> 5: internal -> org.apache.maven.archetypes:maven-archetype-portlet (An archetype which
contains a sample JSR-268 Portlet.)
> 6: internal -> org.apache.maven.archetypes:maven-archetype-profiles ()
> 7: internal -> org.apache.maven.archetypes:maven-archetype-quickstart (An archetype
which contains a sample Maven project.)
> 8: internal -> org.apache.maven.archetypes:maven-archetype-site (An archetype which
contains a sample Maven site which demonstrates
>       some of the supported document types like APT, XDoc, and FML and demonstrates how
>       to i18n your site. This archetype can be layered upon an existing Maven project.)
> 9: internal -> org.apache.maven.archetypes:maven-archetype-site-simple (An archetype
which contains a sample Maven site.)
> 10: internal -> org.apache.maven.archetypes:maven-archetype-webapp (An archetype which
contains a sample Maven Webapp project.)
> Choose a number or apply filter (format: [groupId:]artifactId, case sensitive contains):
> {code}
> Version 2.4 works as expected (the archetype catalog exists under given URL and can be
downloaded).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message