camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-3470) Document the procedure of adding new components
Date Mon, 03 Jan 2011 05:59:45 GMT

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

Claus Ibsen resolved CAMEL-3470.
--------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Future)
                   2.6.0

Nice. 

I added a note about you need to add the new component to the manual

One last note is actually to add the new component to the distribution kit. Its something
like the following:

Add the new component in the following files:
- parent/pom.xml
- apache-camel/src/main/descriptors/common-bin.xml 

Build the kit by running: mvn clean install from the apache-camel directory. And check the
generated .zip file from the target folder contains the new component.

> Document the procedure of adding new components
> -----------------------------------------------
>
>                 Key: CAMEL-3470
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3470
>             Project: Camel
>          Issue Type: Task
>          Components: documentation
>            Reporter: Christian Müller
>            Assignee: Christian Müller
>            Priority: Minor
>             Fix For: 2.6.0
>
>
> Document the procedure of adding new components (check the license, check the contributed
source code, run the tests and look on the test coverage, run check style, provide a feature
file, ...). I think this will help new committers and also contributors to provide "better"
patches.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message