A domain-specific file system to store "materials" (screenshots, HTML, JSON, XML) collected during End-to-End testings using Selenium WebDriver etc. Features to make "diff" and compiling HTML reports are also included. This is written in pure Java8
Apache License 2.0
0
stars
0
forks
source link
Materialstore should go back to be a monolithic project, rather than multi-project #378
During this course of exercise, I suddently realized that the materialstore project v0.12.5 is quite different from the gradle-java-library-plugin-multiproject. The materialstore project is somehow broken.
What is bad in the materialstore project? Let me raise a significant point.
The gradle-java-library-plugin-multiproject told me that every subproject SHOULD have its own jar & pom and pubulish it into the mavenLocal() repository.
On the other hand, the materialstore project publishes only 1 single jar & pom even though it has multiple subprojects. I worked a lot to implement this twist.
It is necessary to implement this? --- 1 single jar&pom out of multiple subprojects?
Possibly not. I misunderstood.
I reviewed the project structure of the materialstore 0.12.5. And thought ---- do I really need it to be multi-project? May be not, it is better to be a monolithic project.
This issue#376 is a difficutl issue. I had to go back to the basics of Gradle. I read an article How to use Gradle api vs. implementation configuration .... This article told me to make the following 2 projects
I wondered how can I make these 2 projects combined to be a single "multi-project". I could make this:
This project worked just fine.
During this course of exercise, I suddently realized that the materialstore project v0.12.5 is quite different from the gradle-java-library-plugin-multiproject. The materialstore project is somehow broken.
What is bad in the materialstore project? Let me raise a significant point.
The gradle-java-library-plugin-multiproject told me that every subproject SHOULD have its own jar & pom and pubulish it into the mavenLocal() repository.
On the other hand, the materialstore project publishes only 1 single jar & pom even though it has multiple subprojects. I worked a lot to implement this twist.
It is necessary to implement this? --- 1 single jar&pom out of multiple subprojects?
Possibly not. I misunderstood.
I reviewed the project structure of the materialstore 0.12.5. And thought ---- do I really need it to be multi-project? May be not, it is better to be a monolithic project.
Ah ----- !