edbras wrote: > >> I suppose exclude is added for you, so JDT won't overwrite them and you >> could run Maven from the command line to get those resource filtered. > > What do you mean ? I don't really understand what you mean. > It's not about maven filtering correclty or not. > It's about the maven eclipse plugin that I don't want to fill in the > exluded/included pattern in the .classpath file. It has to leave this > alone. >
Let me rephrase it. If exclude won't be added there, then Eclipse will copy unfiltered files into the target folder. Assuming that there was some meaning in filtering resources in the first place, such copying won't be correct. So, it is done for your own good. If you don't like that, then you can try move your filters into a profile, so your eclipse:eclipse plugin won't see them. edbras wrote: > >> By the way, out of curiosity, why you are not using Maven integration for >> Eclipse, such as m2eclipse? http://m2eclipse.codehaus.org/ It would >> import >> your project automatically and also configure filtering in the IDE. > > That's true for a simple project but I have several super pom's that > doesn't appear in eclipse, but the sub projects have to appear in eclipse > as projects. > Not really. It is up to you what you want to have in your workspace. m2eclipse will resolve projects from workspace if they are there, but if not, it would resolve artifacts from the local Maven repository. That also work nicely for any parent poms. edbras wrote: > > And I don't see a way to update the .classpath files with m2eclipse when > updating the version of a library... :(.. > That is the beauty of IDE integration, you don't need to update .classpath. Basically, you edit pom.xml in the IDE and classpath is updated for you automatically. With m2eclipse you can also force it using "Maven / Update dependencies" or "Maven / Update snapshots" popup menus on your project. edbras wrote: > > Because my super pom does'n't appear in eclipse, neither can I update my > .classpath files (about 10 of them) in one-go. That is: outside eclipse, I > simple run mvn eclipse:eclipse and it updates all my .classpath files and > also includes the other sub projects as eclipse projects and not as jars. > Which works nice, but I want to configure it to leave my included/exluded > alone... > In case of m2eclipse, the .classpath files don't change when you change dependency declaration in pom.xml. This is done using special classpath container that using pom.xml as source of dependencies, so .classpath is always in sync with pom.xml. There are additional advantages, e.g. you can open/close/import additional dependencies and your project configuration will automatically reflect that, linking or unlinking those projects into other's classpaths. regards, Eugene -- View this message in context: http://www.nabble.com/eclipse%3Aeclipse-resource-filtering---tp19344600p19359218.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
