Debugging.builds

Debugging the build

For those mysterious times when Eclipse doesn't complain about errors but the jar never works anyway.

What I do after the update has been built.

• If there are any log.zip, open them up and make sure to address any errors. Somehow.

When there are no more errors and the update site built but instllation fails. Or the installation succeeds and the editor fails to load the MarkdownEditor class.

• Make sure that the excludes in the pom.xml are removed. When they are removed, update the project using maven. It will correct the classpath that it broke.
• Make sure that the build.properties are like so:

source.. = src/main/java/,\
               org/,\
               target/,\
               src/main/java/github_markdown_css/
src.includes = src/
jars.extra.classpath = commonmark-0.11.0.jar,\
                       commonmark-ext-gfm-strikethrough-0.11.0.jar,\
                       commonmark-ext-gfm-tables-0.10.0.jar
output.. = target/classes/,\
           target/test-classes/
bin.includes = plugin.xml,\
               src/main/java/github_markdown_css/,\
               org/

• Eclipse will probably not see the changes you made to the file on the filesystem. Check the correct properties within build.properties using the package explorer.

If markdownEditor class fails to load due to an exception regarding BufferedReaderWrapper, it's probably because it can't find the github_markdown_css files. Check if the submodules are cloned and rebuild the jar.

git submodule init
git submodule update
git pull --recurse-submodules

When all of these are fine, last effort is to unzip the jar exported, unzip the jar within plugins/ and make sure that the classes are actually built. And I have never had to do anything else except note that nothing built...I just force build again and it was included. I blame Eclipse.