river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Reedy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (RIVER-300) introduce maven to the river build process
Date Tue, 18 Jan 2011 14:58:45 GMT

    [ https://issues.apache.org/jira/browse/RIVER-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983213#action_12983213
] 

Dennis Reedy commented on RIVER-300:
------------------------------------

With regard to including the following classes into river-platform:

DiscoveryEvent
DiscoveryListener
DiscoverLocatorManagement
DiscoveryManagement
LookupLocatorDiscovery

The net.jini.core.discoveryLookupLocator imports net.jini.discovery.LookupLocatorDiscovery.
If net.jini.discovery.LookupLocatorDiscovery is not part of the river-platform, the river-platform
cannot build. The inclusion of the other classes in question is due to this dependency as
well, so the inclusion was definitely deliberate. :)

> 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
>
>
> 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.


Mime
View raw message