Hi, On Wed, 22 Apr 2020 at 08:20, Robert Oxspring <[email protected]> wrote:
> Hi all, > > I’m working on a multi module project where should-be no-op “mvn install > -DskipTests” takes multiple minutes and "assembly:single" appears to be > among the offenders - needlessly recreating archives when none of the > inputs have been modified. I’m considering modifying the plugin to avoid > this recreation, leading to the following questions… > > Would such a change be welcome? Is it important that the modified > behaviour is optional and not default? I figure the next step would be to > start hacking out a poc, but if you need me to raise a Jira issue or > something then please let me know. > yes such change would be welcome for sure (but optional per default until we are sure it works great and doesn't break anything) > > Should I be targeting my change at the assembly plugin or would it make > more sense to try and get this deeper into plexus-archiver? Do you have any > further advice where best to start?? > Well you're hitting the real problem: where to start :) the first question is how do you know nothing changed in the m-assembly-p inputs before you're starting it? (inputs are so many: jars, files, directories etc...) the first is to identify those inputs and then try to figure out how do I store the state of those inputs between 2 builds > > Are there reasons why this hasn’t been done before? - e.g. folks have died > on this hill and I should give up now. > some died for sure! > > What other questions should I be asking!? > so many so not sure where to start :) > > Thanks, > > Rob > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
