Mailing-List: contact river-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: river-dev@incubator.apache.org
Message-ID: <835361349.1229448884294.JavaMail.jira@brutus>
Date: Tue, 16 Dec 2008 09:34:44 -0800 (PST)
From: "Wade Chandler (JIRA)" <jira@apache.org>
To: river-commits@incubator.apache.org
Subject: [jira] Commented: (RIVER-300) introduce maven to the river build
 process
In-Reply-To: <421249875.1228751444406.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/RIVER-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657075#action_12657075 ] 

Wade Chandler commented on RIVER-300:
-------------------------------------

Jools, have you began working on the issue? Is there anything which I can help you with?

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