Hi,

I am using a custom assembly to generate Apache UIMA
PEAR files. There is a top-level POM with many child
POMs. Each sub-project has a custom assembly that 
looks like this:

<assembly>
  <id>distribution</id>
  <formats>
    <format>zip</format>
  </formats>
  <fileSets>
    <fileSet>
      <directory>bin</directory>
      <outputDirectory>/bin</outputDirectory>
    </fileSet>
    <fileSet>
      <directory>desc</directory>
      <outputDirectory>/desc</outputDirectory>
    </fileSet>
    <fileSet>
      <directory>metadata</directory>
      <outputDirectory>/metadata</outputDirectory>
    </fileSet>
  </fileSets>
  <dependencySets>
    <dependencySet>
      <outputDirectory>lib</outputDirectory>
      <includes>
        <include>mygroup:support</include>
        <include>mygroup:client</include>
        <include>mygroup:XBeans</include>
        <include>axis2:axis2</include>
        <include>xmlbeans:xmlbeans</include>
      </includes>
    </dependencySet>
  </dependencySets>
</assembly>

I have a couple of questions:

1. mygroup:support is a sibling of this project under
the same top-level POM file. It doesn't have an
assembly, but rather I simply execute the
"install:install-file" so that it gets installed into
the local repository. However, the mygroup:client and
mygroup:XBeans are deployed in a company-wide Maven
repository. Whenever I assemble this project, it
includes the mygroup-support-1.0-SNAPSHOT.jar (which
is correct), but it includes
mygroup-client-1.0-20070326.222023-1.jar and 
mygroup-XBeans-1.0-20070326.222010-1.jar (which is not
what I want). Ultimately I want just the
1.0-SNAPSHOT.jar of all three - how/where do I achieve
this?

2. I have specified assembly descriptors (like the one
listed above) for all of my sub-projects. When I
execute the assembly:assembly target from the
individual sub-project's directory, it works great.
However, since I want this to be automated, my hope
was that I could execute the assembly:assembly at the
top-level POM and have that execute all of its child
POM's assembly:assembly targets. Of course, this does
not happen. Unfortunately, as per the above, my
individual sub-projects' assemblies are custom
assemblies . If I execute an assembly at the top level
POM, it captures the artifact JARs, not the assembled
binaries. Is it possible to have the top-level
assembly include custom assemblies of its children?

3. Is there a simple way to name the file that an
assembly generates *including* the extension? As per
the above, each of my child projects wants to have a
XXXX.pear file (really just a ZIP file, but it's
Apache UIMA's file naming scheme). No matter what I
tweak, set, and specify, it always tacks on "*.zip".
Is it possible to have total control over the entirety
of the name?

Thanks!
Kirk

--------------------------------------------
Kirk True
Principal Engineer
Mustard Grain

[EMAIL PROTECTED]
(831) 588-7959
http://www.mustardgrain.com

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

Reply via email to