Disable unwanted modules by default

[RadekCap]

By #61 we probably introduced loading of some modules. When you run application from the latest source code, the message box appear with warning:

Warning - could not install some modules: JSch Agent Proxy library - The module named com.jcraft.jsch was needed and not found.
HTML Validation - The module named org.apache.commons.logging was needed and not found.
Mylyn Support Utilities - The module named org.eclipse.mylyn.commons.net was needed and not found.
Mylyn Support Utilities - The module named org.eclipse.mylyn.tasks.core was needed and not found.
Mylyn Support Utilities - The module named org.eclipse.core.jobs was needed and not found.
Mylyn Support Utilities - The module named org.eclipse.mylyn.wikitext.core was needed and not found.
Mylyn Support Utilities - The module named org.eclipse.equinox.common was needed and not found.
Mylyn Support Utilities - The module named org.eclipse.core.runtime was needed and not found.
Local Tasks - The module named org.eclipse.mylyn.tasks.core was needed and not found.
Local Tasks - The module named org.eclipse.equinox.common was needed and not found.
Local Tasks - The module named org.eclipse.core.runtime was needed and not found.
Bugzilla - The module named org.eclipse.mylyn.commons.net was needed and not found.
Bugzilla - The module named org.eclipse.mylyn.bugzilla.core was needed and not found.
Bugzilla - The module named org.eclipse.mylyn.tasks.core was needed and not found.
Bugzilla - The module named org.eclipse.equinox.common was needed and not found.
Bugzilla - The module named org.apache.commons.httpclient was needed and not found.
Bugzilla - The module named org.eclipse.core.runtime was needed and not found.
Native Execution - The module named com.jcraft.jsch was needed and not found.
TextMate Lexer - The module named com.google.gson was needed and not found.
LSP Client - The module named com.google.guava was needed and not found.
LSP Client - The module named com.google.gson was needed and not found.
Git Client Library - The module named org.eclipse.jgit was needed and not found.
Git Client Library - The module named com.jcraft.jsch was needed and not found.
Git - The module named org.eclipse.jgit was needed and not found.
10 further modules could not be installed due to the above problems.

It appears just only one, it's skippable and never occurs again. I'm not sure if this is worth to solve but a new collaborators could be a little bit scared but his huge warning :)

[ursjoss]

Could probably be solved in context of ticket #57. could we treat this ticket as duplicate and you paste your findings there?

[RadekCap]

It probably could be solved there but this is something that could discourage contributors so I've marked it as a bug so it'll will have a little higher priority.

[RadekCap]

During the first start after clean compilation, and after modules warning, another dialog appears. This one:

We should probably hide it as well. Or, maybe better, understand how it's working and use it the next time during the new release.

[ursjoss]

:-) This pop-up is the result from fixing the issue of #60. With the fix from PR #61, the messages from the endpoint are downloaded correctly by the MessageChecker and passed on to the MessageParser. The last check-date is cached, but since you have a clean repo (as you describe it after cleaning it), the code considers the check to be the first one. In this case, all valid messages are displayed. Currnelty, there is exactly one message not commented out. It is therefore displayed once (unless you clean again).

See the message here:

tr-pc/modules/au.com.trgtd.tr.task.messages/test/unit/src/au/com/trgtd/tr/task/messages/messages.xml

Line 3 in 4b8f107

<msg date='2014/03/27' type='A'>

It is true, that we should not show that outdated message once we release a version 4.0.0. Until then, I don't mind. To not show the version, @clairelema should remove it from the XML.

[ursjoss]

I found a link to an article stating that those symptoms may be caused by an outdated netbeans cache. Deleting the cached files may resolve it.

After having deleted my netbeans cache (on my linux system ~/.cache/netbeans/16/), I have not had the issue anymore. Let's see if it pops up in the near future.

[RadekCap]

Unfortunately, it's still present on my RHEL system after cache deletion.

[ursjoss]

@RadekCap We might be able to close it now, what do you think?

[RadekCap]

Yes