>>>>> "Eric Redmond" <[EMAIL PROTECTED]>: > If you're getting syntax errors, its probably your pom's > syntax. That has nothing to do with your project structure that > would give errors of other kinds.
You're right. I'd copied the <plugins> element that seemed to be on the top level in the original pom.xml file I ripped it on, into the top level of the new pom. I had to enclose it into a <build> element. > To answer your question: it is ok to not create artifacts. Artifact > creation is only (usually) done at the package phase anyway, so as > long as you execute a phase before it - or only execute goals (that > don't create artifacts - or require a project structure you don't > honor) you should be fine. Right! Thanx! After I'd posted my message, I studied this URL closer http://docs.codehaus.org/display/MAVENUSER/Eclipse+Plugin and used the "validate" goal, rather than the "install" or "deploy" goals, and that seemed to work, ie. pull files out of the maven repository. (Well, at least it's partly working... The eclipse:make-artifacts goal doesn't install all of the dependencies that's needed to create a single runtime. It seems I have to specify the platform (ie. win32 or linux.gtk.x86) in some manner in the POM or as arguments to the maven command, and I'd hoped to avoid that. But that's a different issues) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
