No, currently the dependency sorting approach is the only way. However,
you can lessen some of the burden of maintaining those dependencies in
the future if you use expressions for groupId and version in the
dependency declarations (something like ${project.groupId} if the dep
has the same groupId as the assembly, and ${project.version} if the dep
has the same version...like, it shares the same release cycle).
HTH,
-john
On 5/3/11 8:03 AM, David Tombs wrote:
Hello Maven Developers,
I assume you all are familiar with the Maven issue causing this
symptom:<http://jira.codehaus.org/browse/MASSEMBLY-94>. That report,
along with the assembly plugin FAQ, suggests an assembly-only child
module. This works, but has a remaining problem of manipulating that
child module's dependencies to get it to build last which requires
developers to remember to update that child's dependencies whenever
they add or remove modules.
Is there any resolution in sight to this issue? I tried to search for
a mailing list discussion, but couldn't find anything.
Thanks in advance,
David
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.johnofalltrades.name/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
