[ANN] JUnitTestPlugin 0.17 available

Oh, I´m gad to hear that... This was a very annoying bug... :)

• * Recompiled for 915

• Fix creating test class in the wrong location when roots paths are overlapping (c:/src & c:/src-test, c:/src & c:/src/test)

great thanks ;)

an (not so important) NPE, while choosing to create new project and choosing to open it in a new Idea frame:



2003-09-02 17:31:15,894 DEBUG - .junit.JUnitTestPluginActivity - Starting org.intellij.plugins.junit.PsiElementRefactorer for project untitled9.ipr
2003-09-02 17:31:15,894 DEBUG - .junit.JUnitTestPluginActivity - Starting org.intellij.plugins.junit.PsiElementRefactorer for project untitled9.ipr
2003-09-02 17:31:15,894 ERROR - ellij.project.impl.ProjectImpl -
2003-09-02 17:31:15,894 ERROR - ellij.project.impl.ProjectImpl - IntelliJ IDEA (Aurora) Build #915
2003-09-02 17:31:15,894 ERROR - ellij.project.impl.ProjectImpl - JDK: 1.4.2
2003-09-02 17:31:15,894 ERROR - ellij.project.impl.ProjectImpl - VM: Java HotSpot(TM) Client VM
2003-09-02 17:31:15,894 ERROR - ellij.project.impl.ProjectImpl - Vendor: Sun Microsystems Inc.
2003-09-02 17:31:15,894 ERROR - ellij.project.impl.ProjectImpl - OS: Windows 2000
2003-09-02 17:31:15,894 ERROR - ellij.project.impl.ProjectImpl -
java.lang.NullPointerException

at com.intellij.psi.impl.a.a.e.a(e.java:254)

at com.intellij.psi.impl.cb.b(cb.java:134)

at com.intellij.psi.impl.cb.getPsiFile(cb.java:139)

at org.intellij.plugins.junit.UntestedMethodHighlighter.markUntestedMethodsInEditor(UntestedMethodHighlighter.java:82)

at org.intellij.plugins.junit.UntestedMethodHighlighter.mark(UntestedMethodHighlighter.java:147)

at org.intellij.plugins.junit.config.JUnitTestConfiguration.updateUntestedMethodHighlighterState(JUnitTestConfiguration.java:98)

at org.intellij.plugins.junit.config.JUnitTestConfiguration.updateInternalState(JUnitTestConfiguration.java:81)

at org.intellij.plugins.config.Config.configChanged(Config.java:33)

at org.intellij.plugins.config.Config.projectOpened(Config.java:28)

at com.intellij.openapi.project.b.d.c(d.java:125)

at com.intellij.openapi.project.b.d.b(d.java:163)

at com.intellij.openapi.project.b.k.projectOpened(k.java:6)

at com.intellij.openapi.project.b.l.projectOpened(l.java:8)

at com.intellij.openapi.project.b.w.i(w.java:0)

at com.intellij.openapi.project.b.w.a(w.java:139)

at com.intellij.ide.p.p.a(p.java:48)

at com.intellij.ide.q.dl.actionPerformed(dl.java)

at com.intellij.openapi.actionSystem.a.k.actionPerformed(k.java:9)

at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)

at com.intellij.openapi.actionSystem.a.bb.fireActionPerformed(bb.java:6)

at com.intellij.ui.c.a.t.doClick(t.java:161)

at com.intellij.ui.c.a.t.access$300(t.java:7)

at com.intellij.ui.c.a.u.mouseReleased(u.java:5)

at java.awt.Component.processMouseEvent(Unknown Source)

at java.awt.Component.processEvent(Unknown Source)

at java.awt.Container.processEvent(Unknown Source)

at java.awt.Component.dispatchEventImpl(Unknown Source)

at java.awt.Container.dispatchEventImpl(Unknown Source)

at java.awt.Component.dispatchEvent(Unknown Source)

at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)

at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)

at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)

at java.awt.Container.dispatchEventImpl(Unknown Source)

at java.awt.Window.dispatchEventImpl(Unknown Source)

at java.awt.Component.dispatchEvent(Unknown Source)

at java.awt.EventQueue.dispatchEvent(Unknown Source)

at com.intellij.ide.s.a(s.java:61)

at com.intellij.ide.s.dispatchEvent(s.java:110)

at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.run(Unknown Source)

The same exception happens when you open an existing project in a new IDEA
frame.

m.milicevic wrote:

an (not so important) NPE, while choosing to create new project and choosing to open it in a new Idea frame:

Vil.
--
Vilya Harvey
vilya.harvey@digitalsteps.com / digital steps /
(W) +44 (0)1483 469 480
(M) +44 (0)7816 678 457 http://www.digitalsteps.com/

Disclaimer

This e-mail and any attachments may be confidential and/or legally
privileged. If you have received this email and you are not a named
addressee, please inform the sender at Digital Steps Ltd by phone on
+44 (0)1483 469 480 or by reply email and then delete the email from
your system. If you are not a named addressee you must not use,
disclose, distribute, copy, print or rely on this email. Although
Digital Steps Ltd routinely screens for viruses, addressees should
check this email and any attachments for viruses. Digital Steps Ltd
makes no representation or warranty as to the absence of viruses in this
email or any attachments.

Yep, I know about it but I have no idea how to fix it.

I will try to post to the Open API forum and see if JetBrains can help me know why.

Jacques

Do not call any PSI activity in projectOpen(). One just not ready at that
point. Use newly opened StartupManager.registerPostStartupActivity(Runnable
r) in projectOpen() where r does all the stuff which should be executed on
project startup.

--

Best regards,
Maxim Shafirov
JetBrains, Inc / IntelliJ Software
http://www.intellij.com
"Develop with pleasure!"


"Jacques Morel" <jacmorel@yahoo.com> wrote in message
news:15667631.1062521630243.JavaMail.itn@is.intellij.net...

Yep, I know about it but I have no idea how to fix it.

>

I will try to post to the Open API forum and see if JetBrains can help me

know why.
>

Jacques

Is there any plan to "clean up" the component startup process? Right now it is very unintuitive and this new API just smells like a hack to me ;)
Dependencies between components should be managed better IMHO and clear entry points with defined constraints should be defined.
For more detail on my little rant see http://www.intellij.net/tracker/idea/viewSCR?publicId=14726 (BTW who is assigned to this SCR?)

Jacques

I forgot to thank you Maxim for you quick answer.
I will implement it right away.
What are the guarantees I have when using this? Will my PostStartupActivities be run after projectOpened() and before control is returned to the user?

Jacques

I forgot to thank you Maxim for you quick answer.

You're welcome!

Will my PostStartupActivities be run after projectOpened() and before

control is returned to the user?

Yes, exactly. One will be run immedeately after "opening project" progress
window is gone and before user gets control. For instance this is a way all
IDEA's toolwindow are initialized and files being opened at last shutdown
get opened.

--

Best regards,
Maxim Shafirov
JetBrains, Inc / IntelliJ Software
http://www.intellij.com
"Develop with pleasure!"

I am not sure if you know about this one, but, plugin will not work if you have a dot in your file path,
Below is debug info, with same settings for junit plugin, note that regular expression (at least I think it is a regexp) is doing very strange things (actually it is probably doing expected things, considering the fact that "." dot is a special character ): i.e:


devel_Yaf_v1.0
becomes:
devel_Yaf_v1Test.0
Also, it changed path to:D:/snapshots/test/....com/ezgov/blahblah.java

instead of :
D:/snapshots/....com/ezgov/test/blahblah.java


debug info with a dot in the file path, (plugin fails without error ):

2003-09-04 11:17:46,573 DEBUG - [getTestClassPath(
D:/snapshots/devel_Yaf_v1.0/yaf/java/src/com/ezgov/yaf/xmlgenerator/IncludeGenerator.java)=
D:/snapshots/test/devel_Yaf_v1Test.0/yaf/java/src/com/ezgov/yaf/xmlgenerator/IncludeGenerator.java] - at org.intellij.plugins.junit.TestPattern.debug(Logger.java:63)




Debug info without a dot in the path (works as desired):

2003-09-04 11:56:57,096 DEBUG - [getTestClassPath(
D:/snapshots/devel_Yaf_v102/yaf/java/src/com/ezgov/yaf/xmlgenerator/IncludeGenerator.java)=
D:/snapshots/devel_Yaf_v102/yaf/java/src/com/ezgov/yaf/xmlgenerator/test/IncludeGeneratorTest.java] - at org.intellij.plugins.junit.TestPattern.debug(Logger.java:63)