0

I want to use Apache Camel 2.14.0 in my project, and specifically use the Quickfixj component. However, I want to make some changes to the camel-quickfix component, and deploy those changes to our local Nexus repo for use. The changes would meet certain functionality we are looking for our FIX Engine.

However, the question I have is, in the {local-git-repo}/camel/components/camel-quickfix/pom.xml, I see the following:

<parent>
  <groupId>org.apache.camel</groupId>
  <artifactId>components</artifactId>
  <version>2.14.0</version>
</parent>

<artifactId>camel-quickfix</artifactId>
<packaging>bundle</packaging>
<name>Camel :: QuickFIX/J</name>
<description>Camel QuickFIX/J support</description>

Usually, what I would do is change the version to say, 2.14.1, and then build and deploy to our local nexus repo, so we can reuse the modified component in our local projects. However, with this, it seems to be referring to the parent pom.

How could I go about modifying this component, and yet still have it refer to the camel-core 2.14.0 version and its dependencies?

Or could I just build it as 2.14.0, and hope that when my maven project runs, it picks up the artifact from my thirdparty repo, and not the one from the apache mirror?

Please help, if you are a maven expert :)

Jose
  • 1,616
  • 4
  • 26
  • 38
  • If others can benefit from your needed changes in camel-quickfix, why not contribute to the Apache Camel project? – Claus Ibsen Feb 03 '15 at 06:25
  • That would be a great idea! However, right now I would like to have an internal build, and be able to use it locally. If I see the change is good, I would definitely bring it up for inclusion. – Jose Feb 03 '15 at 14:34

1 Answers1

1

It would be wise to avoid building a different version of 2.14.0 and hoping that the correct version gets pulled from your local repo by maven (which can do apparently strange things at the best of times).

Likewise, I would also avoid future official versioning (2.14.1, etc).

If you can't or aren't willing to contribute your changes to the core build via the Apache project, why not just build a local version, like for example 2.14.0-CUSTOM-1.0?

The version attribute 2.14.0-CUSTOM-1.0 clearly states that this will be a custom build descendant on 2.14.0, plus with your own versioning on the end.

<parent>
  <groupId>org.apache.camel</groupId>
  <artifactId>components</artifactId>
  <version>2.14.0</version>
</parent>

<artifactId>camel-quickfix</artifactId>
<version>2.14.0-CUSTOM-1.0</version>
<packaging>bundle</packaging>
<name>Camel :: QuickFIX/J</name>
<description>Camel QuickFIX/J support</description>

(Remember to use the correct version in your features.xml)

vikingsteve
  • 38,481
  • 23
  • 112
  • 156
  • I totally agree, I don't want to deploy a new official version to the apache repo :) However, I am looking to do a local build with my changes, and deploy that to my local Nexus for use within development team. – Jose Feb 03 '15 at 14:35
  • From your change, I see you added a version to the actual apache component. I will try that. Would this mean building the whole apache camel? or just the component? how would I deploy it to my local repo? – Jose Feb 03 '15 at 14:36
  • Just build the camel-quickfix component. If you start with version `2.14.0-CUSTOM-1.0-SNAPSHOT` you should be able to do the normal `mvn release:prepare release:perform` to put version `2.14.0-CUSTOM-1.0` into your local repo. – vikingsteve Feb 03 '15 at 14:53