Skip to content

Commit 37818a0

Browse files
committed
2 parents a1af9a8 + 6830f34 commit 37818a0

File tree

1 file changed

+15
-6
lines changed

1 file changed

+15
-6
lines changed

README.md

Lines changed: 15 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,15 @@ The project is based on the completely reworked Apache Jakarta-Commons JavaFlow
1616

1717
You have to add the following configuration to enable build-time instrumentation of classes during Maven build:
1818
```xml
19+
<dependencies>
20+
<dependency>
21+
<groupId>net.tascalate.javaflow</groupId>
22+
<artifactId>net.tascalate.javaflow.api</artifactId>
23+
<version>2.0-SNAPSHOT</version>
24+
</dependency>
25+
...
26+
</dependencies>
27+
1928
<build>
2029
<plugins>
2130
<plugin>
@@ -27,8 +36,8 @@ You have to add the following configuration to enable build-time instrumentation
2736
</configuration>
2837
</plugin>
2938
<plugin>
30-
<groupId>org.apache.commons</groupId>
31-
<artifactId>org.apache.commons.javaflow.tools.maven</artifactId>
39+
<groupId>net.tascalate.javaflow</groupId>
40+
<artifactId>net.tascalate.javaflow.tools.maven</artifactId>
3241
<version>2.0-SNAPSHOT</version>
3342
<executions>
3443
<execution>
@@ -42,9 +51,9 @@ You have to add the following configuration to enable build-time instrumentation
4251
</plugins>
4352
</build>
4453
```
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.
4655

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
4857

4958
# Ant
5059

@@ -65,7 +74,7 @@ It's possibe to instrument compiled Java classes as below:
6574
<taskdef name="javaflow" classname="org.apache.commons.javaflow.ant.AntRewriteTask"
6675
classpathref="ant-lib-classpath"/>
6776
<echo message="JavaFlow instrumentation of compiled classes in ${jar.dir}/${ant.project.name}.jar" />
68-
<javaflow srcdir="${jar.dir}" destdir="${i-jar.dir}"/>
77+
<javaflow srcdir="${jar.dir}" destdir="${i-jar.dir}" classpathref="classpath"/>
6978
</target>
7079
```
71-
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

Comments
 (0)