[
https://issues.apache.org/jira/browse/RIVER-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983631#action_12983631
]
Tom Hobbs commented on RIVER-300:
---------------------------------
A separate module sounds like a good idea. Am I right in thinking that will
help us when supporting multiple JDK versions?
The not requiring preferred class loading sounds like a very good idea. Can be
done after River-300 though? I'm just concious of the scope of River-300
getting to large. I'm tempted to say let's sort the build system (one way or
another) and define the modules (including Service API). Then we can apply the
gravy afterwards.
> 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,
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
