Brett Porter wrote: > That's actually a bug we need to fix. While the resolution technique > might be "latest" instead of "nearest", I think the version in the > current POM should always win. Yes :)
> You could actually do this by using > [1.3.02] in the mean time, How do I specify this? <version>[1.3.02]</version> creates a NPE. > or you can add exclusions for those > introducing the other xml-apis (trace that using -X). If you actually > think they are erroneous in the first place, feel free to file a MEV > JIRA issue. > > The xml-apis situation is quite a mess and unfortunately 2.0.2 seems > very prevalent. It would be fantastic if we could get some sanctioned > releases to use instead (or can we use jaxp-1.3?) > I was thinking about using a new name like xml-commons-apis as it is a sub project of the xml-commons project. This would solve the mess but introduce a new name. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
