I'm able to generate similar packages without the /target/../ something
included using assembly 2.2-beta-1. I don't use <baseDirectory> tag at all
and inside fileset, I use for example:
            <directory>${basedir}/target/dependency</directory>
            <outputDirectory>lib/</outputDirectory>

That works for me.

Kalle


On 1/3/08, Pankaj Tandon <[EMAIL PROTECTED]> wrote:
>
>
> Just to provide a workaround.. I punted and ended up using the ant zip
> task.
> That works fine.
> If in the meanwhile someone finds out how to solve this using the assembly
> plugin please reply to this thread.
>
> Thanks
> Pankaj
>
>
> Pankaj Tandon wrote:
> >
> > Hi,
> > I was away for 10 days so I couldn't participate in this discussion. But
> > thanks Ryan for persuing the cause!
> >
> > However, I'm not sure how the solution is working for you. It will
> greatly
> > help if you provide details.
> >
> > First, I used the following plugin config:
> >         <plugin>
> >              <groupId>org.apache.maven.plugins</groupId>
> >              <artifactId>maven-assembly-plugin</artifactId>
> >         <executions>
> >           <execution>
> >             <id>assemble</id>
> >             <phase>verify</phase>
> >             <goals>
> >               <goal>attached</goal>
> >             </goals>
> >
> >              <configuration>
> >                 <descriptors>
> >                   <descriptor>src/war-assembly.xml</descriptor>
> >                 </descriptors>
> >               </configuration>
> >             </execution>
> >             </executions>
> >
> >         </plugin>
> >
> >
> > Note that in the above config, there is no explicit mention of the
> > version. But when I looked in  my local repo, I was getting 2.2-beta-1.
> > So, somehow it *was* pulling the latest version.
> > But anyway, I did mention the version like so:
> >         <plugin>
> >              <groupId>org.apache.maven.plugins</groupId>
> >              <artifactId>maven-assembly-plugin</artifactId>
> >              <version>2.2-beta-1</version>
> >         <executions>
> >           <execution>
> >             <id>assemble</id>
> >             <phase>verify</phase>
> >             <goals>
> >               <goal>attached</goal>
> >             </goals>
> >
> >              <configuration>
> >                 <descriptors>
> >                   <descriptor>src/war-assembly.xml</descriptor>
> >                 </descriptors>
> >               </configuration>
> >             </execution>
> >             </executions>
> >
> >         </plugin>
> >
> > And just for completeness, here's my descriptor:
> > <assembly>
> >   <id>portal</id>
> >   <formats>
> >     <format>war</format>
> >   </formats>
> >   <includeBaseDirectory>false</includeBaseDirectory>
> >   <baseDirectory></baseDirectory>
> >   <fileSets>
> >     <fileSet>
> >       <includes>
> >               <include>target/portal/**</include>
> >               <outputDirectory>/</outputDirectory>
> >       </includes>
> >     </fileSet>
> >   </fileSets>
> > </assembly>
> >
> > I *still* get the target/portal in the top level :(
> >
> > What am I doing wrong?
> >
> > To answer your earlier question, as to why I could not use the war
> > plugin.. it is because the war plugin needs the location of the web.xmlin
> > a certain location... herer all I want is the zip up the existing
> > structure after my custom mojo has made mids to it.
> >
> > Any help will be highly appreciated!
> >
> > Thanks
> > Pankaj
> >
> >
> > Ryan Moquin wrote:
> >>
> >> Yeah, that seems to have solved the problem.... I must have been stuck
> >> then
> >> on the 2.1 then.
> >>
> >> On Dec 27, 2007 3:16 PM, Ryan Moquin <[EMAIL PROTECTED]> wrote:
> >>
> >>> So, by using that, it pull whatever the latest released version is?
> >>>
> >>>
> >>> On Dec 27, 2007 3:14 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> >>>
> >>> > On Dec 27, 2007 1:09 PM, Ryan Moquin <[EMAIL PROTECTED]> wrote:
> >>> > > My pom specified the assembly plugin like this:
> >>> > >
> >>> > > <plugin>
> >>> > >         <artifactId>maven-assembly-plugin</artifactId>
> >>> > >         <configuration>
> >>> > >
> >>> > > I'm guessing this means I'm using version 2.2, and more than
> likely
> >>> he
> >>> > is
> >>> > > using the same thing?
> >>> >
> >>> > It means you're using whatever is in your local repository, so
> there's
> >>> > no telling.
> >>> >
> >>> > Try adding this... <version>2.2-beta-1</version>
> >>> >
> >>> > --
> >>> > Wendy
> >>> >
> >>> >
> ---------------------------------------------------------------------
> >>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>> > For additional commands, e-mail: [EMAIL PROTECTED]
> >>> >
> >>> >
> >>>
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/assembly-plugin---topLevel-directory-to-be-supressed-in-war-tp14424240s177p14598572.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to