A friend of mine and I were both experimenting with the assembly plugin this morning. It seems as if putting the appendAsssemblyId parameter to false causes the assembly not to get installed.
I've got a multiproject build. Let's say the overall project is com.mycompany.myproject:myproject:1.0. I have a top-level pom that (packaging pom, with modules) and submodules that use the top-level as parent POM and that create artifacts that I want to bundle into a distribution assembly. Because of the build order issue (top-level project will be packaged before sub-modules), I've put the distribution into a module. That module becomes com.mycompany.myproject:myproject-distribution:1.0. Because the module is already specific to the creation of a distribution, I don't really want an additional classifier. Right now, if my assembly id is 'distribution', I end up with the following in my repo: com/mycompany/myproject/myproject-distribution/1.0/myproject-distribution-1.0-distribution.zip (and .tar.gz). myproject-distribution-1.0-distribution.zip is a pretty ugly name, I imagine you'd agree. So I turned off appendAssemblyId, which gets me a good archive (myproject-distribution-1.0.zip), but no longer installs to the repository. I'm open to suggestions that either allow me not to append the assembly id, or other alternate suggestions that can get me an archive with a non-stupid (subjective, I know) name. - Geoffrey -- Geoffrey Wiseman
