hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-417) Refactoring of the Maven structure
Date Fri, 05 Aug 2011 08:34:27 GMT

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

Hudson commented on HAMA-417:
-----------------------------

Integrated in Hama-Nightly #275 (See [https://builds.apache.org/job/Hama-Nightly/275/])
    [HAMA-417] - removed unnecessary files in source directory of site module

tommaso : 
Files : 
* /incubator/hama/trunk/site/src/webapps
* /incubator/hama/trunk/site/src/test
* /incubator/hama/trunk/site/src/java
* /incubator/hama/trunk/site/src/examples


> Refactoring of the Maven structure
> ----------------------------------
>
>                 Key: HAMA-417
>                 URL: https://issues.apache.org/jira/browse/HAMA-417
>             Project: Hama
>          Issue Type: Improvement
>          Components: build 
>    Affects Versions: 0.3.0
>            Reporter: Tommaso Teofili
>            Assignee: Tommaso Teofili
>             Fix For: 0.4.0
>
>         Attachments: HAMA-417.patch, HAMA-417_2.patch, HAMA-417_3.patch, HAMA-417_4.patch,
HAMA-417_5.patch
>
>
> The current structure of the project makes separate management/releasing of core and
examples artifacts complicated as the source directory is selected upon profile activation.
> The proposed solution is to create a common parent POM (hama-parent) in the SVN top node,
and then two modules 'core' and 'examples' which can be tested/managed/released separately
(and better, hopefully).
> This will also allow further refactoring and additions of new modules.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message