[
http://jira.codehaus.org/browse/MEV-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98240
]
Henri Yandell commented on MEV-524:
-----------------------------------
> for i in commons-*; do find $i -type f -name '*-javadoc.javadoc.jar'; done
commons-configuration/commons-configuration/1.4/commons-configuration-1.4-javadoc.javadoc.jar
commons-digester/commons-digester/1.8/commons-digester-1.8-javadoc.javadoc.jar
commons-io/commons-io/1.3/commons-io-1.3-javadoc.javadoc.jar
commons-io/commons-io/1.3.1/commons-io-1.3.1-javadoc.javadoc.jar
commons-lang/commons-lang/2.3/commons-lang-2.3-javadoc.javadoc.jar
commons-lang/commons-lang/2.2/commons-lang-2.2-javadoc.javadoc.jar
I suspect it's not /javadocs as these are pretty recent commons releases. I'll
dig a bit more; only the commons-lang-2.2 has a good javadoc jar currently, so
for most the fix-by-hand would be to move the file, while for lang-2.2 the bad
file can simply be removed.
> Javadoc jar not uploaded correctly for digester
> -----------------------------------------------
>
> Key: MEV-524
> URL: http://jira.codehaus.org/browse/MEV-524
> Project: Maven Evangelism
> Issue Type: Bug
> Reporter: Henri Yandell
>
> The migration of the javadoc jar from the Apache rsync to the central
> repository doesn't seem to work well for javadocs - or more likely I did
> something wrong. Any thoughts?
> http://repo1.maven.org/maven2/commons-digester/commons-digester/1.8/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
