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
@@ -39,9 +40,9 @@ The general flow for making a change to the library is:
39
40
40
41
The following instructions explain how to test durabletask-java changes in a Durable Functions Java app.
41
42
42
-
1. After making changes in durabletask-java, you will need to increment the version number in build.gradle. For example, if I make a change in the azurefunctions directory, then I would update the version in `azurefunctions/build.gradle`.
43
+
1. After making changes in durabletask-java, you will need to increment the version number in build.gradle. For example, if you make a change in the azurefunctions directory, then you would update the version in `azurefunctions/build.gradle`.
43
44
2. In the durabletask-java repo, from the root of the project, run `gradle clean build`. This will create the .jar files with the updated version that you specified.
44
-
3. To get the .jar file that was created, go to the `build/libs` directory. For example, if you made a change in azurefunctions, then go to `distributed-tracing\durabletask-java\azurefunctions\build\libs`. If you made a change to client, then go to `distributed-tracing\durabletask-java\client\build\`. Add the .jar files that you are testing to a local directory.
45
+
3. To get the .jar file that was created, go to the `build/libs` directory. For example, if you made a change in azurefunctions, then go to `durabletask-java/azurefunctions/build/libs`. If you made a change to client, then go to `durabletask-java/client/build/libs`. Add the .jar files that you are testing to a local directory.
45
46
4.[Create a Durable Functions Java app](https://learn.microsoft.com/en-us/azure/azure-functions/durable/quickstart-java?tabs=bash&pivots=create-option-vscode) if you haven't done so already.
46
47
5. In the Durable Functions Java app, run the following command to install the local .jar files that were created in step 2: `mvn install:install-file -Dfile="<path to .jar file that was created in step 2>" -DgroupId="com.microsoft" -DartifactId="<name of .jar file>" -Dversion="<version>" -Dpackaging="jar" -DlocalRepositoryPath="<path to Durable Functions Java app>"`.
## Debugging .NET packages from a Durable Functions Java app
60
61
61
-
If you want to debug into the Durable Task or any of the .NET bits, follow instructions below:
62
+
If you want to debug into the Durable Task or any of the .NET bits, follow the instructions below:
62
63
63
64
1. If you would like to debug a custom local WebJobs extension package then create the custom package, place it in a local directory, and then run `func extensions install --package Microsoft.Azure.WebJobs.Extensions.DurableTask --version <VERSION>`. If you update the version while debugging and the new version doesn't get picked up, then try running `func extensions install` to get the new changes.
64
65
3. Make sure the Durable Functions Java debugging is setup already and the debugger has started the `func` process.
65
-
4. In the VSCode editor for DurableTask, click Debug -> .NET Core Attach Process, search for `func host start` process and attach to it. If you are using Visual Studio, click Debug -> Attach to Process, search for the `func` process and attach to it.
66
+
4. In the VSCode editor for DurableTask, click Debug -> .NET Core Attach Process, search for `func host start` process and attach to it.
66
67
5. Add a breakpoint in both editors and continue debugging.
0 commit comments