camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadrian Zbarcea (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 Wed, 25 May 2011 21:29:47 GMT

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

Hadrian Zbarcea commented on CAMEL-4013:
----------------------------------------

It is a good goal, that's how the Talend examples are done, but I am not sure how the release
process would work, if at all, because a lot of the release configuration is defined in the
(grand)parents. One option would be to not release examples or more precisely not *all* examples,
especially given the fact that the number of examples is growing (and will continue to grow,
most likely). An examples subproject is an option I considered a while ago, either at apache
or extras, but not sure if it would be a good idea either.

> 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