[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[m2e-dev] Project configuration is not up-to-date with pom.xml
- From: Lance Linder <llinder@xxxxxxxxx>
- Date: Wed, 23 Nov 2011 11:17:36 -0600
- Delivered-to: firstname.lastname@example.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=qxDQBMTV69RmEstTuwNXCWqGAL7dIQJ3TRRNRRM4ZJU=; b=wjFOuE5901TJxTDBN5lgJMPlF+4R0HiyWxr5qr+KdpTOZbcarFz1sZC5u2Ze2f8OKK GZjGwxrP9twYl8CLxtdDRqPhe3FZqaRyIFMX0UoNlRxMHQlBscGmtpXsW2N8TvdHhcrw CllTy9UTzX6HCBkfLQjkKmSA+Vfo1Wn/meWic=
I have had a nagging issue with a custom project configurator since m2e 1.0 was released and I haven't been able to solve it.
When I import a Maven POM the project is configured correctly and everything builds but I always get the error message "Project configuration is not up-to-date with pom.xml. Run project configuration update". Running Maven > Update Project Configuration does resolve it but this seems redundant as the import process already ran the configuration once.
With pre 1.0 builds of m2e I didn't get this problem. Once m2e 1.0 was released I figured I must be doing something wrong but I have never been able to figure out what.
Has anyone else seen this or have ideas of what might be wrong?