[ 
http://jira.codehaus.org/browse/MRPM-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218755#action_218755
 ] 

Fabien KOCIK commented on MRPM-73:
----------------------------------

Oh! Sorry I didn't see this issue...
Yes, it is essentially the same need.

> Allow dynamic require population through Maven dependencies mechanism
> ---------------------------------------------------------------------
>
>                 Key: MRPM-73
>                 URL: http://jira.codehaus.org/browse/MRPM-73
>             Project: Mojo RPM Plugin
>          Issue Type: Improvement
>          Components: rpm
>    Affects Versions: 2.0.1
>         Environment: Using Apache Maven to operate complex system inetgration.
>            Reporter: Fabien KOCIK
>            Assignee: Brett Okken
>            Priority: Minor
>         Attachments: rpm-maven-plugin-2.0.1-CIRSO1.patch
>
>
> Hello,
> I'm system engineer in a software development team that use MAVEN to produce 
> applications.
> My job is to automate application deployment on production environment.
> I use RPM to do that. I choosed *rpm-maven-plugin* because it is a great tool 
> for RPM generation, more robust than shell scripts but I was blocking on a 
> limitation.
> I need to deploy a very complex package grid where some packages require 
> other librariries.
> Ok, you'll say "??Use requires parameter??" and you'll be right in the 
> approach of statically declared dependencies.
> However, in my system, I need a dynamic approach that define a delivery rpm 
> and a meta-rpm used to configure the application (several meta-rpm can exists 
> for one delivery model).
> And I also need a static approach : it's a fact that a A package depends of a 
> B one.
> To design this, I used the {{requires}} parameter in order to link 
> meta-package with their delivery source package (in an ancestor POM that 
> developpers should not modify and that represent a delivery model).
> Then, developers can declare packages inter-dependency through classical 
> MAVEN {{dependency}} tag.
> I think it is a good practice to allow a RPM to depends another RPM using 
> MAVEN dependency mechanism. That the reason why I posted this message with a 
> piece of code I wrote in order to establish this link through an additional 
> parameter called {{requireMavenDependencies}}.
> This code works for me : it scans project's declared dependencies and then 
> adds an entry in the {{requires}} Set if the dependency type is {{rpm}}.
> I don't know if the extensibility is sufficient ... it's just an idea.
> Regards.
> Fabien KOCIK

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


Reply via email to