That wasn't my post at SO but it exactly describes my post. What I wanted to avoid is the duplication of the assembly descriptor.
Creating 2 projects would add too much complexity. I would have to add one project per filter that I want to apply (in this case, one per environment). For now I decided to use a component descriptor describing the main packaging, and let the assembly descriptors use the component. It's not the best solution but at least I don't have to duplicate a lot. Thanks for your help! On Thu, Jul 19, 2012 at 1:05 PM, Wayne Fay <[email protected]> wrote: > > Basically, I have an assembly descriptor that filters resources. > > I would like to produce two different assemblies, where each one uses the > > same descriptor but with a different filter. > > Looks like the "appendAssemblyId" option puts a bit of a constraint > because > > the names collide when installing in the repo. > > Use the appendAssemblyId and specify different <id> for the two > executions. Which is just what you're told to do in the SO post. > Otherwise you will need to make 2 projects, duplicate the assembly > plugin configuration, and specify different artifactIds. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
