I'm not honestly sure if its a bug or not... It really depends on how the versions are specified in the various poms. You can use <version>[1.1.3]</version> to lock-in a specific version; its possible the acegi pom specifies this explicitly, so Maven will not automatically upgrade all your spring artifacts to the 1.2.4 release as you might hope/expect.
You'll need to do more research into these specific artifacts to figure out what's going on... And then perhaps file as a bug, if necessary. Wayne On 5/17/06, Douglas WF Acheson <[EMAIL PROTECTED]> wrote:
Thx, I thought so. Do you see this as a defect, or is this the way things are supposed to work? I have no problems logging this as a defect (if that is what it is) and manipulating the pom file as a work around. My concern is how many times will this I have to do this (rhetorical question). So I guess what I am asking is, is this really a bug? Regards, Douglas WF Acheson On Wed, 2006-05-17 at 12:20 -0500, Wayne Fay wrote: > You could download the acegisecurity source code, "move it" under your > own company's groupId, modify the pom so it uses the newer Spring > 1.2.4, build and deploy it to your local corporate repo. > > Then adjust your own project's pom to reflect the new groupId etc. > > I'm sure this is more painful than you're probably interested in > dealing with, but it would work... > > Wayne > > On 5/17/06, Douglas WF Acheson <[EMAIL PROTECTED]> wrote: > > Hello, > > > > Thanks for the response. I wen through the exercise of using -X to > > resolve my compile issues when I started to use Maven2. > > > > What happens (found out by using -X) is that Spring 1.1.3 is added to > > the classpath via the acegi (0.7) dependency, even though I have > > explicitly put the Spring 1.2.4 as a direct dependency in my pom.xml. It > > adds it before Spring 1.2.4. So, to remove this from the classpath I > > used the exclusion on the acegi dependency, and that worked. > > > > Now site does not work, grrr .... > > > > Regards, > > Douglas WF Acheson > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
