The "binary" assembly I'm trying to reproduce is the one our And project generated -- the artifact jarfile, plus source and input for the samples, plus the documentation directory -- basically, everything an end-user might want locally. I'm getting close to having that working.
Output directory in some places refers to directory within the archive. For example, I have it copying my Maven target/site/ directory to releaseName/docs/ inside the tar.gz and zip files, to confirm to past patterns. It isn't clear whether I should move the src assembly build down into this late processing module. Conceptually it belongs next to the bin assembly, but syntactically I think it's simpler in the parent pom. Unless I'm missing something. Again. Biggest remaining challenge: Again for convenience of folks who were used to the Ant build, I'd like to move/copy both bin and src assemblies to my Ant-emulation build/ directory. And again, if I try to do this with a separate copying operation it looks like I need another layer of dependency to ensure the bin assembly is generated before I copy it. Doable but not pretty. Having the assemblies write directly into build/ would be another solution if available. Random brainstorm, may be all wet: Maven might want to consider allowing users to specify priority. Phase is a good default/basic sequencing tool, but as the need to resort to dependencies shows, not quite complete by itself. If I could assign what amount to sub-phases by saying "this is higher or lower priority than anything else which runs in that phase", that might let me resolve cases where the phase alone is not enough to ensure desired sequence of operations... such as not running assembly until after other packaging is complete. -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ () Plaintext Ribbon Campaign /\ Stamp out HTML mail! ________________________________ From: Greg Chabala <greg.chab...@gmail.com> Sent: Saturday, November 11, 2023 12:38:05 PM To: Maven Users List <users@maven.apache.org> Subject: Re: Can the jar plugin respect .gitignore? I have no first hand experience using it, and only know of its existence as it's mentioned at the bottom the Reproducible Builds docs: https://reproducible-builds.org/docs/jvm/ Notably the maven-assembly-plugin documentation mentions a predefined 'project' descriptor which may also do just what you want(for buildable sources): https://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html#project You should be able to configure outputDirectory for either to place the assembly where you like: https://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#outputDirectory Didn't see a binary equivalent, but perhaps that would just be your normal build artifact?
