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
The libertyDev task adds some file monitoring but only for the current project (also see #624 ).
However as soon as the current project does not contain all sources but has dependencies to other projects even if they are in the same multiproject build - their source folders are not included making the feature unpredictable or even useless.
For my test case I am using a ear to deploy the application (which has no java sources at all) and all ejbs and web applications are in dependent projects
In this configuration - file system watching is completely useless as is.
The file system monitoring should include all output folders from all project dependencies. The DeployTask already collects the nessesary folders for the LooseEarApplication:
The
libertyDev
task adds some file monitoring but only for the current project (also see #624 ).However as soon as the current project does not contain all sources but has dependencies to other projects even if they are in the same multiproject build - their source folders are not included making the feature unpredictable or even useless.
For my test case I am using a
ear
to deploy the application (which has no java sources at all) and all ejbs and web applications are in dependent projectsIn this configuration - file system watching is completely useless as is.
The file system monitoring should include all output folders from all project dependencies. The
DeployTask
already collects the nessesary folders for theLooseEarApplication
:ci.gradle/src/main/groovy/io/openliberty/tools/gradle/tasks/DeployTask.groovy
Line 389 in 554caad
In case the project is very big (thinking of legacy projects) - a closure to filter the monitored projects may also be a good idea.
The text was updated successfully, but these errors were encountered: