[ 
https://issues.apache.org/jira/browse/CASSANDRA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675555#comment-13675555
 ] 

Benjamin Coverston commented on CASSANDRA-5611:
-----------------------------------------------

Nothing here:

{code}
Ben-Coverstons-MacBook-Pro:riptano-cassandra bcoverston$ java -version
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06-451-11M4406)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01-451, mixed mode)
{code}

Also not getting anything after upgrading:

{code}
Ben-Coverstons-MacBook-Pro:riptano-cassandra bcoverston$ java -version
java version "1.7.0_21"
Java(TM) SE Runtime Environment (build 1.7.0_21-b12)
Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode)
{code}
                
> OS X puts an icon for Cassandra in the dock
> -------------------------------------------
>
>                 Key: CASSANDRA-5611
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5611
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 1.1.12, 1.2.5, 2.0
>         Environment: OS X, JDK 1.7
>            Reporter: Aleksey Yeschenko
>            Priority: Trivial
>
> "Even when a Java program doesn't display any windows or other visible 
> elements, if it accesses the AWT subsystem in some way (e.g., to do image 
> processing internally), OS X will still put an icon for the Java program in 
> the dock as if it were a GUI-based app. (When the program quits, the dock 
> icon goes away as usual.)"
> (more details at 
> http://hints.macworld.com/article.php?story=20071208235352641)
> Can't remember when it started happening, but it wasn't always the case for 
> Cassandra. Now launching Cassandra puts an icon in the dock, and, worse, 
> running ant test puts an icon in the dock for each test, stealing focus, too. 
> This is extremely annoying.
> I ninja-d a workaround (-Djava.awt.headless=true) for ant test in 
> 99824496aa359fcbe5e71f4e54f2738f09524a87, but we should try and find the real 
> source of this (my guess is that some dependency of ours is to blame).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to