[
https://issues.apache.org/jira/browse/RIVER-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983726#action_12983726
]
Dennis Reedy commented on RIVER-300:
------------------------------------
I agree with making sure we dont pile on too much for this issue. IMO this
issue should be scoped to provide (as much as possible) a structured and
modular distribution of the source code that results in the creation of
artifacts that are equivalent (again: as much as possible) jars as found in the
current project build.
I had taken the opportunity to perform the namespace replacement of
com.sun.jini.* to org.apache.river.*, perhaps that was too far reaching, but it
made sense to me at the time.
Possible next steps here may be:
1. Address the issue for jsk-resources.jar and jsk-policy.jar
2. Provide aggregation tasks for javadoc
3. Add QA project (or at least some of the QA project) execution into the
lifecycle of building the project
4. Perhaps this should be item #0, decide whether we want to work with Maven or
Gradle. Gradle may have benefits for #1 above, where we could create multiple
artifacts from a single module. While this is doable with Maven, its not
exactly straightforward.
> 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.
