You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Dennis Reedy (JIRA)" <ji...@apache.org> on 2011/01/05 19:58:45 UTC

[jira] Updated: (RIVER-300) introduce maven to the river build process

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

Dennis Reedy updated RIVER-300:
-------------------------------

    Attachment: apache-river-maven.zip
                apache-river-gradle.zip

> introduce maven to the river build process
> ------------------------------------------
>
>                 Key: RIVER-300
>                 URL: https://issues.apache.org/jira/browse/RIVER-300
>             Project: River
>          Issue Type: Improvement
>          Components: build
>            Reporter: Jools Enticknap
>         Attachments: apache-river-gradle.zip, apache-river-maven.zip
>
>
> Currently the river build using ant, but it's a custom build process and has many hang overs from the original make build.
> Given that the project has no 3rd party dependencies, it would be very easy to break the code up into modules.
> Please feel free to add to this JIRA if you have any opinions on how the maven repository should be setup.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.