StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Actually, I have no idea why <code>mvn clean install</code> and <code>mvn clean deploy</code> don't have a consistent result. First, <code>wsimport</code> is bound to the <code>generate-sources</code> phase and is executed in both case much earlier. Second, the <code>deploy</code> phase which occurs right after <code>install</code> doesn't do much more things, as documented:</p> <blockquote> <p>done in an integration or release environment, copies the final package to the remote repository for sharing with other developers and projects.</p> </blockquote> <p>So, really, I don't see how copying an artifact to a repository can impact <code>wsimport</code> or make the build fail on something related to the WSDL. Very, very weird. Maybe run <code>mvn -X clean deploy</code> to see if you can get more information. </p> <p>Anyway, I have a few suggestions about the jaxws-maven-plugin configuration.</p> <p>The first one would be to <strong>not</strong> generate sources in <code>src/main/java</code>. IMO, generated sources should go under the <code>target</code> directory as you want to be able to delete them during a <code>clean</code>. So I'd suggest to use the default value which is <code>${project.build.directory}/jaxws/wsimport/java</code> or something like <code>${project.build.directory}/generated-sources/jaxws</code> instead (this is the standard maven pattern for generated stuff). But this is a side note, this won't solve your issue :)</p> <p>The second suggestion is about the <code><wsdlUrls></code> configuration. Instead of using <code><wsdlUrls></code>, why don't you get the WSDL (as a file) and put it in <code>src/wsdl</code> (or another location in which case you'll have to specify it using the <code><wsdlLocation></code> element). This should help to workaround the timeout issue.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload