... Right. I was thinking specifically about source assembly, where a good initial approximation is to include the same files checked into git. Obviously that's wrong for binary assembly, but having the option of "import ignore list into source excludes" would help keep the two in synch. And the basic selection pattern syntax seems close to the same.
Not a big deal to maintain manually; I'm just looking to automate what I can. -- /_ 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: John Patrick <nhoj.patr...@gmail.com> Sent: Saturday, November 11, 2023 6:18:43 AM To: Maven Users List <users@maven.apache.org> Subject: Re: Can the jar plugin respect .gitignore? my .gitignore includes target, so that would probably cause more issues with the assembly plugin. On Fri, 10 Nov 2023 at 21:34, <e...@zusammenkunft.net> wrote: > I think there are two issues with this, first of all git is not the only > SCM, so why prefer it’s file. > > But secondly it is very common that binary result artifacts are git > ignored and exactly the stuff you want to package. For example target/ > > Are you thinking about -src archives, only? > > Having said that, supporting the file format and patterns might be a good > idea (if it can be sorted out which directory level should be relevant) and > having a easy way to enable .*ignore. > > Joseph Kessselman wrote on 10. Nov 2023 19:42 (GMT +01:00): > > > (Or, equivalently be told to take exclude list from a file in .gitignore > > syntax and then be told .gitignore was that file.) > > > > If not, I'd consider that worth adding. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
