On 12/29/2010 04:17 PM, Jon Paynter wrote:
well the build didnt fail. However it seems none of your modules were
included in the assembly. Ive done a little bit with assemblies, I was
never able to get the<include> tags to work.
What are you trying to accomplish here?
Basically, I'm trying to retrofit into an environment where the service
management (deployers and such) know a fair bit about unix and much less
about java. It's nothing for them to unzip a tarball and restart an
application. This runs as a standalone java app, with some
configuration files outside of jars for on the fly tweaking. As its
name implies it manages batch processes. Some of these modules are used
in other applications, a set of Hibernate classes for manipulating a
database, some web service clients for outside web services, etc. Many
of these same modules get deployed in a Web App that runs from a WAR
file in Tomcat, but that's not this case for this application.
it looks like you just want the
artifacts from your 6 modules added into a zip file. Also, what is the
structure of your project?
So the basic structure is that each module is its own project, with its
own POM and gets deployed into the repository. I thought it would be
simple to just aggregate those into a zip along with their third party
dependencies but nothing is as simple with Maven as you hope it will be.
Well, not nothing, many things are simple, but the assemblies are a bear.
Have you tried running with useAllReactorProjects set to false?
No, as I said in my earlier thread, I was following the model that is
described at
http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html
where they introduce useAllReactorProjects which is supposed to be the
whole key to making this work, the greatest thing since sliced bread:
> Finally, notice the new useAllReactorProjects flag. This enables
access to all projects in the current reactor (multimodule build), even
from a child module. Using this flag, it's now possible to use a child
module - sorted to the end of the multimodule build process using
appropriate dependency declarations - to generate an assembly containing
module binaries.
Actually I had a workable but imperfect implementation that used the
older plugin until earlier this week. It bothered me because the Junit
tests were running twice for each build and this was supposed to fix
that. It did that -- and more :-(
I can always go back to that if I can't find an answer to this. But I
feel that I'm so close and just missing something simple.
beyond that -- somebody with more experience in asemblies will need to help
you.
Hope so, and thanks.
On Wed, Dec 29, 2010 at 11:38 AM, Steve Cohen<sco...@javactivity.org>wrote:
Here ya go:
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
