I tied the assembly goal to a phase. Problem resolved. Thanx for looking.
Cheers
Prasad
On 6/26/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
Dan,
I cannot use the dependency-plugin because with it I cannot duplicate
the maven local repo structure in my assembly. The <repository>
element of the assembly's descriptor allows me to do that. However,
only the maven metadata info under META-INF/maven/* in the repo is
extraneous to me.
Cheers
Prasad
On 6/26/06, dan tran <[EMAIL PROTECTED]> wrote:
> maven-dependency-plugin can prepare the "staging area" for you.
>
>
>
> -D
>
>
> On 6/26/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> >
> > I have to use the <repository> element in the maven-assembly-plugin's
> > assembly descriptor. Using this makes the assembly contains maven
> > metadata files under META-INF. (maven/.../*.pom and pom.propperties).
> >
> > One solution Jesse and I talked about was to execute the assembly
> > plugin twice. The first execution would copy the repository to the
> > ${tempRoot}. The second execution would use <fileset><exclude> to copy
> > the dirs over but exclude META-INF/maven.
> >
> > Here are the problems with this approach.
> >
> > 1) If I use assembly plugin in a execution, I get a "descriptor not
> > found error". How can the assembly plugin be used in multiple
> > executions ?
> >
> > 2) The first execution of the assembly copies the repo into
> > ${tempRoot}. But the next execution of the assembly cleans this dir
> > before starting. So the repo dirs are lost. Any ideas on how to get
> > around this ?
> >
> > Thanx in advance
> > Prasad
> >
> > ---------------------------------------------------------------------
> > 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]
