> the only thing I can suggest is to build from the top and save the > .project / .classpath files, then build locally and save them again. > (perhaps also save the manifest file) > > then compare the 2 sets of files to spot any differences - if these > files are identical then it's another problem between Eclipse and > Maven and you'd have to start comparing differences in the whole > tree (including the target folders) > > if there is a difference in the .project / .classpath files then raise > a JIRA issue and attach both sets of files.
Yep, there's a difference in the files. I'll file a JIRA issue. BTW, I also committed the problematic projects in my lab on ops4j and was able to recreate the problem. Cheers, David _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
