Are you generating any reports using the spotfire plugin and/or perhaps generating code coverage reports? Those have helped me identify whats going on in the past. What you describe sounds like a dependency issue within your modules. As others have mentioned, seeing a POM or some output would help. Beyond that it is very difficult to speculate on what is going on. Personally, I would try putting everything into an aggregator project and see what happens. Perhaps run install instead of compile so update compilation units are installed in your local repo. Those are the things I would do.
On Thu, Oct 31, 2013 at 9:00 AM, Russell Gold <[email protected]> wrote: > No need to specify. Any plugins bound to generate-sources will run before > the compile phase. Are you using custom plugins? Multiple modules? > > Maybe show us your pom? > > On Oct 31, 2013, at 11:23 AM, Andrew Pennebaker <[email protected]> > wrote: > > >> It sounds as though you might have intermittent tests. > > > > > > Good guess, but no. In my case, I had refactored the arity of some > > constructors, without updating all the code calling the constructors. On > my > > machine, `mvn test` showed everything passing. Wasn't until a coworker > ran > > `mvn test` on her computer that we saw a test failure. > > > > Also, on her computer, `mvn install` failed due to missing generated > > sources. Would be nice if I could specify in the pom that the > > `generate-sources` task is required before `mvn compile`. > > > > I'd like Maven tasks to work more like Make tasks, so that everything > > downstream gets updated based on upstream file changes. > > > > -- > > Cheers, > > > > Andrew Pennebaker > > [email protected] > > ----------------- > Author, Getting Started with Apache Maven < > http://www.packtpub.com/getting-started-with-apache-maven/video> > > Come read my webnovel, Take a Lemon <http://www.takealemon.com>, > and listen to the Misfile radio play < > http://www.fuzzyfacetheater.com/misfile/>! > > > > > > > >
