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

ASF GitHub Bot commented on CLOUDSTACK-9146:
--------------------------------------------

Github user wilderrodrigues commented on the pull request:

    https://github.com/apache/cloudstack/pull/1224#issuecomment-164371097
  
    @DaanHoogland @bhaisaab 
    
    The first thing is that using a standard is better than doing the way 
nobody else is doing. When one adopts a technology is essential to stick with 
what that technology has standardised. It help in the long run when other 
people, used to that technology, will join the project. In addition, ACS is not 
our only Maven project. So, sticking with the standard is great.
    
    Nothing personal, but I'm not a fan of ```the only issue for me is that 
most users are not as agile as we want them to be.``` those kind or arguments. 
We have to improve, as much as we can, and it should not be stopped because 
other users cannot improve. What we do is to make our work better and also to 
help them see the better way of doing things. A bit philosophical, but I 
believe that we have to lead by example.
    
    This code should have been merged before the 4.7 cut.
    
    More on this: 
https://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html


> Refactor plugin kvm-hypervisor to default maven structure.
> ----------------------------------------------------------
>
>                 Key: CLOUDSTACK-9146
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9146
>             Project: CloudStack
>          Issue Type: Sub-task
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Boris Schrijver
>            Assignee: Boris Schrijver
>
> Adhere to the default maven directory structure.
> https://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to