JarCasting
JarCasting JarCasting

swingexplorer-agent

An agent which instruments Swing application to gather necessary information to Swing Explorer

License

License
GroupId

GroupId

org.swingexplorer
ArtifactId

ArtifactId

swingexplorer-agent
Last Version

Last Version

1.7.0
Release Date

Release Date
Type

Type

jar
Description

Description

swingexplorer-agent
An agent which instruments Swing application to gather necessary information to Swing Explorer

Download swingexplorer-agent

Filename Size
swingexplorer-agent-1.7.0.pom
swingexplorer-agent-1.7.0.jar 9 KB
swingexplorer-agent-1.7.0-sources.jar 8 KB
swingexplorer-agent-1.7.0-javadoc.jar 37 KB
Browse

How to add to project

<!-- https://jarcasting.com/artifacts/org.swingexplorer/swingexplorer-agent/ -->
<dependency>
    <groupId>org.swingexplorer</groupId>
    <artifactId>swingexplorer-agent</artifactId>
    <version>1.7.0</version>
</dependency>
// https://jarcasting.com/artifacts/org.swingexplorer/swingexplorer-agent/
implementation 'org.swingexplorer:swingexplorer-agent:1.7.0'
// https://jarcasting.com/artifacts/org.swingexplorer/swingexplorer-agent/
implementation ("org.swingexplorer:swingexplorer-agent:1.7.0")
'org.swingexplorer:swingexplorer-agent:jar:1.7.0'
<dependency org="org.swingexplorer" name="swingexplorer-agent" rev="1.7.0">
  <artifact name="swingexplorer-agent" type="jar" />
</dependency>
@Grapes(
@Grab(group='org.swingexplorer', module='swingexplorer-agent', version='1.7.0')
)
libraryDependencies += "org.swingexplorer" % "swingexplorer-agent" % "1.7.0"
[org.swingexplorer/swingexplorer-agent "1.7.0"]

Dependencies

compile (1)

Group / Artifact Type Version
javassist : javassist jar 3.12.1.GA

Project Modules

There are no modules declared in this project.

Swing Explorer

A GUI tool for inspecting Java Swing GUIs. It works in a similar way as developer plugins for HTML browsers but for Java Swing toolkit. The tool is useful for debugging, testing, inspecting and fine tunning of Swing Applications.

With Swing Explorer you can:

  • Visually browse through application component hierarchy
  • Monitor AWT/Swing events
  • Debug 2D graphics
  • Easily find places in the source code responsible for creation of certain peaces of UI.
  • Monitor threading rule violations

Below is shown how basic Swing application is inspected by Swing Explorer. More detailed information about Swing Explorer can be found in the User Manual (TBD).
Swing Explorer

Running Swing Explorer with your application

Using standalone mode

Use the swexpl command, found in bin/, to launch your application.

swexpl -cp <classpath> <mainclass>

Where <classpath> is your program's classpath, and <mainclass> is the fully-qualified name of your program's main class.

You can also manually pull in the Swing Explorer libraries and use org.swingexplorer.Launcher.main() to run your program with Swing Explorer active.

See the User Guide for more details.

Using IDE plug-in

TBD

Building from source

Using maven it is necessary to run mvn clean package command from the root folder of cloned project's repository. To test whether the build worked, you can cd in to swingexplorer-core and run dev-tools/launch_sample.sh to run the sample application.

Versions

Version
1.7.0