From: Justin D. <jde...@op...> - 2009-05-12 14:09:54
|
However, this one wrinkle, in geotools the build-configs plugin is also used for clover. Is anyone using this? Do we actually still have a license? Given that cobertura does not require a license or any additional configuration i would lean in that direction for reporting code coverage. -Justin Justin Deoliveira wrote: > Originally sent to the geoserver list, but the same problem and > solutions apply. Thoughts? > > Hi all, > > So the source of the problems of not being able to build with maven > 2.1.0 stems from the jalopy setup in the root pom.xml: > > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>jalopy-maven-plugin</artifactId> > <version>1.0-SNAPSHOT</version> > <configuration> > <convention>geoserver/geoserverjalopy.xml</convention> > <failOnError>false</failOnError> > </configuration> > <dependencies> > <dependency> > <groupId>org.geoserver.maven</groupId> > <artifactId>build-configs</artifactId> > <version>1.7.5-SNAPSHOT</version> > </dependency> > </dependencies> > > which depends on the build-configs module. But the build-configs module > inheirets from this pom == kaboom, cyclic dependency. > > So two options to fix: > > 1) Kill the jalopy configuration and the build-configs module since > neither is used > > 2) Ensure that build-configs does not inheiret from the root pom by > removing its parent. To do this we would probably have to duplicate some > of the configuration from the current parent poms. > > I vote for 1 :) > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. |