You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2011/05/25 23:07:47 UTC

[jira] [Created] (CAMEL-4013) examples - Do not inherit pom.xml from parent to make it easy to copy example

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

[jira] [Commented] (CAMEL-4013) examples - Do not inherit pom.xml from parent to make it easy to copy example

Posted by "Ioannis Canellos (JIRA)" <ji...@apache.org>.
    [ 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

[jira] [Commented] (CAMEL-4013) examples - Do not inherit pom.xml from parent to make it easy to copy example

Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CAMEL-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040266#comment-13040266 ] 

Daniel Kulp commented on CAMEL-4013:
------------------------------------


For CXF, the default "mvn install" build does not include the examples or the distribution (tarballs) as they take too long and likely not to really be impacted by developer changes.   We have a separate "everything" profile that does add those back into the build.   The "deploy" builds in Jenkins are setup to run with the everything profile to catch issues.

HOWEVER, it does change the release process slightly.   Instead of "mvn release:prepare", you need to make sure you do "mvn release:prepare -Peverything" to make sure everything is released.



> 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

[jira] [Commented] (CAMEL-4013) examples - Do not inherit pom.xml from parent to make it easy to copy example

Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
    [ 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

[jira] [Commented] (CAMEL-4013) examples - Do not inherit pom.xml from parent to make it easy to copy example

Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CAMEL-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040251#comment-13040251 ] 

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

That is an idea, examples being small, their poms won't get too big that way.

This doesn't address however the other problem (not the object of this jira, but important nevertheless) of examples taking time during build, not being really relevant for camel in production, increasing the distro size *and* increasing in number from a release to another. Do we want to move examples somewhere else? Or any other good solution? Because the current model doesn't scale :).

> 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

[jira] [Updated] (CAMEL-4013) examples - Do not inherit pom.xml from parent to make it easy to copy example

Posted by "Claus Ibsen (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-4013:
-------------------------------

           Fix Version/s:     (was: 2.9.0)
                          Future
    Estimated Complexity: Novice
    
> 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: Future
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CAMEL-4013) examples - Do not inherit pom.xml from parent to make it easy to copy example

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CAMEL-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044784#comment-13044784 ] 

Claus Ibsen commented on CAMEL-4013:
------------------------------------

Frankly I dont care if "its dont scale" and I dont see that problem.

Instead what matters is that its easier for new users of Camel to get started. The download the ZIP file, extract it. And go in the examples directory and try the examples. Then they copy those examples to a project directory of their own, because they need to build a POC with Camel or whatnot. And then its hard for them to define spring/camel version and whatnot, and not inherit a examples Camel pom.xml file.

And we do not add many examples over the time. So if its been done, then adding a new example should be easy.

> 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