That is not what I meant.

I meant dependences for maven pom files.

We would have an jar file (for example ant-commons-logging.jar that
did not contain any classes) and have a pom file like:

<project>
  <parent>
    <groupId>org.apache.ant</groupId>
    <artifactId>ant-parent</artifactId>
    <relativePath>../pom.xml</relativePath>
    <version>1.8.2</version>
  </parent>
  <modelVersion>4.0.0</modelVersion>
  <groupId>org.apache.ant</groupId>
  <artifactId>ant-commons-logging</artifactId>
  <version>1.8.2alpha</version>
  <description>Ant Listener based on commons-logging</description>
  <dependencies>
    <dependency>
      <groupId>org.apache.ant</groupId>
      <artifactId>ant</artifactId>
      <version>1.8.2</version>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>commons-logging</groupId>
      <artifactId>commons-logging-api</artifactId>
      <version>1.0.4</version>
      <scope>compile</scope>
    </dependency>
  </dependencies>
</project>

This would allow maven users to use ant.jar and specify which optional parts
are needed.

Peter


On Tue, May 18, 2010 at 6:17 AM,  <jan.mate...@rzf.fin-nrw.de> wrote:
>>We could have dummy jar's for dependences.
>>Peter
>
> You could use https://svn.apache.org/repos/asf/ant/sandbox/mocks ;-)
>
> Jan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Reply via email to