I think I have an answer.
Have the windows profile set the property
os-specific-descriptorwindows/os-specific-descriptor, then in the
installer profile, specify
descriptor${os-specific-descriptor}/descriptor
descriptorsrc/main/assembly/executable.xml/descriptor. To reduce
duplication, I'll need a no-installer profile which is activated
whenever installer isn't, but for the moment each OS-specific profile
will specify the descriptor name twice, which is still duplication,
but more localised than before!
Ricky.
2009/12/23 Ricky Clarkson ricky.clark...@gmail.com:
Hi,
I have one profile, windows, which configures the
maven-assembly-plugin with the src/main/assembly/win32.xml assembly
descriptor, and another profile, installer, which configures it with
the src/main/assembly/executable.xml assembly descriptor.
Unfortunately specifying -Pinstaller makes it so that the
effective-pom only refers to the src/main/assembly/executable.xml
descriptor.
Is there a way of making it so that the descriptors get aggregated
rather than replaced when specified from separate profiles, or is
there a better way of going about this problem that I'm missing?
Thanks,
Ricky.
--
Ricky Clarkson
Java and Scala Programmer, AD Holdings
Skype: ricky_clarkson
Google Talk: ricky.clark...@gmail.com
Google Wave: ricky.clark...@googlewave.com
--
Ricky Clarkson
Java and Scala Programmer, AD Holdings
Skype: ricky_clarkson
Google Talk: ricky.clark...@gmail.com
Google Wave: ricky.clark...@googlewave.com
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
