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
Scaladoc can determine the relative source path for a symbol if -sourcepath is defined and use that to link to the source. However, -sourcepath has unintended side effects and can break compilation. (See this thread.) Scaladoc should instead use its own -doc-sourcepath option. Alternatively, what is currently called -sourcepath should be renamed and hidden behind -X as suggested in the thread.
The text was updated successfully, but these errors were encountered:
@VladUreche said (edited on Jun 13, 2012 10:56:29 PM UTC):
Fixed in 94db9d983c.
EDIT: When using scaladoc, -sourcepath bootstrapping is disabled, thus there's no need for a new name. Keeping the same name avoids breaking existing scripts or having to remove deprecated members in a future release.
Scaladoc can determine the relative source path for a symbol if -sourcepath is defined and use that to link to the source. However, -sourcepath has unintended side effects and can break compilation. (See this thread.) Scaladoc should instead use its own -doc-sourcepath option. Alternatively, what is currently called -sourcepath should be renamed and hidden behind -X as suggested in the thread.
The text was updated successfully, but these errors were encountered: