FYI, this in the configs/pom.xml should do the trick:

    <build>
        <plugins>
            <!--
| NOTE: Currently to build CAR files, we need to ensure that the module has been cleaned first | otherwise the second time around the build will fail.
             -->
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-clean-plugin</artifactId>
                <executions>
                    <execution>
                        <goals>
                            <goal>clean</goal>
                        </goals>
                        <phase>validate</phase>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </build>

--jason


On Jul 1, 2006, at 12:47 PM, David Jencks wrote:

The packaging plugin needs to be made to do a clean first, the m1 plugin did this with jelly.

I always run mvn -o clean install inside configs, which is annoying, but I haven't had time to investigate how to do "clean" from within an m2 plugin. Maybe you or someone else knows how?

thanks
david jencks

On Jul 1, 2006, at 12:17 PM, Jason Dillon wrote:

This happens during the m2 build... and actually the build ends up cycling between 2 errors, this one and another that is an internal plugin error regarding some JCL classes...

:-(

At least it appears to switch back and forth between these two errors and is not completly random... but still its _whack_ that the same build fails in different ways on consecutive runs.

I was just running this over and over:

    mvn -o -Dmaven.test.skip=true

(with changes applied from GERONIMO-2161)

--jason


On Jul 1, 2006, at 12:08 PM, Jacek Laskowski wrote:

On 7/1/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Is there any reason why a rebuild (with no clean) would cause errors
like this:

<snip>
[INFO]
------------------------------------------------------------------- -----
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------- -----
[INFO] java.lang.reflect.InvocationTargetException

Configuration already exists: org.apache.geronimo.configs/rmi- naming/
1.2-SNAPSHOT/car
</snip>

Just a guess, isn't Geronimo already populated with the config and
thus the error? I believe the script uses deploy nor redeploy. What
command did you use? It's M1 build, isn't it?

--jason

Jacek

--
Jacek Laskowski
http://www.laskowski.net.pl



Reply via email to