Hey all, We're currently having an issue with debugging (and in a way, releasing) our maven based project in IDEA thats both an IDEA issue, and a maven issue (I'd be happy to be told its a ME issue and I'm just doing maven wrong thou).
We have a multi-module project, and when single stepping through code, or clicking through stack traces IDEA insists on sending the editor to .java files inside -sources.jars rather than the versions currently in the project. From what I can tell, the problem lines in that our poms currently look like: - parent - module a v 1.2 - module b v 1.3 - depends on a v 1.1 - module c v 1.1 - depends on b v 1.2 The dependencies declared in modules b and c contain the minimum compilation version required, which isn't neccesarilly the current version of the module. AFAIK, as IDEA sees a reference b version 1.2 as the last thing it scans it seems to want to use that version for ALL references to code in that module, rather than going to the -actual- module b sources. Initially I changed our parent pom to include a <dependencyManagement> section, pinning all the versions of each module which worked for debugging/strack-trace clicking, as the project only knows about b:1.3 - however, this means we can no longer do a maven release of b, if the parent pom currently refers to a SNAPSHOT of a or c, and we end up putting <version> elements back in our module poms. Is there some magic dependency foo I'm missing when using a multi-module (or parented module) setup where the modules have their own release cycles. Mark -- Discouragement is a dissatisfaction with the past, a distaste for the present, and a distrust of the future - Maree De Jong, Life NZ. blog: http://www.talios.com podcast: http://www.illegalargument.com skype / twitter: talios Sent from Auckland, Auk, New Zealand --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
