[
https://issues.apache.org/jira/browse/RIVER-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984397#action_12984397
]
Peter Firmstone commented on RIVER-300:
---------------------------------------
I've added a link to River-341, although I think we need to update that
document.
When I say Service API, I mean the public API of services; interfaces and
classes common to clients, services and proxy's These would be the platform
services in this case.
These are the classes that you don't want to change, the end of protocols for
Jini meant that protocols were replaced by java interfaces, these are those
interfaces, the public api of services. An appropriate name might be
jini-platform-service-api.jar
The Service UI API contains classes and entry's that would also be common to
clients, proxy's and services, although it can remain separate if necessary.
(Are there still eager loading JVM's out there? I'm thinking of headless
nodes).
For example, the lease service's api is currently packaged in jsk-dl.jar
(river-dl.jar), we don't really want it there, we want it to already be at the
client.
So to confirm the difference between the -api.jar and -dl.jar, the -dl.jar will
depend on the -api.jar, which should be installed by the client.
I think it would be likely that the river-platform.jar might depend on the
jini-platform-service-api.jar also, in which case clients only depend on the
river-platform.jar
> 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.
