We need to delete target/repository to preserve the work done by the earlier operation (car:dependencies). The M2 plugin will also have code to delete this directory. Since we run both M1 and M2 builds and the generated plans are different for each, it is necessary to delete the target directory. I found this error to be very useful in making sure M2 build doesn't operate on the plans generated by M1 build! :)
Thanks Anita > 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 --- anita kulshreshtha <[EMAIL PROTECTED]> wrote: > This helped us ensure that we always have a clean environment for > the configuration being packaged. As soon as we have our first server > that starts, this restriction will be removed. > > Thanks > Anita > > --- 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> > > > > --jason > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
