I would still ping the velocity list, too. They might have had someone else encounter this already.
On Thu, Apr 15, 2010 at 10:47 AM, Ludwig Magnusson <[email protected]> wrote: > Ok, I'll do that and hope it won't be too much to manage =) > Thanks > /Ludwig > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of James Carman > Sent: den 15 april 2010 16:34 > To: Commons Users List > Subject: Re: Problems with old and new group id > > Well, I'd play around with doing excludes in your maven setup. > > On Thu, Apr 15, 2010 at 10:31 AM, Ludwig Magnusson > <[email protected]> wrote: >> Well the problem is still that the project I depend on (turbine) will > still >> have its velocity.velocity dependency. It does not matter if there is a >> "correct" one available, right? >> And this was just an example. There are lot of other dependencies that >> create the same problem. >> /Ludwig >> >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] > On >> Behalf Of James Carman >> Sent: den 15 april 2010 16:21 >> To: Commons Users List >> Subject: Re: Problems with old and new group id >> >> I would suggest you bring this up to the Velocity community: >> >> http://velocity.apache.org/contact.html >> >> What we would hopefully do here in Apache Commons is that we would >> change the package name so that there are no naming collisions even if >> both jars are on the classpath. >> >> On Thu, Apr 15, 2010 at 10:14 AM, Ludwig Magnusson >> <[email protected]> wrote: >>> Hi! >>> >>> I have a dependency in my project that in turn depends on velocity 1.5. >> More >>> precisely velocity.velocity (maven 1 layout). >>> >>> However, my project also _directly_ depends on velocity 1.6.3 or, >>> org.apache.velocity.velocity (maven 2 laoyt). >>> >>> Maven doesn't understand that these are different versions of the same >>> artifact. Is there a way to solve this, because now two velocity packages >>> are added to my classpath. It seems like this would be a very common >> problem >>> with some kind of solution but I can't find information about it. >>> >>> /Ludwig >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
