You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -42,9 +51,9 @@ You have to add the following configuration to enable build-time instrumentation
42
51
</plugins>
43
52
</build>
44
53
```
45
-
Note that if you are using continuations with Java 1.8 lambdas then you need to add JavaFlow instrumentation agent at run-time as command-line option, while lambda-related classes are generated by JVM on the fly and there is no other way to instrument them.
54
+
Note that if you are using continuations with Java 1.8 lambdas then you need to add Tascalate JavaFlow instrumentation agent at run-time as command-line option, while lambda-related classes are generated by JVM on the fly and there is no other way to instrument them.
46
55
47
-
Please refer to [pom.xml](https://github.com/vsilaev/java-continuations/blob/master/org.apache.commons.javaflow.examples/pom.xml) in examples project for typical Maven configuration
56
+
Please refer to [pom.xml](https://github.com/vsilaev/tascalate-javaflow/blob/master/net.tascalate.javaflow.examples/pom.xml) in examples project for typical Maven configuration
48
57
49
58
# Ant
50
59
@@ -65,7 +74,7 @@ It's possibe to instrument compiled Java classes as below:
You may take a look at [examples project](https://github.com/vsilaev/java-continuations/tree/master/org.apache.commons.javaflow.examples) for complete configuration template.
80
+
You may take a look at [examples project](https://github.com/vsilaev/tascalate-javaflow/tree/master/net.tascalate.javaflow.examples) for complete configuration template. Please pay attention to <code>ant-lib</code> folder with Ant TaskDef and <code>lib</code> folder with compile-/runtime-dependencies.
0 commit comments