[
http://jira.codehaus.org/browse/MRPM-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208593#action_208593
]
Brett Okken commented on MRPM-62:
---------------------------------
The version goal was made part of the default lifecycle for an rpm project
(executing in the initialize phase). The phases that are executed depends on
the default lifecycle for the packaging type you have defined.
But just as you had to define an execution with a goal of rpm (because it was
not associated with your default lifecycle), you will also have to define the
version goal to execute.
> Provide expression for release attribute
> ----------------------------------------
>
> Key: MRPM-62
> URL: http://jira.codehaus.org/browse/MRPM-62
> Project: Mojo RPM Plugin
> Issue Type: Improvement
> Components: rpm
> Affects Versions: 2.0-beta-4
> Reporter: Robert Munteanu
> Assignee: Brett Okken
> Priority: Minor
> Fix For: 2.0
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> When building a multi-module project , e.g.
> project
> \- sub-project-a
> \- sub-project-b
> \- scripts
> It's useful to declare that the RPMs for both _sub-project a_ and
> _sub-project-b_ depend on the _scripts_ RPM. At the moment I can't declare an
> exact version requirement, since I don't have access to the release version
> of the project (
> http://mojo.codehaus.org/rpm-maven-plugin/rpm-mojo.html#release ) , which
> would allow me to use:
> {code}
> <requires>
> <require>scripts = ${project.version}-${project.rpm.release}</require>
> </requires>
> {code}
> Please consider providing this expression.
--
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
