Re: The maven-archetype-plugin paradox

Looks like https://issues.apache.org/jira/browse/ARCHETYPE-528 With mirror this seems to work as expected, but without is uses Central to look for the catalog. So that's a bug. Robert On Mon, 22 May 2017 17:53:36 +0200, Amélie Deltour wrote: (the catalog is

Re: The maven-archetype-plugin paradox

(the catalog is located at http://artifactory.mycompany.com/internal-releases/archetype-catalog.xml) On 05/22/2017 05:52 PM, Amélie Deltour wrote: Hi, Thanks for the link, I could not find where this "archetype" repository was documented. However, I tried to use the "archetype" repository

Re: The maven-archetype-plugin paradox

Hi, Thanks for the link, I could not find where this "archetype" repository was documented. However, I tried to use the "archetype" repository earlier, and tried again, and I can't make it work. With 2.4: mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate

Re: The maven-archetype-plugin paradox

Hi Amélie, first thank you for helping to us to improve this and to get more information about the several use cases. If you have a repository in the settings.xml, it must be inside a profile. This would mean that it looks more like you have to do this:

Re: The maven-archetype-plugin paradox

ARCHETYPE-520 (and ARCHETYPE-358) are indeed close to the problem I try to describe, but not exactly the same. These issues are about using the mirror configuration to access archetype data, i.e. using http://myrepo.mycompany/maven/archetype-catalog.xml instead of direct access to

Re: The maven-archetype-plugin paradox

> The more I think about it, the more I'm convinced we should also remove > the archetypeCatalog parameter. Right now it is only causing confusion. > Yes, you're probably right. It should just work - you shouldn't have to specify what sort of catalog to be used. /Anders > Does it still make

Re: The maven-archetype-plugin paradox

Looks like ARCHETYPE-520[1] to me. I've created an integration-test for it, so that should work with 3.0.1 The more I think about it, the more I'm convinced we should also remove the archetypeCatalog parameter. Right now it is only causing confusion. Does it still make sense to have

Re: The maven-archetype-plugin paradox

I would expect "remote" not be the central repo but what repo(s) (or mirrors) are configured in settings.xml. Robert, what's your view of how this works in the plugin now? /Anders On Tue, May 16, 2017 at 11:06 AM, Amélie Deltour wrote: > Hi Anders, > > Thanks for

Re: The maven-archetype-plugin paradox

Hi Anders, Thanks for your clarification. In understand well the idea behind the 3.x version and the concern for more security and avoid to fetch anything directly from the Internet. Every "external" access should go throud the repositories configured in the Maven settings.xml, I completely

Re: The maven-archetype-plugin paradox

Amélie, Thanks for describing your use case here on the list! As I am one of the reporters for the tickets behind the change in question I'd like to describe my reasoning: First off, your use case is actually (if I understand it correctly) standard for Maven usage. For a company environment I

Re: The maven-archetype-plugin paradox

Sorry guys, but as a maven-archetype-plugin user I don't share your views on this subject. Of course, I totally agree with the aim of this new 3.x release and the idea to be compliant with Maven3 behaviour and in particular the security features. However, there have been quite a lot of

Re: The maven-archetype-plugin paradox

As one of the reporters of the breaking change tickets I also rather not see this reverted as I think that our plugins should follow The Maven Way and help people do the right thing. I've seen some voices raises in some of the tickets (after the fact). But how many is it really that has a

Re: The maven-archetype-plugin paradox

+1 to the general analysis perhaps using previous release is not so easy since this plugin is used on CLI, not in a pom.xml (in general), then you don't really choose which version will be used when you launch "mvn archetype:generate": Maven magic does a choice for you The longer command line

Re: The maven-archetype-plugin paradox

Hi, On 08/05/17 19:38, Robert Scholte wrote: So we have this plugin, which has been released lately as requested by the community. It has been released as a 3.x, so it now requires Maven3 and with this major release[1] we used this opportunity to break compatibility in case there are parameters

Re: The maven-archetype-plugin paradox

I think you have done the right thing even if some users are not necessarily happy. The documentation about the new behavior is clear enough, but maybe it needs to be more explicit. In either I would just keep the plugin at ASF and do minimal maintenance like you have been doing. If someone