[
https://issues.apache.org/jira/browse/RIVER-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845085#comment-13845085
]
Greg Trasuk commented on RIVER-300:
-----------------------------------
I propose that we close this issue as "won't fix". We currently have in place
the capability to publish the produced jars to Maven Central. Restructuring or
modularizing the build may be appropriate if/when River components are
modified, but I would suggest it's not an end in itself.
Greg.
> 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,
> ldm.pdf, lld.pdf, persistOutrigger.pdf, river-modularization-overview.odt,
> river-modularization-overview.pdf
>
>
> 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 was sent by Atlassian JIRA
(v6.1.4#6159)
