Yeah the warning is in place to just show the problem has occurred though you are right that probably managing situations like this in either changes to the dependencyManagement or the pom
Cheers P On 7/3/06, Grant McDonald <[EMAIL PROTECTED]> wrote:
I tried something similar by switching off the lines I mentioned in the issue report. This had the effect of including commons-codec-1.2 instead of 1.3 which actually caused servicemix to completely crash since the versions had different encoding/decoding formats (this was using the trunk as of 2006-06-28 with a few custom patches). When I explicitly added commons-codec-1.3 as a dependency in servicemix-http this problem went away. So it may be that fine tuning is needed in some cases with regards to transitive dependencies (either that or just use the override from the parent pom. -----Original Message----- From: Philip Dodds [mailto:[EMAIL PROTECTED] Sent: Tuesday, 4 July 2006 12:27 AM To: servicemix-dev@geronimo.apache.org Subject: Re: Transitive dependency problem with jbi maven plugin The problem was that the version found through the transitive dependency was not the same as the version from the top level pom's dependency management - I have switched it so that in this case a warning it thrown but the version from the transitive dependency it packaged into the installer. P On 7/2/06, Grant McDonald <[EMAIL PROTECTED]> wrote: > > > This appears to be due to line 181 in GenerateComponentMojo.java in the > jbi-maven-plugin project. At this point the includes are refiltered based > on the JbiResolutionListener created for the project. This seems to eject > some dependencies of subprojects.... needs more investigation. > -- > View this message in context: > http://www.nabble.com/Transitive-dependency-problem-with-jbi-maven-plugin-tf 1879526.html#a5139375 > Sent from the ServiceMix - Dev forum at Nabble.com. > >
