On 10/12/17 00:47, Andrew Grimberg wrote: > The bailing wire and bubble gum that is making javadocs.opendaylight.org > function properly does not make it possible to have a domain name per > project. Plus it would be an extra amount of administrative overhead on > us to do this as it would require extra configuration of puppet > configuration for each project if I could figure out the extra magic needed. > > Each of the projects can be referenced at > https://javadocs.opendaylight.org/${project_short_code} which maps to > the actual official URL of > https://javadocs.opendaylight/${group_id}.${project}
Fair enough, though there is one slight snag -- maven javadoc plugin is
relying on javadocs to be present at a fixed location,
${project.url}/apidocs. I am not sure what else the project's URL is
used for -- right now we point to the project's wiki page.
Would it be possible to add some URL rewrite scheme on the
infrastructure side, so that we can pretend to the outside world we have
a mavenesque per-project structure (say,
http://opendaylight.org/yangtools/) and remap requests to appropriate
hosts (say, http://opendaylight.org/yangtools/**/apidocs ->
javadocs.opendaylight.org/yangtools/)?
Thanks,
Robert
signature.asc
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/infrastructure
