I've used both M2 and M3 builds for Spring-based apps and done many component scans. I've never heard of the well-known issue nor had problems with doing so.
I agree with Wayne it is a Spring question at this point, unless you can demonstrate how, as Wayne says, the M2 vs M3 build difference causes the problem. On Wed, May 25, 2011 at 1:49 PM, Wayne Fay <wayne...@gmail.com> wrote: >> Just to Make a scenary: I am Having a well known problem about Spring can't >> do a Component Scan aganinst a jar generated by Maven 2. >> >> Apparently this happens because the generated Jar does not add its Directory >> Entries. > > If you can take the Maven-generated Jar file and modify it such that > it works in Spring, then you can come back and tell us the difference > and ask how to configure things to compensate for those differences. > > You may have better luck with this question on a Spring forum. I don't > even understand what you're asking. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
