All Classes and Interfaces

Class
Description
A BuildConnection allow communication between a an IDE and a maven build to observe the state of the build and act on certain events.
BuildContext interface.
Provides access to the configuration provided by the server
Filesystem based non-incremental build context implementation which behaves as if all files were just created.
Default implementation of the Messages interface.
The default implementation simply log to debug and check for thread interruption
Listen to all maven events and forward them to the endpoint
Message send to init the inital communication with the endpoints
A message exchanged between two endpoints, usually an IDE and a maven build
Represents a message with all its parameters.
Builder class for constructing messages.
Messages interface.
Enum representing the type/severity of a message.
Mesaage generated when a mojo is executed
create the event type
The Progress allows a mojo to report its current state and check if the user has requested cancellation.
Send to inform about project changes
Describe the type of the event
Message send to inform about reactor project in the build and their effective model
Holds basic project info
A message that indicates a path should be refreshed (e.g.
Event that is received / send when a session starts/end
Default implementation using the system property plexus.build.ipc.port to communicate with an endpoint to exchange messages
Represents a server connection that must be created to communicate with the maven process using the TcpBuildConnection