I'm not part of the maven developers, but on the surface, if any plugin finds two different configurations, it wouldn't surprise me if it ran once for each of them.
On 2/19/07, EJ Ciramella <[EMAIL PROTECTED]> wrote:
We did and that's how we diagnosed this, but that doesn't answer the question if this is a bug or not. Is this what it's supposed to do? Find a surefire configuration and run twice with it? The lowerlevel one is only activated when a profile is activated via a property setting (which works flawlessly). -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Monday, February 19, 2007 12:11 PM To: Maven Users List Subject: Re: [m2] Integration-test target runs integration tests twice... FYI for the future... Next time, use "mvn help:effective-pom" to help diagnose problems like this. Wayne On 2/19/07, EJ Ciramella <[EMAIL PROTECTED]> wrote: > Ok, so I seem to have found out why this is happening. At the top most > pom, we have a minor surefire configuration (we'd like all the unittests > to wind up in one central location for processing). When maven see this > AND the child pom with a different path to that main folder, maven > decides to run the unittests twice. > > If I remove the surefire configuration from the parent pom, maven only > runs the tests once. > > This is a bug with maven2, correct or is this how its supposed to > operate? > --------------------------------------------------------------------- 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]
