That particular jar is a sun licensed jar so it won't be in the
central repository, you will have to get it yourself, it's POM has the
download url (the POM in the original location, not the new one
http://www.ibiblio.org/maven2/jdbc/jdbc-stdext/2.0/jdbc-stdext-2.0.pom).
See: http://maven.apache.org/maven2/guides/mini/guide-coping-with-sun-jars.html
No need to log a JIRA about the fact that it is missing but you might
log one about the new POM not having the download info in it.
http://jira.codehaus.org/browse/MEV
On 11/1/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Does anyone know where the best place is to log problems with Repository
> Dependencies.
>
> The sort of problems I'm talking about, is .pom file referencing a jar
> that isn't in the Maven2 Repository (e.g.
> http://repo1.maven.org/maven2/javax/sql/jdbc-stdext/2.0/jdbc-stdext-2.0.jar).
>
> I have looked at the various JIRA Maven projects and it isn't clear where
> these issues should be logged. Is there a Repository Administration bug
> list?
>
--
tom
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
