2008/9/17 Brad Cox <[EMAIL PROTECTED]> > > hard to know what's going on without an example to play with > > - do you mean the manifest viewer reports errors/warnings? > > Yes. After the seemingly error free run I sent you, eclipse showed errors > everywhere. I've noticed this before. jdom being found by maven, not by > eclipse, even though jdom-1.0.jar is right there in the classpath. I've > attached a screenshot. > > PS: Deleting .svn directories is very not good. Breaks that workspace from > then on. >
yes - that's why I ask maven to try not to delete them when cleaning up, unfortunately maven seems to ignore this exclusion Agree with the theory of not checking these things in when the tools are > reliable. Right now they're not; its important that I retrieve them to > return to a working state. That should be my judgement call, not pax's. > sure, in which case don't use pax:clean (which btw works the same as eclipse:clean) - there's only so much it can infer, just like 'rm' can't know that the file you asked it to delete was really important or not > Stuart McCulloch wrote: > >> 2008/9/17 Brad Cox <[EMAIL PROTECTED]> >> >> Just tried it again and same thing happened. .project disappeared from >>> all >>> the pom modules, and in the others, MANIFEST.MF was completely empty. >>> >>> >> well I'd expect the .project files to disappear from the pom projects, >> because the default setup is to *not* generate .project files for any >> intermediate pom projects - basically because Eclipse doesn't like >> hierarchical projects >> >> Also something seems to be deleting the META-INF directories and >> recreating >> >>> them (.svn suybdirectories are now missing). >>> >>> >> this is because of pax:clean which removes all generated content >> including .project files and the top-level META-INF directories - I've >> tried to tell Maven not to remove any .svn subdirectories if they're >> there, but it still deletes them :( >> >> ...but if you don't call pax:clean then these files won't go missing >> >> ps. where I work we tend to discourage checking in generated files >> especially IDE files, because our developers all use different IDEs >> >> References to org.jdom seemed to resolve successfully, but the eclipse >> >>> manifest wizard can't find them. I'm totally confused. Obviously. >>> >>> >> hard to know what's going on without an example to play with >> - do you mean the manifest viewer reports errors/warnings? >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Cheers, Stuart
