Just to see if it would work, I moved the child-dep-jdk15 dependency out of profiles and moved it into <dependencies></dependencies> (outside of profiles). It still fails with the same stack trace. Any idea why? I can get the build to pass if I leave out that dependency altogether, but that's not really an option without significant code rewriting.
I'm also curious about why including a dependency in a profile is not a good idea (as is using profiles at all). I'm working on a large codebase and would need to explain to the rest of the team before making such changes. Where can I read up on best practices about this? On Wed, Apr 11, 2012 at 1:29 PM, Wayne Fay <wayne...@gmail.com> wrote: > > I've managed to do to get the build to succeed is to (1) remove the > > dependency listed within <profiles></profiles> of child-alpha, or (2) > first > > For a ton of reasons, including a dependency in a profile is a really > terrible thing to do. The very first thing I would do would be to > remove it. > > In fact, I'd do everything I could to remove the use of profiles from > your build entirely. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
