[Geoserver-devel] building with maven 2.1.0

GeoServer GeoServer Developer
1

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 :slight_smile:

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

2

Justin Deoliveira ha scritto:

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 :slight_smile:

Jalopy reformat is a failed experiment.
I vote for 1 as well.

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

3

+1 on option 1). Get rid of dead code, dead configuration, anything dead!
Justin Deoliveira wrote:

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 :slight_smile:

--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.

4

+1

Jody

On Wed, May 13, 2009 at 12:03 AM, Andrea Aime <aaime@anonymised.com> wrote:

Justin Deoliveira ha scritto:

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 :slight_smile:

Jalopy reformat is a failed experiment.
I vote for 1 as well.

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel