On Thu, Jan 6, 2011 at 11:06 AM, Wendy Smoak <wsm...@gmail.com> wrote: > On Thu, Jan 6, 2011 at 11:56 AM, Phillip Hellewell <ssh...@gmail.com> wrote: >>> You might also be interested in NPanday >>> (http://incubator.apache.org/npanday/) which provides several .NET specific >>> plugins if that's the flavour of DLL you are dealing with. >> >> Thanks,but at a quick glance it looks like NPanday is more to help >> with the build process, and to plug-in to the Visual Studio IDE, so it >> doesn't look like it will help me copy DLLs with special logic. > > With NPanday, you can treat DLLs like normal dependencies. NPanday > copies them 'where you need them' automatically.
Thanks. Maybe I should take a closer look at NPanday. But given all the other custom logic I need, I'm pretty sure I'll still need my own plugin. So, can anyone answer my actual question of would it work to take an xml with just a <resources> tag in it, surround it with <project><build> </build></project> or whatever to make it a valid pom, and then use the MavenXpp3Reader to parse that? Or would it be better to copy and modify the code I found in parseResource() function in MavenXpp3Reader? Another idea is to write an .mdo file, based on the one in the assembly plugin, and use the modello plugin to generate the Java I need to parse my xml, but that seems like it might be more work than just copying the parseResource() function from MavenXpp3Reader. Phillip --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
