Works a treat - thanks very much James
-----Original Message----- From: Carlos Sanchez [mailto:[EMAIL PROTECTED] Sent: 21 July 2004 10:22 To: 'Maven Users List' Subject: RE: Referencing non-artifact file from another project Hi, You can add a dependency on the war file and extract it before some goal. e.g. from http://cvs.sourceforge.net/viewcvs.py/oness/common/maven/model/maven.xml?rev =1.2&view=auto <unjar src="${pom.getDependencyPath('oness:oness-common-model')}" dest="${pom.build.sourceDirectory}"> <patternset> <include name="${hibernate.superclasses.dir}/*.java"/> </patternset> </unjar> Regards Carlos Sanchez A Coru�a, Spain Oness Project http://oness.sourceforge.net > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 21, 2004 9:51 AM > To: [EMAIL PROTECTED] > Subject: Referencing non-artifact file from another project > > Can anybody suggest an elegant solution to this problem: > > I've got 2 projects: > - TCW-WebService > A war project > > - TCW-Client > Uses Axis and the wsdl file from the above to generate client stubs > > So the question is how should the latter reference that wsdl > file. I originally used a clearcase symlink, but I've had to > abandon that as the wsdl file is now actually generated from > a couple of constituent files, so the final wsdl isn't > actually in ccase any more, hence can't be symlinked > > Now as a "get it working" step I can just put a step in the > client project to do a copy on > ../TCW-WebService/src/tcw.wsdl, but it feels "wrong". Is > there a better way? > > thanks > > James > > > -------------------------------------------------------------- > ---------- > For more information about Barclays Capital, please visit our > web site at http://www.barcap.com. > > > Internet communications are not secure and therefore the > Barclays Group does not accept legal responsibility for the > contents of this message. Although the Barclays Group > operates anti-virus programmes, it does not accept > responsibility for any damage whatsoever that is caused by > viruses being passed. Any views or opinions presented are > solely those of the author and do not necessarily represent > those of the Barclays Group. Replies to this email may be > monitored by the Barclays Group for operational or business reasons. > > -------------------------------------------------------------- > ---------- > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
