incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tommaso Teofili (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HAMA-417) Refactoring of the Maven structure
Date Mon, 01 Aug 2011 13:42:09 GMT

     [ https://issues.apache.org/jira/browse/HAMA-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tommaso Teofili updated HAMA-417:
---------------------------------

    Attachment: HAMA-417_5.patch

I think we should move the site generation to be triggered once the 'site' phase is executed.
However the site can be generated by adding the site profile (-Psite) and the forrest.home
variable (-Dforrest.home=PATHTOFORREST).
This way the everyday developers won't see the site being generated each time they run 'mvn
install'

> 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
>             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