Mrudhulraj commented on PR #6016:
URL: https://github.com/apache/texera/pull/6016#issuecomment-4985699494
@carloea2 DatasetResourceSpec (in file-service) needs access to the
DashboardResource class (part of the amber project).
Hence, I am unable to write the test cases without dragging in all of
amber's heavy runtime classpath (Dropwizard conflicts, old Jetty/Jackson
versions, etc.).
To bypass this cleanly and pull only the dashboard files we need directly
into the file-service test scope, we can share the source files via
unmanagedSources in the root build.sbt.
Shall I add the following to lazy val FileService in the root build.sbt?
```
Test / unmanagedSources ++= Seq(
(ThisBuild / baseDirectory).value / "amber" / "src" / "main" / "scala" /
"org" / "apache" / "texera" / "web" / "resource" / "dashboard" /
"DashboardResource.scala",
)
```
This will compile these files strictly within the test phase of file-service
without impacting any production artifacts or causing dependency conflicts. I
will be able to add test cases for DatasetSearchQueryBuilder post this.
cc: @Yicong-Huang appreciate your insights too!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
