Check http://jira.codehaus.org/browse/MAVEN-1087
On 5/20/05, David Jackman <[EMAIL PROTECTED]> wrote: > After I sent this I found this on the mail archive from 23 November 1994 > (http://www.mail-archive.com/[email protected]/msg14797.html): > > "search the archives for more information (typically it refers to tlds). > Fixed in 1.1. The JIRA roadmap for 1.1 will have it listed. (1.0.1 does > not contain the fix, it is not backwards compatible)." > > Is this still the case? > > ..David.. > > > -----Original Message----- > From: David Jackman [mailto:[EMAIL PROTECTED] > Sent: Friday, May 20, 2005 10:15 AM > To: Maven Users List; Brett Porter > Subject: RE: Dependencies with the same artifactId/groupId but a > different type > > This doesn't work. It still ignores the second dependency that has the > same groupId and artifactId as a previous one. Changing the artifactId > will get it noticed, so my workaround was to change the artifactId then > use the <jar> element to "fix" the filename back to what it should be > (with the original artifactId). It's ugly but it works. > > What does "known issue" in this case mean? Is it something that is > going to be fixed? In M1.1 or M2 timeframe? > > ..David.. > > > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Saturday, May 14, 2005 7:53 PM > To: Maven Users List > Subject: Re: Dependencies with the same artifactId/groupId but a > different type > > put the first part of "type" into the version as a workaround. > > - Brett > > On 5/14/05, Arik Kfir <[EMAIL PROTECTED]> wrote: > > > > ----- Original Message ----- > > From: "Julien Kirch" <[EMAIL PROTECTED]> > > To: "Maven Users List" <[email protected]> > > Sent: Saturday, May 14, 2005 1:28 PM > > Subject: Re: Dependencies with the same artifactId/groupId but a > > different type > > > > >> It seems that maven does not correctly handle identical > > >> dependencies with only different types - is this true? Each of > > >> these dependencies DOES get downloaded if I comment the other two. > > > > > > Hi, > > > > > > It's a known issue in maven 1 > > > > Is there a way to go around it? Perhaps even manual dependency > > downloading in maven.xml or something of the sort? > > > > > > > > Regards > > > > > > Julein > > > > > > -------------------------------------------------------------------- > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
