[
https://issues.apache.org/jira/browse/RIVER-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982049#action_12982049
]
Peter Firmstone commented on RIVER-300:
---------------------------------------
I'm going to assume for now that the reasons the classes have been moved into
platform from lib was perhaps due to time, we can move classes back in later.
For now I'm just going to stick with the dependency structure of the existing
build, but without class file duplication, as Dennis has done so far.
LookupLocatorDiscovery, looks like a good candidate to be moved into the
platform, perhaps we can discuss it at length later.
> 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.
