[
http://jira.codehaus.org/browse/CBUILDS-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87164
]
John Casey commented on CBUILDS-9:
----------------------------------
I've got code in place and tested under 1.0-alpha-3 and higher that will do the
translation from maven version ranges to rpm version ranges...do we need to
convert back for any reason?
I guess farther down the line we may want to "read" the version ranges out of
the dependency statements of other rpms already on the system, to use them in
constraining the set of possible versions that can be used during the
build/install of the current project, so they can all live
side-by-side...however, without doing something like a `rpm -qa` and reading
the dependencies from each, I'm not sure how to pull "what depends on this
dependency"...
> Maven dependencies need to match RPM dependencies
> -------------------------------------------------
>
> Key: CBUILDS-9
> URL: http://jira.codehaus.org/browse/CBUILDS-9
> Project: Mojo C Builds
> Issue Type: Bug
> Components: Dependency Resolution and Build-on-Demand
> Reporter: Roger Hoover
> Fix For: 1.0-alpha-4
>
>
> Maven dependency ranges translate into RPM dependency ranges. Exactly Maven
> dependencies should translate into exact rpm dependencies.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
