No Main-Class attribute in manifest about tcpmon

[GoogleCodeExporter]

Could you add the Main-Class configuration in the MANIFEST.MF ?
Otherwise, I could only run it as a java application not a jar file.

Original comment by [email protected] on 21 Sep 2011 at 2:50

[GoogleCodeExporter]

In the meantime, this works for me:
java -cp tcpmon-1.1.jar com.codegoogle.tcpmon.MainWindow

Original comment by [email protected] on 6 Oct 2011 at 10:13

[GoogleCodeExporter]

In the meantime you can rebuild the jar with the appropriate manifest header by 
1) unzipping it somewhere.  2) Create a manifest.mf file in the same location 
containing "Main-Class: com.codegoogle.tcpmon.MainWindow" followed by a 
newline.  3) Run from the terminal at that location: "jar cfm 
a_new_jar_name.jar manifest.mf com/codegoogle/tcpmon/*.class".  Of course 
switch the path separators to match whatever your OS expects.

Original comment by [email protected] on 13 Oct 2011 at 6:51

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

To improve upon Ian, simply

 echo Main-Class: com.codegoogle.tcpmon.MainWindow > abc 
 jar ufmv tcpmon-1.1.jar abc
 rm abc

Also, a removal of the signature file is necessary:

  zip -d tcpmon-1.1.jar META-INF/TCPMON.SF

Original comment by k.tinnefeld on 18 Apr 2012 at 4:09

[GoogleCodeExporter]

Verified k.tinnef's fix above resolves the issue.

Perhaps the home page should be updated? It currently still reads, "Download 
tcpmon and simply double-click on the downloaded executable jar file to launch 
tcpmon." Perhaps it should be updated to read, "Download tcpmon, unzip it, open 
the META-INF/MANIFEST.MF file in a text editor, append the Main-Class 
attribute, save the file, delete the META-INF/TCPMON.SF file, recompress the 
JAR file, and double-click on the newly created executable jar file." Having 
these instructions available would certainly help new TCPMon users who aren't 
savvy enough to locate this issue.

Original comment by [email protected] on 28 Jun 2012 at 2:51

[GoogleCodeExporter]

-bash-3.2$ ./java -cp tcpmon-1.1.jar com.codegoogle.tcpmon.MainWindow
Exception in thread "AWT-EventQueue-0" java.awt.HeadlessException:
No X11 DISPLAY variable was set, but this program performed an operation which 
r                                 equires it.
        at java.awt.GraphicsEnvironment.checkHeadless(Unknown Source)
        at java.awt.Window.<init>(Unknown Source)
        at java.awt.Frame.<init>(Unknown Source)
        at java.awt.Frame.<init>(Unknown Source)
        at javax.swing.JFrame.<init>(Unknown Source)
        at com.codegoogle.tcpmon.MainWindow.<init>(MainWindow.java:29)
        at com.codegoogle.tcpmon.MainWindow$2.run(MainWindow.java:232)
        at java.awt.event.InvocationEvent.dispatch(Unknown Source)
        at java.awt.EventQueue.dispatchEvent(Unknown Source)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForFilter(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)

Original comment by [email protected] on 27 Feb 2013 at 11:28

[GoogleCodeExporter]

> No X11 DISPLAY variable was set

This will happen to any X program in your environment. See e.g. 
http://www.linuxforums.org/forum/newbie/143095-no-x11-display-variable-what-does
-mean.html

Original comment by k.tinnefeld on 28 Feb 2013 at 6:53