Menu

#115 Ant node not automatically activated in JB 2005

open
None
7
2004-11-18
2004-11-17
No

I'm using JB 2005 with the current (as of 20041117) top
of tree AntRunner.

When a project with a configured AntRunner node is
loaded, the AntRunner node is not automatically set
Active. I have to explicitly right-click on the Ant
node in the Project view, and "Set Active", before the
antrunner toolbar buttons light up.

Looks like the
AntRunnerBrowserAdapter.browserProjectActivated() is
never being called (I don't see any DEBUG messages from
it when running -verbose). I see the build file parser
being called, and then nothing else.

I'm attaching the output of "jbuilder -verbose".

Discussion

  • Shankar Unni

    Shankar Unni - 2004-11-17

    JBuilder -verbose output

     
  • Shankar Unni

    Shankar Unni - 2004-11-17
    • priority: 5 --> 7
     
  • Shankar Unni

    Shankar Unni - 2004-11-17
    • summary: Ant node not automatically acvitated in JB 2005 --> Ant node not automatically activated in JB 2005
     
  • Shankar Unni

    Shankar Unni - 2004-11-17

    Logged In: YES
    user_id=167432

    Aha. Got it.

    JB2005 apparently doesn't bother to fire the "browserOpened"
    callback when the browser is opened. It directly jumps into
    "browserProjectActivated".

    I've attached a patch that attempts to detect a missing
    browserOpened() callback and corrects for it. I didn't want
    to co-opt "fireEvents" for this, because I sense that that's
    a workaround for a similar botch in earlier releases, but
    I'm not completely sure if the two cases overlap in every
    instance.

     
  • Shankar Unni

    Shankar Unni - 2004-11-17

    Fix for missing browserOpened event in AntRunnerBrowserAdapter.java

     
  • Dirk Schnelle-Walka

    • assigned_to: nobody --> schnelle
     
  • Dirk Schnelle-Walka

    Logged In: YES
    user_id=192116

    Thanks for the patch. It works for me with JB2005. Have to
    check JB4.

    /dirk

     
  • SamK

    SamK - 2004-12-12

    Logged In: YES
    user_id=1176895

    When should the AntRunner with this fix be available