Thanks, Ron. I'll certainly check that out. The real problem is that I
want a text file to be the deliverable artifact from this module. The
QE and Operations staff would prefer not to have to unzip something to
get to it. I currently deliver it as part of our assembly.
Anyway, I'll check out the Resources plugin to see if it'll help me out.
Ron Senykoff wrote:
On Tue, Feb 17, 2009 at 4:59 PM, David C. Hicks <[email protected]> wrote:
I've had a request to deliver release notes for our project as a separate
deliverable when a release is cut. Perhaps I'm going about this the wrong
way, but my first reaction was, "No problem. I'll just pull the notes into
their own module and attach the text file to the deploy step." That was
much easier to think than it has proven to do. I haven't been able to find
a way to simply attach a file that resides in my module.
I do something similar using the resources plugin plus the assembly
plugin. Resources to copy only the files I want bundled into
/target/scripts. Assembly to take everything in scripts, put it in a
scripts folder at the root of the zip which is how we deploy. Even if
you don't use the assembly plugin, resources would be where I would
start, as you can have it pick up a file and copy it to a specific
location. This is done before 'package'.
HTH,
-Ron
---------------------------------------------------------------------
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]
