It is actually a problem that affects many Maven plugins. The usual
workaround is to use ${basedir} to build the absolute path.Andreas On Wed, Mar 16, 2011 at 22:05, stlecho <[email protected]> wrote: > > I'm really blocked by this issue, so I would be more than glad if someone > could help me with this issue ;o) > > > stlecho wrote: >> >> I'm using a multi-module project. When building a sub-module, the >> wsdl2code plugin finds the WSDL for which I'm generating Java classes. >> When building the complete module, the WSDL is not found: >> "java.io.FileNotFoundException: This file was not found: >> file:/D:/MULTI_MODULE_PROJECT/src/main/resources/SITRANWebService.wsdl". >> >> I've tried to include ${project.artifactId} or >> ${parent.artifactId}/${project.artifactId} in the location of the WSDL >> file, but none of them solved the problem. >> >> Configuration I'm using: >> <configuration> >> ... >> <wsdlFile>src/main/resources/SITRANWebService.wsdl</wsdlFile> >> ... >> </configuration> >> >> What is the best way to define the location of the WSDL file when working >> with a multi-module project ? >> > > -- > View this message in context: > http://old.nabble.com/wsdl2code-and-multi-module-project-tp31097649p31167598.html > Sent from the Axis - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
