It's not a bug... Those are jar files that can't be redistributed via the website, because of licensing issues.
http://maven.apache.org/reference/standard-sun-jar-names.html Generally, either put them in your internal repository if you have one, or install in your local repository, or specify an exclusion if you really don't actually need it. In the "you really don't need it" case, I think that an "optional" scope for dependencies was added, and as POM's start to use that correctly, you'll pull down less. I'm not sure where that stands currently though... -Stephen On 10/6/05, Daniel Hannum <[EMAIL PROTECTED]> wrote: > I'm using the Maven2 ant tasks and I have the following dependency listed in > my ant script > > <dependency groupId="hibernate" artifactId="hibernate" version="3.0.5"/> > > Problem is, this pulls down easily 20 different sub-dependencies, but one of > them (javax/security/jacc/1.0) is missing a jar (that dir only contains a > pom) > > I tried pulling down spring, but it has a similar problem where > jdbc/jdbc/2.0 is missing a jar. > > What is the solution to this? I know I can just tell maven to exclude the > ones that don't work, but that's a hack. Does this happen often? Is it a > known bug? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Stephen Duncan Jr www.stephenduncanjr.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
