You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the repo naively assumes that Javadoc bundles will be available as <symbolic-name>.javadoc_<version>.jar, which does not actually seem to be a standard. In my cursory looking around, I don't see a real standard at all, in fact - it could just be up to publishing the Javadoc online.
In lieu of a real standard, maybe the next best would be to look for embedded Maven metadata and, if present, try to proxy the request along to Javadoc artifacts already published on Maven central. It'd be too dangerous to try to use true Maven resolution inside a resolution request, so maybe it'd make sense to hard-code some Maven central URL(s) to check.
The text was updated successfully, but these errors were encountered:
Currently, the repo naively assumes that Javadoc bundles will be available as
<symbolic-name>.javadoc_<version>.jar
, which does not actually seem to be a standard. In my cursory looking around, I don't see a real standard at all, in fact - it could just be up to publishing the Javadoc online.In lieu of a real standard, maybe the next best would be to look for embedded Maven metadata and, if present, try to proxy the request along to Javadoc artifacts already published on Maven central. It'd be too dangerous to try to use true Maven resolution inside a resolution request, so maybe it'd make sense to hard-code some Maven central URL(s) to check.
The text was updated successfully, but these errors were encountered: