Sorry:
https://github.com/apache/xalan-java/tree/xalan-java-mvn-refactored
(which currently has the binary assembly commented out).
Dependency order... Well, I'm currently running the assembly at the top
level, which would presumably mean it has to run after packaging of the
contained modules. I suppose I could try moving it down to the module at
the farthest end of the current dependency chain, or even into a new
module which exists just to depend on everything else, but that feels
like I'm solving the wrong problem; "give me an assembly for the whole
project" is conceptually a top-level operation and I'd expect to invoke
it from the root module.
On 11/10/2023 10:54 PM, Alexander Kriegisch wrote:
Tried making my top-level module dependent on all the others
Don't! That does not make any logical sense.
Checked in on xalan-java branch xalan-java-mvn-refactored
Please always provide a link. I have no idea where to find your project.
To you, that might be obvious. to others, it is not.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
