[
https://issues.apache.org/jira/browse/RIVER-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981531#action_12981531
]
Peter Firmstone commented on RIVER-300:
---------------------------------------
In the existing build jsk-policy.jar is an optional file, it duplicates class
files from jsk-platform.jar
Since jsk-policy.jar is loaded by the ext class loader, it is actually a parent
ClassLoader of the application ClassLoader, which means that classes in
jsk-platform.jar cannot be seen by jsk-policy.jar classes, therefore, it would
seem to make sense to include the duplicated classes in the policy module, and
have the platform module depend on the policy module.
Does this make sense? How will this affect modular systems? The policy module
will need to be loaded into the java extension class loader, this can be done
by way of a java command argument or by using the jre ext directory.
> 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.
