[GitHub] [beam] kennknowles opened a new issue, #18762: Load in-process FnHarness instances with a restricted classpath

[GitBox <gi...@apache.org>]

kennknowles opened a new issue, #18762:
URL: https://github.com/apache/beam/issues/18762

   The new classpath can contain the Java harness code and the user's classpath. This simulates the SDK container, and removes the need for users to provide beam-sdks-java-harness as a dependency.
   
   The idea would be that beam-sdks-java-harness would be a jar containing all of its dependencies shaded away similar to what we do for Dataflow. We would embed the beam-sdks-java-harness.jar as a jar inside the direct runner jar so we wouldn't need to fetch it from Maven and also would be able to solve the problem where tests would run from the provided jar.
   
   Imported from Jira [BEAM-4384](https://issues.apache.org/jira/browse/BEAM-4384). Original Jira may contain additional context.
   Reported by: tgroh.


-- 
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.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org