Tibor17 commented on a change in pull request #240: [SUREFIRE-1658] TCP/IP
Channel for forked Surefire JVM. Extensions API and SPI. Polymorphism for
remote and local process communication.
URL: https://github.com/apache/maven-surefire/pull/240#discussion_r382992315
##########
File path:
surefire-booter/src/main/java/org/apache/maven/surefire/booter/BooterDeserializer.java
##########
@@ -58,6 +60,18 @@ public BooterDeserializer( InputStream inputStream )
properties = SystemPropertyManager.loadProperties( inputStream );
}
+ /**
+ * Describes the current connection channel used by the client in the
forked JVM
+ * in order to connect to the plugin process.
+ *
+ * @return connection string (must not be null)
+ */
+ @Nonnull
+ public String getConnectionString()
+ {
+ return properties.getProperty( FORK_NODE_CONNECTION_STRING );
Review comment:
@eolivelli
The task with JSON is of course related to another issue. It is not
mandatory here. But it can simplify a lot. Please see the list of modules in
Surefire. There is one important for our discussion. It is named
`surefire-shadefire` because it contains all shaded artifacts and it's SNAPSHOT
version cannot be, in principle, used by other modules due to the compiler. We
have to use the release version. Therefore we have to discuss the JSON one
release version ahead of time.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
