In addition, the parent groupId and version can be inherited by the
pom file, so the pom file header can be reduced from:

  <groupId>org.apache.stanbol</groupId>
  <artifactId>org.apache.stanbol.ontologymanager.web</artifactId>
  <version>0.10.0-incubating-SNAPSHOT</version>
  <packaging>bundle</packaging>

to:

  <artifactId>org.apache.stanbol.ontologymanager.web</artifactId>
  <packaging>bundle</packaging>

This should make it easier to maintain the pom files.

On 18 May 2012 15:38, Peter Ansell <[email protected]> wrote:
> Some dependencies in the trunk doesn't seem to have been migrated
> across from 0.9.0-incubating-SNAPSHOT to 0.9.0-incubating and then to
> 0.10.0-incubating-SNAPSHOT completely.
>
> Is there an intentional slow migration of the versions of some packages 
> across?
>
> The examples I am looking at right now are ontologymanager.registry:
>
>    <dependency>
>      <groupId>org.apache.stanbol</groupId>
>      
> <artifactId>org.apache.stanbol.commons.stanboltools.datafileprovider</artifactId>
>      <version>0.9.0-incubating</version>
>    </dependency>
>    <dependency>
>      <groupId>org.apache.stanbol</groupId>
>      <artifactId>org.apache.stanbol.commons.stanboltools.offline</artifactId>
>      <version>0.9.0-incubating</version>
>    </dependency>
>    <dependency>
>      <groupId>org.apache.stanbol</groupId>
>      <artifactId>org.apache.stanbol.ontologymanager.ontonet</artifactId>
>      <version>0.9.0-incubating</version>
>    </dependency>
>    <dependency>
>      <groupId>org.apache.stanbol</groupId>
>      <artifactId>org.apache.stanbol.commons.owl</artifactId>
>      <version>0.10.0-incubating-SNAPSHOT</version>
>    </dependency>
>
> and ontologymanager.web (which doesn't use the new
> ontologymanager.registry code!):
>
>      <groupId>org.apache.stanbol</groupId>
>      <artifactId>org.apache.stanbol.commons.indexedgraph</artifactId>
>      <version>0.9.0-incubating</version>
>    </dependency>
>    <dependency>
>      <groupId>org.apache.stanbol</groupId>
>      <artifactId>org.apache.stanbol.commons.web.base</artifactId>
>      <version>0.9.0-incubating</version>
>    </dependency>
>    <dependency>
>      <groupId>org.apache.stanbol</groupId>
>      <artifactId>org.apache.stanbol.ontologymanager.ontonet</artifactId>
>      <version>0.10.0-incubating-SNAPSHOT</version>
>    </dependency>
>    <dependency>
>      <groupId>org.apache.stanbol</groupId>
>      <artifactId>org.apache.stanbol.ontologymanager.registry</artifactId>
>      <version>0.9.0-incubating</version>
>    </dependency>
>    <dependency>
>      <groupId>org.apache.stanbol</groupId>
>      <artifactId>org.apache.stanbol.commons.owl</artifactId>
>      <version>0.10.0-incubating-SNAPSHOT</version>
>    </dependency>
>
> I typically declare module dependency versions like the following to
> avoid these inconsistencies, so that the version and groupId only have
> to be set once in the parent section for each POM file:
>
>    <dependency>
>      <groupId>${project.groupId}</groupId>
>      <artifactId>org.apache.stanbol.commons.owl</artifactId>
>      <version>${project.version}</version>
>    </dependency>
>
> Cheers,
>
> Peter

Reply via email to