A couple options: 1. This resource should live in its own artifact since it is a shared resource. So move it to its own project, and use maven-dependency-plugin:unpack mojo to make it available where it is needed (in both projects) at build time.
2. Copy this resource to a public webserver somewhere and use maven-remote-resources-plugin to pull it into both projects at build time. 3. Leave the resource where it currently lives (in project1's jar), and use dependency:unpack to copy it somewhere in project2 when it is needed at build time. Wayne On 8/20/07, DCVer <[EMAIL PROTECTED]> wrote: > > Hi all, > > I have a question: One of my projects needs a wsdl file resource from > another project, but doesn't need anything else from this project. Is there > a method to create some dependency (jar?) containing only that resource? Now > I specify needed resources by pointing relative path to resource directory > of the other project. > -- > View this message in context: > http://www.nabble.com/Making-resources-separate-dependencies-tf4299111s177.html#a12236643 > Sent from the Maven - Users 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]
