camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ioannis Canellos (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-4013) examples - Do not inherit pom.xml from parent to make it easy to copy example
Date Fri, 27 May 2011 14:14:47 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040245#comment-13040245
] 

Ioannis Canellos commented on CAMEL-4013:
-----------------------------------------

An alternative would be to inherit from their parent pom, but continue to work even if the
parent definition is removed.

What I suggest is to keep the parent definition, for release purposes, but make the project
autonomous.
By autonomous I mean that the project should not inherit properties, dependencies, plugins
etc.

> examples - Do not inherit pom.xml from parent to make it easy to copy example
> -----------------------------------------------------------------------------
>
>                 Key: CAMEL-4013
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4013
>             Project: Camel
>          Issue Type: Improvement
>          Components: examples
>    Affects Versions: 2.7.0
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.9.0
>
>
> We should not inherit any parent pom.xml files in any of the examples. Instead we should
make the pom.xml file completely standalone. Then its easier for end users to copy the examples
and customize those to their needs. For example to adjust camel version and whatnot.

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

Mime
View raw message