On Sun, 16 Jan 2005 19:09:38 -0500, Phil Steitz <[EMAIL PROTECTED]> wrote:
Its hard-coded in the dist plugin, e.g.:
<ant:copy todir="${maven.dist.bin.assembly.dir}"> <ant:fileset dir="."> <ant:include name="README.txt"/> <ant:include name="LICENSE*"/> </ant:fileset> </ant:copy>
Similar for source distro. To add other stuff, you need to use maven.xml (unless I am missing something).
Wow, that is gross. They should at least do what the jar plugin does, yeah?
The jar plugin can rely on resources specified in the POM. It seems that we need something else to specify files to go in the top level directories in the distros. I made an attempt at that in the patch that I added to MPDIST-20, adding
maven.dist.bin.includes=README*,LICENSE*,NOTICE*
maven.dist.src.includes=README*,LICENSE*,NOTICE*,project.properties,maven.xml,project.xml, build.xml
to plugin.properties for the dist plugin and using these in place of the hard-coded specs in the plugin. I don't know if that is the best way to handle it; but it works for me.
Alex and I (really mostly Alex ;) have been working on adding multiproject support to the dist plugin and I added the change above to Alex's more significant patch to support multiprojects. Might be better to make this a separate issue. I can do that if necessary.
Phil
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
