You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Simone Bordet (JIRA)" <ji...@apache.org> on 2017/02/27 18:30:46 UTC
[jira] [Comment Edited] (ARCHETYPE-519) archetype:generate with
specified remote archetypeCatalog falls back to internal catalog
[ https://issues.apache.org/jira/browse/ARCHETYPE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886271#comment-15886271 ]
Simone Bordet edited comment on ARCHETYPE-519 at 2/27/17 6:30 PM:
------------------------------------------------------------------
Robert, pardon me but I don't understand. Archetype artifacts are stored in Maven Central, and it has always been so.
The problem here is just a simple XML file, the archetype catalog, that just points to artifacts in Maven central.
I don't understand what you mean by "archetype repository", and it does not look like it is related to this issue.
I, for one, do not want another "repository". Maven Central is enough. I just want the ability to run {{mvn archetype:generate}} with a pointer to my project so that the user can choose between 1-10 choices and not thousands.
Can you point to the complains that you mention ?
Can you also explain the "pureness" you mention, because I feel we are all lost here - the old approach was really "pure" to me, and way simpler.
Regarding adding the new {{register-repository}} goal, I don't know what problems would it solve, and how would make things simpler like they were before.
And, as I said, I don't want another repository, Maven Central is enough.
Thanks !
was (Author: sbordet):
Robert, pardon me but I don't understand. Archetype artifacts are stored in Maven Central, and it has always been so.
The problem here is just a simple XML file, the archetype catalog, that just points to artifacts in Maven central.
I don't understand what you mean by "archetype repository", and it does not look like it is related to this issue.
I, for one, do not want another "repository". Maven Central is enough. I just want the ability to run {{mvn archetype:generate}} with a pointer to my project so that the user can choose between 1-10 choices and not thousands.
Can you point to the complains that you mention ?
Can you also explain the "pureness" you mention, because I feel we are all lost here - the old approach was really "pure" to me, and way simpler.
Regarding adding the new {{register-repository}} goal, I don't know what problems would it solve, and how would make this simpler like they were before.
And, as I said, I don't want another repository, Maven Central is enough.
Thanks !
> 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)