"Can't the plugin just detect the OS and figure what dependencies it needs to download on it's own? "
It's a fair question, but a few things are going on here, first GWT is unlike any typical Java component that any other Maven plugin deals with. it requires not only java, but also NATIVE libs, to be present at certain locations (the stuff for the shell). Those libraries are platform dependent. It is arguable that GWT itself should be packaged a bit differently (separating out the platform differences more cleanly, not repeating anything in the dev jar, etc), but suffice to say it's not as trivial as "compile." There are a few other GWT and Maven plugins if you just want something that does compile, and those are more straightforward, yes - but they can't run tests, or run the shell, or generate your i18n content, or . . . etc. Also, at one point we did have the plugin just figuring out what it needed and not requiring GWT deps in the project POM, etc. But then OTHER plugins and build phases of Maven didn't have access to the dependencies, and they ended up being needed anyway. For example you would still have to add dependencies for Surefire or war, etc. Explicit is better, and it's the Maven way. Unless you have something that is a dependency ONLY needed for your plugin (PMD or Checkstyle), you really have to declare them in the project POM (rather than have the plugin include it for itself only). Also, you don't need the profiles at all if you don't want them, that's just a tip (I think a good one, but if you just run on one platform and don't care, don't use them). The classifiers and such come from the way GWT is built and the way GWT is packaged in the maven central repo - have nothing to do with GWT-Maven. On Sep 10, 12:41 pm, jimbo801 <[EMAIL PROTECTED]> wrote: > I have to assume this question may have been asked before... > > What I don't understand is why so much configuration with profiles and > classifiers? > > Can't the plugin just detect the OS and figure what dependencies it > needs to download on it's own? > > I just think about the maven-compiler-plugin, you specify the target > version, and that's it. > > Is this a totally stupid question? > > -James --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
