[ 
https://issues.apache.org/jira/browse/ARCHETYPE-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010710#comment-16010710
 ] 

Henry Saputra edited comment on ARCHETYPE-439 at 5/15/17 4:41 PM:
------------------------------------------------------------------

The description of this bug is also bit vague. 
Why is it not good? What is the proposed solution? Why would proposed solution 
work?

See ARCHETYPE-519 for after math of these changes. 

I understand major version changes can be used for "breaking" changes but it 
should have good reason why and have users to have equivalent solution or path 
to achieve similar result. 
Thanks. 


was (Author: hsaputra):
The description of this bug is very vague. Why is it not good? What is the 
proposed solution? Why would proposed solution work?

See ARCHETYPE-519 for after math of these changes. 

I understand major version changes can be used for "breaking" changes but it 
should have good reason why and have users to have equivalent solution or path 
to achieve similar result.

> Remove archetypeRepository param
> --------------------------------
>
>                 Key: ARCHETYPE-439
>                 URL: https://issues.apache.org/jira/browse/ARCHETYPE-439
>             Project: Maven Archetype
>          Issue Type: Improvement
>          Components: Generator
>         Environment: n/a
>            Reporter: Anders Hammar
>            Assignee: Robert Scholte
>             Fix For: 3.0.0
>
>
> The archetypeRepository param makes it possible to bypass the configured 
> Maven repos for retrieving an archetype. This is not good.



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

Reply via email to