I won't speak for best practices but typically you would create another
module to do the packaging (similar to some of the EAR examples).

For a simple command-line application, my guess is one pom and one assembly
descriptor will be enough.  For my command-line tool I generate the jar and
then assemble the whole applicaiton like so:

snippet from my assembly descriptor XML file:

<fileSets>
   <fileSet>
     <directory>target</directory>
       <outputDirectory></outputDirectory>
       <includes>
         <include>*.jar</include>
       </includes>
     </fileSet>
     <fileSet>
         <outputDirectory></outputDirectory>
         <directory>dist</directory>
         <includes>
       <include>*</include>
         </includes>
      </fileSet>
 </fileSets>

Basically dist has some extra static files in it, target is where the JAR
gets built, and then the assembly plugin builds everything together.


-aps

On 12/4/06, Eric Wang <[EMAIL PROTECTED]> wrote:

My project is a simple command-line application. I didn't think it
required multiple modules so I never looked into that. Is that the
preferred way to accomplish what I'm describing? Basically, I just
want to include my assembly jar along with a few other files inside a
zip file.


On 12/4/06, Alexander Sack <[EMAIL PROTECTED]> wrote:
> Quick question, why can't you have two sub modules under your POM, one
that
> generates an assembly, the other generating the final output with the
other
> assembly included?  (you get the idea)
>
> -aps
>
> On 12/4/06, Eric Wang <[EMAIL PROTECTED]> wrote:
> >
> > Hi, I'm new to Maven so forgive me if this something really obvious. I
> > looked through the assembly plugin documentation and searched the
> > archives, but couldn't find anything covering my use case.
> >
> > I'm building an assembly using the built-in "jar-with-dependencies"
> > descriptor. That works great. I'd like to include the generated
> > assembly inside another custom assembly. The custom assembly would be
> > a zip file containing my jar (generated with the
> > "jar-with-dependencies" descriptor) along with some other supporting
> > files located in my project root folder.
> >
> > Is something like this possible? I've tried messing around with my
> > custom descriptor, but to no avail. I can generate the zip file, but
> > it doesn't contain my jar, only the supporting files. If I'm going in
> > the wrong direction with this, I'd appreciate if someone could let me
> > know. Thanks.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> "What lies behind us and what lies in front of us is of little concern
to
> what lies within us." -Ralph Waldo Emerson
>
>

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




--
"What lies behind us and what lies in front of us is of little concern to
what lies within us." -Ralph Waldo Emerson

Reply via email to