I would also like do create a custom component or tweak exisitng components. I have downlaoded the source code for Fuse from the below link
I am not able to compile the code as there is a pom error.
Project build error: Non-resolvable parent POM: Failure to transfer org.fusesource:fuse-project:pom:7.2.0.redhat-024 from http://repo.fusesource.com/nexus/content/groups/m2-proxy was cached in the local repository, resolution will not be reattempted until the update interval of fusesource-proxy has elapsed or updates are forced. Original error: Could not transfer artifact org.fusesource:fuse-project:pom:7.2.0.redhat-024 from/to fusesource-proxy (http://repo.fusesource.com/nexus/content/groups/m2-proxy): Access denied to http://repo.fusesource.com/nexus/content/groups/m2-proxy/org/fusesource/fuse-project/7.2.0.redhat-024/fuse-project-7.2.0.redhat-024.pom . Status code 401 and 'parent.relativePath' points at wrong local POM
Any idea how to get rid of this error.
What do you mean with a custom component?
Do you mean a custom Camel component? If so read this docs
From Fuse IDE you can create a new Fuse project ... -> camel-archetype-component.
And it creates a custom component with sample code. You can then adjust this sample code.
That repo reference has been removed already in trunk but not in a release yet AFAIK. You can just comment out the http://repo.fusesource.com/nexus/content/groups/m2-release-proxy references in the root level pom.xml.
Incidentally the web based camel editor is a little ahead of Fuse IDE in terms of component discovery & custom palettes. If you check out the CamelOne keynote I did this shows our iPaaS (basically Fuse running in the cloud & using a web browser to interact with it); you'll notice that the palette is dynamic; at one point we edit the Profile (i.e. configuration of a group of servers) - about 7:43 minutes into the video-to add new camel features and then the palette updates in the camel editor to reflect the new components available.
We'll hopefully be adding this capability soon in Fuse IDE as well. Its using the usual Camel approach to writing components which are then discovered using the META-INF/services/org/apache/camel/component/FOO file where FOO is your components scheme.
In addition for better tooling there are some new hooks in Camel 2.12 to make tooling for custom components easiler such as: