16

I am trying to deploy a maven web application on my local wildfly machine. But I am getting this error:

08:55:02,595 ERROR [io.undertow.request] (default task-55) UT005023: Exception handling request to /reg-server-1.0.0-SNAPSHOT/v1/lineage: org.jboss.resteasy.spi.Unhandled
Exception: java.lang.IllegalArgumentException: Parameter 'directory' is not a directory
Improve this question

7 Answers 7

Reset to default
24

./gradlew assembleDebug --rerun-tasks

This command run in the command prompt will work if you are trying to connect multiple code bases using settings.gradle and get this error.

Improve this answer
Sign up to request clarification or add additional context in comments.

3 Comments

I prefer this answer as you can specify the modules failing on the CLI to build without having to invalidate your entire cache and restarting the IDE
This is certainly the better anwer.
sometimes this execution in terminal may failed because of other reasons. But the directory issue will sow
7

The following worked for me:

  1. Go to Build.gradle(Module: app) and enable make databinding => enable :false.
  2. Rebuild your project.
Improve this answer

2 Comments

deletin .gradle folder and invalidating solved it as no one can disable databinding
Even just deleting ".gradle" folder was enough for me.
4

I had encountered the similar error in Android Studio. I just invalidated the cache and restarted the IDE. I suppose it has some thing to do with stale cache data which do not get updated during build processes. Thus, when you undo some changes which previously resulted in creation and deletion of packages and classes, like DataBinding classes in Android Studio. You are left with directories which do not exist and IDE never updated the caches to reflect the same in following builds. Thus, even if after cleaning and rebuilding, error persist. Hope this helps.

In Android Studio, goto FILE -> Invalidate Cache and Restart.

Improve this answer

5 Comments

This didn't work for me. However, invoking Gradle from the command line with the --rerun-tasks flag did. I was also experiencing a databinding issue.
This didn't work for me as well, i am using data binding
I had to delete the .gradle folder before invalidating as suggested in this answer to similar question
removing .gradle, invalidating the cache and restarting worked for me
remove .gradle fixed it.
4

For me it solved by deleting the .gradle folder and running the build again.

Improve this answer

Comments

1

in build.gradle I changed buildFeatures.dataBinding = true to buildFeatures.dataBinding = false and it's worked for me

Improve this answer

1 Comment

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.
1

For me, deleting the .gradle directory did nothing. I was running my instrumentation tests on an emulator, and I had to wipe the data on it then do a cold boot. Voila! The tests ran.

Improve this answer

Comments

0

It seems that at deploy time, the application is looking for a directory which has not been generated at package time thus the problem. When created in the target/lib then the deployment runs ok.

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.