| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
see https://github.com/scala/scala-dev/issues/72 for details
|
|
|
|
|
|
|
|
|
|
| |
I imagine these date back to old Subversion days and are probably the
result of inadvertent commits from Windows users with vcs client
configs.
having the bit set isn't really harmful most of the time,
but it's just not right, and it makes the files stand out in directory
listings for no reason
|
|
|
|
|
|
|
| |
This reverts commit 8986ee4fd56c53d563165d992185c6c532f35790.
Scaladoc seems to work reliably for 2.11.x. We are using it in the IDE builds and haven't noticed any
flakiness, so we'd like to get reinstate this test.
|
|
|
|
|
|
|
|
| |
Francois is investigating the root cause as part of his
work on stabilizing Scaladoc preview in the IDE.
The test seems to only fail on the windows nightly build.
I suspect this is due to a slower or loaded machine.
|
|
|
|
|
|
| |
for given fragments. Don't type-check when forcing doc comments, but rather
do it directly. Test the new functionality as well as better tests for
the old one.
|
| |
|
|
|
|
| |
Refactor scaladoc base functionality to allow it to be mixed in with Global in the IDE.
|
|
|