At work we started out with Maven and quickly discovered you couldn't do dependencies to other projects unless they shared a parent POM. Things quickly started becoming unwieldy. Discovered "loosely coupled" projects with Gradle. We haven't looked back.
On Wed, Mar 10, 2021 at 10:25 AM Thomas Broyer <t.broyer@gmail.com> wrote:
--On Wednesday, March 10, 2021 at 4:13:03 PM UTC+1 pavel....@gmail.com wrote:We had the same problem with maven but at the end, maven's multi-module project and profiles helped tosolvehack around it.There, fixed it for you 😉Also see https://www.cloudbees.com/blog/maven-profiles-and-maven-way and https://blog.soebes.de/blog/2013/11/09/why-is-it-bad-to-activate-slash-deactive-modules-by-profiles-in-maven/ among others, by prominent Maven PMC members.(and yet, gwt-maven-archetypes use a "dev" profile 🤷, but it's know to be kind of hackish in places due to Maven and jetty-maven-plugin's limitations)
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/cd2b1c5a-f10a-4200-85d0-e9ed96279585n%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CAFHWztxdgKt%3DC%2BzHM%3DcOuaaKvs4%3D0fzLShK_u-fWSUg8aDB1hg%40mail.gmail.com.
No comments:
Post a Comment