Since you're working on this plugin, you don't want there to be any
history, so you can just delete the history (or at least the
dependencies.xml file under src/history) and c-m-p will start over
with a new version of history.... at least that's how I think of it.
I've fixed the flag locally but have a really lot of other changes so
don't want to commit until I have some evidence its all working. I've
been turning on transitive dependencies everywhere and working through
the necessary changes.
thanks
david jencks
On Aug 26, 2008, at 8:06 AM, Lin Sun wrote:
I am able to get around this error.
Initially, there is no history/dependencies.xml file as this is a new
G plugin, so I don't know why I keep getting this error. Then I
changed the pom.xml file to not use mavendependencies, and the c-m-p
generated the history/dependencies.xml file for me. I added the
changed dependencies into the history/dependencies.xml file (my guess
is that they were pulled in via transitive dependencies) and am able
to get a successful build.
Here's what the pom.xml look like - the failOnChange property didn't
seem to work here:
<project>
...
<build>
<plugins>
<plugin>
<groupId>org.apache.geronimo.buildsupport</groupId>
<artifactId>car-maven-plugin</artifactId>
<executions>
<execution>
<id>generate-plugin-metadata</id>
<phase>generate-resources</phase>
<goals>
<goal>prepare-metadata</goal>
</goals>
<configuration>
<useMavenDependencies>
<value>false</value>
<includeVersion>true</includeVersion>
</useMavenDependencies>
<failOnChange>false</failOnChange>
<category>Geronimo Plugin Group</category>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</project>
Lin
