Yeah, I bound this to the verify stage properly, but the outstanding
question is how can the directory structure get passed from the parent
pom to the child?

When the parent pom calls the child one, everything is supposed to be
based on the child's pom location.  Instead, the parent pom is looking
for a target directory at the same level as the child (I'm using the
assembly plugin).  Of course this fails.  

Is there a way to do this? 

-----Original Message-----
From: Edwin Punzalan [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 05, 2006 9:25 PM
To: Maven Users List
Subject: Re: building assemblies from the top level project directory -
binding to lifecycle stages...


Shouldn't there be a <goals><goal/></goals> inside the <executions> ?


EJ Ciramella wrote:
> Shouldn't this work?
>
>     <plugins>
>       <plugin>
>        <artifactId>maven-assembly-plugin</artifactId>
>         <configuration>
>           <descriptor>src/main/assembly/dep.xml</descriptor>
>         </configuration>
>        <executions>
>         <execution>
>           <phase>package</phase>
>         </execution>
>        </executions>
>       </plugin> 
>
> ....
>
>
> It doesn't, but is there a way to do something like this?  Packaging
> this particular module should mean build a tarball in addition to the
> jar with all the classes.
>
> -----Original Message-----
> From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
> Sent: Monday, June 05, 2006 11:56 AM
> To: Maven Users List
> Subject: building assemblies from the top level project directory
>
> If I have a structure like this:
>  
> C:\work\projectname
>  
> And have three modules:
>  
> C:\work\projectname\utils
> C:\work\projectname\someproj
> C:\work\projectname\application
>  
> The only item that has an assembly is the actual application.  Is
there
> some way to build that assembly from the projectname directory, or do
I
> have to run assembly:assembly from the application directory every
time?
>
> ---------------------------------------------------------------------
> 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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to