[
https://issues.apache.org/jira/browse/RIVER-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151286#comment-17151286
]
Phillip Rhodes commented on RIVER-300:
--------------------------------------
Here is a patch against the branch at
[http://svn.apache.org/repos/asf/river/jtsk/modules] that, for me at least,
allows Maven to successfully compile and jar everything. This is not even
close to the desired final state in my mind, for various reason. See my email
to dev@ for more on that.
At best, this may be a stepping stone that somebody else can use.
Unfortunately, I'm not qualified enough to do much more given my relative
unfamiliarity with the River code base.
[^maven_compilation_working_07042020.diff]
> 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
> Priority: Major
> Attachments: apache-river-gradle.zip, apache-river-maven.zip,
> ldm.pdf, lld.pdf, maven_compilation_working_07042020.diff,
> 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
(v8.3.4#803005)
