Hi Jörg, Thanks very much! You released one of my agony. a cup of Java, cheers! Sha Jiang
Jörg Schaible wrote: > > jiangshachina wrote on Wednesday, November 22, 2006 2:38 AM: > >> Hi guys, >> I found the key. >> >> In management-1.0.pom, I excludes jta from hibernate dependency. >> At beginning, I didn't use jta-1.0.1B, but j2ee-1.4.jar, because >> jta-1.0.1B.jar isn't at central repository. >> But jta is transitive dependency of yy another dependency >> hibernate-3.0.jar, so I excludes it. >> >> Serval days later, I wanted to use jta directly and installed >> jta-1.0.1B.jar by manual. >> Unfortunately, I didn't remove the statements of excluding. >> >> According to the case, it seems that excluding scripts have higher >> priority. > > No, it is worse. It depends on the internal sequence the deps are > processed. If the local jta declaration is found before the hibernate one, > jta would have been *not* excluded. Since the sequence of this list > changes with every arbitrary added or removed dep (or new version) I > believe that is based on a iterator over a hash map ... which makes it > really annoying. > > The bug is supposed to be fixed since months in subversion though ... like > so many other ones. > > - Jörg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Don%27t-add-dependency--tf2677027s177.html#a7487130 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
