Closed randymay-insclix closed 3 years ago
To me, that looks like a bug in Maven.
This is actually happening in a multi-maven project if the command is given at the root of the project, using the -pl attribute to use the gwt-app project.
mvn gwt:codeserver -pl <gwt-app-module>
The work-around is to use the command from the same level as the gwt-app module.
It appears that the gwt-maven-plugin can't seem to find the dependent's source jar files when the Maven repository is not the default.
I have run
mvn clean install -Dmaven.repo.local=XXXXX
, and I can see the jars (along with their source jars) in the local repo.When using this command on the gwt-app module:
mvn gwt:devmode -Dmaven.repo.local=XXXXX
, I am seeing the following exception as the source jars are trying to be added: