I suspect that this is a consequence of the reordering of the
initialization sequence.

I'll do some testing to see if my theory is correct.

Tom

On Dec 13, 2007 3:59 PM, Linus Tolke <[EMAIL PROTECTED]> wrote:
> There is a problem with the JUnit test cases in the release. The problem is
> with the guitests that are not normally run because of the need of the
> screen.
>
> Here is the backtrace:
>
>  testProjectWithContents Error N/A
>
> java.lang.NullPointerException
> at java.awt.Container.addImpl(Container.java:1031)
> at java.awt.Container.add(Container.java:395)
> at org.tigris.swidgets.MultipleSplitPane.add(Unknown Source)
>  at org.tigris.swidgets.BorderSplitPane.add(Unknown Source)
> at org.argouml.ui.ProjectBrowser.addPanel(ProjectBrowser.java:571)
> at org.argouml.ui.ProjectBrowser.assemblePanels(ProjectBrowser.java:424)
> at org.argouml.ui.ProjectBrowser .(ProjectBrowser.java:276)
> at org.argouml.ui.ProjectBrowser.(ProjectBrowser.java:244)
> at org.argouml.ui.ProjectBrowser.getInstance(ProjectBrowser.java:348)
> at org.argouml.uml.ui.ActionOpenProject.doCommand(ActionOpenProject.java
> :170)
> at org.argouml.application.Main.performCommands(Main.java:634)
> at org.argouml.util.CheckMain.doCommand(CheckMain.java:52)
> at
> org.argouml.ui.cmd.GUITestActionGotoDiagram.testProjectWithContents(GUITestActionGotoDiagram.java
> :74)
>
>
> I don't really understand this problem. I will not proceed tonight then. I
> attempt to dig into the problem tomorrow night. If anyone else understand
> the problem please fix it!
>
>         /Linus

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to