[
https://issues.apache.org/jira/browse/BEAM-3995?focusedWorklogId=87810&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-87810
]
ASF GitHub Bot logged work on BEAM-3995:
----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Apr/18 23:14
Start Date: 04/Apr/18 23:14
Worklog Time Spent: 10m
Work Description: kennknowles commented on issue #5026: [BEAM-3995] Build
self-contained Nexmark jar
URL: https://github.com/apache/beam/pull/5026#issuecomment-378774094
It is a big hammer; too big. We'll actually need to have a way to get the
different runners on the classpath without bundling. But Gradle has nothing
that I would care to use equivalent to `mvn exec:java`. Still poking around but
the solutions I've found are not reasonable.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 87810)
Time Spent: 20m (was: 10m)
> Launch Nexmark suites from gradle and update web page docs
> ----------------------------------------------------------
>
> Key: BEAM-3995
> URL: https://issues.apache.org/jira/browse/BEAM-3995
> Project: Beam
> Issue Type: Sub-task
> Components: examples-nexmark, website
> Reporter: Kenneth Knowles
> Assignee: Kenneth Knowles
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently our instructions for running Nexmark benchmarks on various runners
> is pretty tightly tied to Maven. We need a good story for running them with
> gradle (or just building an executable with gradle and running that
> standalone).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
