I need to give this a shot within the next 1-2 weeks. If you can wait that long I can give you an entire description how to do your own local releases. If you need it faster feel free to play around and provide the patches to the code and the documentation youself; nevertheless, since fuse & talend do their own releases I'm not sure if it's really a problem with the versions.
Basically, to do own releases, you need to replace the apache ueber parent with your own (which is basically a copy of the apache ueber pom where the distributionManagement/repository sections are corrected). The same parts will need to be adapted locally for karaf. This should do the trick; what other problems do you encounter? What exactly are the errors? Kind regards, Andreas On Sat, Apr 28, 2012 at 07:42, Brian Topping <[email protected]> wrote: > Hi all, > > I've created some patches in https://issues.apache.org/jira/browse/KARAF-1390 > that I'd like to have in my workflow. Every morning, I end up with new > downloads from Hudson because the snapshots have changed. Makes good sense, > so I wanted to create a locally released plugin that I could use until the > patches get applied in one form or another. > > First, I tried to version the plugin POM and do a build, but I believe that > didn't work because of a large number of ${project.version} property > substitutions throughout the POMs, causing the dependency POMs to not have a > version of a dependency with my newly created ${project.version} and filed > https://issues.apache.org/jira/browse/KARAF-1421 toward it. > > But I am realizing that may not be the case, as I tried to substitute all the > version numbers on all the POMs and do a build and it still fails. (I > realize it's a large dependency chain that would be built, but I don't have > time to waste on this.) > > Does anyone have ideas they could share on how to work around this? > > Thanks, Brian
