live edit/chnage a gwt-lib as dependency with gwt-maven-archetypes possible ?

[Frank Taffelt]

My current maven project is based on 3 submodule (shared,server,client) layout from the great gwt-maven-archetypes samples.

Now i want to create an new submodule which is packaged as  "gwt-lib". This module contains some basic omponents which could be reused later by other maven moduls as well.

So for now i added a new dependency to my existing client module:

<dependency>
  <groupId>${project.groupId}</groupId>
  <artifactId>webutil-lib</artifactId>
  <classifier>gwt-lib</classifier>
  <version>${project.version}</version>
</dependency>

what i don't get is live editing of code in my webutil-lib folder without restarting the coderver.

i started the codeserver with -X and found this message in the output:

[DEBUG] Adding sources for de.myproject:dashboard-client:gwt-app:5.4.0-SNAPSHOT

[DEBUG] Ignoring de.myproject:dashboard-shared:jar:5.4.0-SNAPSHOT; neither a gwt-lib or jar:sources.

[DEBUG] Adding sources for de.myproject:dashboard-shared:jar:5.4.0-SNAPSHOT

...

[DEBUG] Ignoring de.myproject:webutil-lib:jar:5.4.0-SNAPSHOT; neither a gwt-lib or jar:sources.
[DEBUG] Ignoring de.myproject:webutil-lib:jar:gwt-lib:5.4.0-SNAPSHOT; neither a gwt-lib or jar:sources.
...

to me it seems that the gwt-lib packaging isn't honoured and therefore not added as a src argument to the codeserver.

should live edit/reload of code in the gwt-lib submodule work for that setup ?

Thanks for any pointers !

[Thomas Broyer]

You have to use <type>gwt-lib</type>, not classifier.

[Frank Taffelt]

ahh that's it. thanks - i was debugging this for 3 hours ....

i was debugging this for the day!

[Frank Taffelt]

[DEBUG] Adding sources for de.myproject:webutil-client:gwt-app:5.4.0-SNAPSHOT
[DEBUG] Ignoring de.myproject:webutil-lib:gwt-lib:5.4.0-SNAPSHOT; no corresponding project reference.

first i thought the issue is solved after changing from classifier to type. but i don't see any changes when i modify parts from my gwt-lib. restarting the codeserver gets them. maybe the last line explains this?

[Thomas Broyer]

"no corresponding project reference" means that the corresponding project is not part of the reactor (multi-module) build.

[Frank Taffelt]

invoke mvn (without any params ) on my parent project says:

[INFO] Reactor Summary:
[INFO]
[INFO] intergator-dashboard-parent ........................ SKIPPED
[INFO] intergator-webutil-lib ............................. SKIPPED
[INFO] intergator-webutil-webapp .......................... SKIPPED
[INFO] intergator-dashboard-shared ........................ SKIPPED
[INFO] intergator-dashboard-client ........................ SKIPPED
[INFO] intergator-dashboard-server ........................ SKIPPED

it lists both projects intergator-webutil-lib and and intergator-webutil-webapp.

is there anything other that i should check ?

[Thomas Broyer]

How do you run SDM on that project? Would you be able to create a small repro case (or maybe this is an open source project?)

[Frank Taffelt]

tried to create a small testproject. but all works as expected. so it must be something of my orginal projectconfig. this is unfortunatly a closed source product.

[Frank Taffelt]

some more pieces. the behaviour only occurs in a enviroment were a unique snapshot repository serves artifacts (our company has an artificatory server). in these case the gwt-lib is installed in my localMavenRepository and the gwt-maven-plugin uses this version prefered over the maven module.

While trying to create a local testproject i never deployed the test artificats. Also a mvn install did work as expected. After deploying my gwt-lib artificat to our local unique repository server, this version was used and code changes where never visible.

A  workarround is to remove the artificat from my local repo and invoke the maven coderserver goal with the -offline option.

So i'm not really sure if it's s an issue with  our local articatory setup or it's an issue with the gwt-maven-plugin under this conditions ?

[Thomas Broyer]

I'd blame Maven here, but given the lack of documentation for almost everything, it might be that I did something wrong in gwt-maven-plugin (but I'd still blame Maven for lack of documentation).