[ 
https://issues.apache.org/jira/browse/SMX4-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen updated SMX4-794:
---------------------------------

    Attachment: parent.xml

parent.xml is a sample of what we should be able to provide : a POM that has 
managed dependencies and plugins for all the stuff people are using when 
they're building applications for ServiceMix

I'm only struggling a bit with what the best way would be to get this included 
in the build: currently tinkering to create a 'parent' module that has this 
kind of pom and then let the root pom inherit from it and add the bits we 
require to build ServiceMix itself in the root pom.

> Provide a convenience POM for users 
> ------------------------------------
>
>                 Key: SMX4-794
>                 URL: https://issues.apache.org/jira/browse/SMX4-794
>             Project: ServiceMix 4
>          Issue Type: New Feature
>    Affects Versions: 4.3.0
>            Reporter: Gert Vanthienen
>            Assignee: Gert Vanthienen
>             Fix For: 4.4.0
>
>         Attachments: parent.xml
>
>
> When people start developing application for ServiceMix, they quickly find 
> themselves defining version and dependencies for the different bits (Camel, 
> ActiveMQ, ...) that have to be kept aligned every time they upgrade to a new 
> version of ServiceMix.  We should provide them with a convenience POM they 
> can inherit from/import into their POMs to make it possible to upgrade by 
> just altering that one POM.
> I don't think our current features' root POM, although it has all the 
> dependencies in there, is a good match here because that also has a lot of 
> stuff that is really specific to building ServiceMix itself rather than for 
> building bundles for ServiceMix, so we should probably create a new POM 
> especially for this goal from the information we have in our build.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to