[
https://issues.apache.org/jira/browse/SMX4-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015545#comment-13015545
]
Gert Vanthienen commented on SMX4-794:
--------------------------------------
The parent pom can be used
* by using it as a parent for your own company ServiceMix POM - the benefit is
that you can also access the properties that have been defined, but it does
require you to override e.g. the SCM information and Apache specific
information in that POM
* by using 'import' scope to import all the managed dependencies from this POM
into your own project - the benefit is that this allows the information to be
mixed into any existing POM, but this approach does not allow you to access the
properties that have been defined
> 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
