Hi Jeremy Would it be better to have the output of this be the companyweb war file with the sources, this way a user would be able to deploy the sample app + see the sample source code and investigate what's going on on the sample app ?
- Luciano On 8/17/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
On Aug 17, 2006, at 10:01 AM, [EMAIL PROTECTED] wrote: > + <!-- include companyweb source --> > + <fileSet> > + <directory>../../samples/das/companyweb/src</directory> > + <lineEnding>keep</lineEnding> > + <includes> > + <include>**/*.java</include> > + <include>**/*.xml</include> > + </includes> > + <fileMode>644</fileMode> > + </fileSet> Although it works, references outside the project like this are generally problematic. I would suggest an alternative would be to have the companyweb module output a source jar as its artifact rather than the usual binary jar - after all for a sample it is the source that is interesting to users. You could then reference it as a dependency and have that exploded into the distribution. -- Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- ----------------------------------------------------- Luciano Resende SOA Opensource - Apache Tuscany -----------------------------------------------------
