Please address the list directly. But I thought I already answer.
Hower,you assembly descriptor looks troublesome since both input and ouput
point to the same directory
-D
On 10/1/06, Morgovsky, Alexander (US - Glen Mills) <[EMAIL PROTECTED]>
wrote:
Hi Dan. If you have a chance, may you please provide further guidance
for me for this issue? Thanks so much.
------------------------------
*From:* Morgovsky, Alexander (US - Glen Mills)
*Sent:* Friday, September 29, 2006 11:28 AM
*To:* 'dan tran'
*Subject:* RE: Packaging dependencies in expanded format
Hey. Thanks.
<assembly>
<formats>
<format>jar</format>
</formats>
<includeBaseDirectory>false</includeBaseDirectory>
<fileSets>
<fileSet>
<directory>target</directory>
<outputDirectory>target</outputDirectory>
</fileSet>
</fileSets>
</assembly>
------------------------------
*From:* dan tran [mailto:[EMAIL PROTECTED]
*Sent:* Friday, September 29, 2006 11:26 AM
*To:* Morgovsky, Alexander (US - Glen Mills)
*Subject:* Re: Packaging dependencies in expanded format
show your assembly descriptor
-D
On 9/29/06, Morgovsky, Alexander (US - Glen Mills) <
[EMAIL PROTECTED]> wrote:
>
> Thanks Dan. I got it work, but there is one more issue left. I want
> to use the assembly plugin to generate a .jar file of all the contents in
> /target. When I do this, the "target" folder is part of each path inside in
> the resulting .jar. I tried using
> <includeBaseDirectory>false</includeBaseDirectory>, but that did not help.
> Is there a way to exclude the parent directory "target" from the resulting
> paths inside the binary? Thanks a lot for the previous help as well.
>
>
> This message (including any attachments) contains confidential
> information intended for a specific individual and purpose, and is protected
> by law. If you are not the intended recipient, you should delete this
> message.
>
> Any disclosure, copying, or distribution of this message, or the taking
> of any action based on it, is strictly prohibited. [v.E.1]
>
