I don't know if the following behaviour is intended or a bug.
If it is a bug and you want me to file a bug report, please let me know
in which project I should file it in jira.
Assume the following setting:
For a project "x" we produce with a custom goal two artifacts
1. x.dll
2. x.model (for example some model of the component x)
and deploy both to the repository.
Another project needs both these artifacts, and thus states in its pom:
<dependency>
<groupId>y</groupId>
<artifactId>x</artifactId>
<type>dll</type>
<version>0.1</version>
</dependency>
<dependency>
<groupId>y</groupId>
<artifactId>x</artifactId>
<type>model</type>
<version>0.1</version>
</dependency>
In maven-1.0 (I have not tested 1.0.1 yet), the second dependency is
completely ignored, eg.
1. it will NOT be downloaded from central repository
2. some jelly code such as
<j:forEach items="${pom.dependencies}" var="dep">
<ant:echo>"${dep.artifact}"</ant:echo>
</j:forEach>
will NOT produce any output for the second dependency.
=> Question 1: Is this a known limitation of the maven pom concept to
allow only one artifact with a given groupId/artifactId combination or a
bug?
=> Question 2: If bug: Does anyone know whether maven-1.0.1 fixes this?
=> Question 3: If limitation: any proposals for a workaround?
Thanks,
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
