Because one project can "produce" more then one artifact. e.g. JSP tag libs are often distributed as two files: jar + tld file.
You should be able to do <dependency> <groupId>foo</groupId> <artifactId>boo</artifactId> <type>jar</type> <dependency> <dependency> <groupId>foo</groupId> <artifactId>boo</artifactId> <type>tld</type> <dependency> and there is nothing wrong with it. There are more examples like this. At the moment even simple project can "emit" following artifacts: jar (jar:install) javadoc (javadoc:install) java-sources (java:install-src) pom (pom:install) Michal > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 05, 2003 4:06 AM > To: [EMAIL PROTECTED] > Subject: [jira] Commented: (MAVEN-194) Two dependiencise having > the same id but diffrent type should not be assumed as duplicats > > > The following comment has been added to this issue: > > Author: dion gillard > Created: Mon, 4 Aug 2003 9:05 PM > Body: > I'm not sure I agree with the use of artifactType as a differentiator. > > From my angle, artifactId and groupId as a combination should be unique. > > I don't see why type should be taken into account at all. Declare them as > > <artifactId>boo</artifactId> > > and > > <artifactId>boo-web</artifactId> > > --------------------------------------------------------------------- > View the issue: > > http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-194 > > > Here is an overview of the issue: > --------------------------------------------------------------------- > Key: MAVEN-194 > Summary: Two dependiencise having the same id but diffrent > type should not be assumed as duplicats > Type: Bug > > Status: Reopened > Priority: Major > > Time Spent: Unknown > Remaining: Unknown > > Project: maven > Fix Fors: > 1.0-final > Versions: > 1.0-beta-8 > > Assignee: Jason van Zyl > Reporter: Michal Maczka > > Created: Sun, 12 Jan 2003 10:22 AM > Updated: Mon, 4 Aug 2003 12:56 PM > > Description: > Currently in case of following dependincies in POM: > > <dependencies> > <dependency> > <id>mydep</id> > <version>1.0.1</version> > <type>war</type> > </dependency> > </dependencies> > > > <dependencies> > <dependency> > <id>mydep</id> > <version>1.0.1</version> > <type>jar</type> > </dependency> > </dependencies> > > only the first dependency will be availabe in dependency list. > > Solution: > > Both "id" and "type" should be used in > org.apache.maven.project.BaseObject and two dependincies should > be assumed as equal only if > dep1.id == dep2.id > && > dep1.type == dep2.type > > > > > > --------------------------------------------------------------------- > JIRA INFORMATION: > This message is automatically generated by JIRA. > > If you think it was sent incorrectly contact one of the administrators: > http://jira.codehaus.org/secure/Administrators.jspa > > If you want more information on JIRA, or have a bug to report see: > http://www.atlassian.com/software/jira > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > ---------------------------------------------------------------------- > Portal INTERIA.PL zaprasza... >>> http://link.interia.pl/f174b > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
