[
https://issues.apache.org/jira/browse/DERBY-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562728#comment-13562728
]
Kristian Waagan commented on DERBY-6052:
----------------------------------------
The changes went in with revision 847783.
Knut, do you see the modified PNGs on Linux? I'm seeing them on Solaris and
Windows.
Myrna, some comments to what you're seeing:
o the PNGs seem to be a problem for several platforms. Tracked by [1], I think.
o the Japanse characters problem can be fixed by using an appropriate locale /
encoding, and is not a problem with the Windows platform itself.
o the CSS diffs issue is another problem with developers on multiple
platforms. We can get rid of it on one platform, but then it pops up on
another...
Regarding the CSS problem, I don't know what tool/technology is used to write
them to disk, but I'd guess they're constructed by Cocoon somehow.
Another tip: Be careful with "forrest clean"... You'd be better off reverting
build/site and manually deleting the other directories within build/. If you
run the target you'll have to check out build/site again, and that takes a
while. This brings me to a discussion we should have at some point, which is
whether we want to keep hosting really old docs in the current representation
indefinitely.
[1] https://issues.apache.org/jira/browse/FOR-915
> Text files under build/site do not have svn:eol-style=native
> ------------------------------------------------------------
>
> Key: DERBY-6052
> URL: https://issues.apache.org/jira/browse/DERBY-6052
> Project: Derby
> Issue Type: Bug
> Components: Web Site
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
>
> Text files under build/site in the site repository, which points to [1],
> don't have the svn:eol-style=native set.
> This is a problem because:
> o it messes up your diffs on some platforms
> o building the site on some platforms ('forrest site') takes a long time (I
> observed 24 minutes on my machine)
> Regarding the second item above, 'svn st' told me there were 16121 changed
> files. I expected two files to have changed... Turns out Forrest will fix the
> line endings, and even when they are already correct all the checked in docs
> files seem to be scanned. A second run took around 5 minutes on my Windows
> machine.
> While 5 minutes is better than 24 minutes, it's still significant. I've heard
> others can build the site in 30 seconds, but I don't know if the fix crlf
> target isn't run on those platforms,or if the file system in question is a
> lot faster.
> As a reminder, people should consider downloading this file [2] to configure
> Subversion wrt EOL style.
> [1] https://svn.apache.org/repos/infra/websites/production/db/content/derby/
> [2] http://apache.org/dev/svn-eol-style.txt
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
