cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9146) Refactor plugin kvm-hypervisor to default maven structure.
Date Sun, 13 Dec 2015 16:16:46 GMT


ASF GitHub Bot commented on CLOUDSTACK-9146:

Github user bhaisaab commented on the pull request:
    @DaanHoogland I'm not opposed to the change it is just that I think it makes my life challenging
with some of the things I do on day-to-day basis :) We do follow all the Maven conventions
except for the directory structure (src and test paths) which I thought was not end of the
    Nevertheless, I'm curious to know what are the pros or cons of not following the Maven
convention (specifically the src/ and test/ directory structure) in the long.

> Refactor plugin kvm-hypervisor to default maven structure.
> ----------------------------------------------------------
>                 Key: CLOUDSTACK-9146
>                 URL:
>             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.

This message was sent by Atlassian JIRA

View raw message