Thomas, As I expected, I can't reproduce your problem. I put the buildCommand that you've included into the .project file for an eclipse project, run eclipse:eclipse and it stays put. Are you running eclipse:clean? That would completely remove and regenerate the .project file. Otherwise, I'm pretty sure that eclipse:eclipse only modifies the .classpath file.
By the way, I'm using v2.3 of the eclipse plugin. Do you have a different one? On 4/26/07, Thomas Van de Velde <[EMAIL PROTECTED]> wrote:
I am using the Eclipse plugin for Maven to add a builder so that upon every clean the resources:resources goal gets invoked. This avoids the tedious process of keep filtered resources up to date after a clean in Eclipse. The output for this in the .project file looks as follows: <buildCommand> <name>org.eclipse.ui.externaltools.ExternalToolBuilder</name> <triggers>full,incremental,</triggers> <arguments> <dictionary> <key>LaunchConfigHandle</key> <value><project>/.externalToolBuilders/Repository Resources [Builder].launch</value> </dictionary> </arguments> </buildCommand> Whenever I regenerate the project with eclipse:eclipse, this section gets wiped out and I need to add it again manually. I haven't found a way to add these more complicated buildCommand to the maven-eclipse plugin. The maven-plugin only seems to support simple buildcommands. Any solutions for this? I have trouble understanding that both the m2 eclipse plugin and the maven-eclipse plugin have not solved this issue. I would assume this is a common requirement for anybody using filters.
-- Gregory Kick http://kickstyle.net/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
