[jira] [Commented] (MASSEMBLY-870) Regression: Repository downloads all dependencies remotely into _tmp folders
[ https://issues.apache.org/jira/browse/MASSEMBLY-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538156#comment-17538156 ] Tamás Cservenák commented on MASSEMBLY-870: --- Confirmed, same as MASSEMBLY-874: due repository element, this error is triggered. > Regression: Repository downloads all dependencies remotely into _tmp folders > > > Key: MASSEMBLY-870 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-870 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 3.1.0 >Reporter: Tuomas Kiviaho >Priority: Major > > Repository {{_tmp}} folders under {{achive-tmp}} are filled with dependency > artifacts (.jar files and all) from pom which are not met by the filtering. I > noticed this when shifting from 2.6 to 3.1.0 and it is quite critical because > these dependencies do not come from local repo, but instead they are always > downloaded remotely. > I do have {{dependency:copy}} also before this plugin which doesn't do this > so I bet it has something to do with how the Aether is setup in > {{DefaultRepositoryAssembler}}. By removing the {{}} section > the assembly stopped this. > The end result is now that everything that I've got in my pom is being filled > into {{runner/tmp/repo_tmp}}. > {code} > > provided > false > > > org.mortbay.jetty.alpn:alpn-boot > > runner/tmp/repo > > > {code} > Once the assembly is complete the _tmp folder gets deleted and the end result > contains just that one jar file. > This is kind of a blocker, because I bet people have got used over the years > to cleaning the target folder so that they can get a nice assembly each time > a dependency is being upgraded despite the efforts of incremental builds. Due > to the cleaning there will always be repeated remote downloads because local > repository in settings is not utilized. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MASSEMBLY-870) Regression: Repository downloads all dependencies remotely into _tmp folders
[ https://issues.apache.org/jira/browse/MASSEMBLY-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16923097#comment-16923097 ] Tuomas Kiviaho commented on MASSEMBLY-870: -- And on top of that the artifacts that I had installed to local repo are not taken into account > Regression: Repository downloads all dependencies remotely into _tmp folders > > > Key: MASSEMBLY-870 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-870 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 3.1.0 >Reporter: Tuomas Kiviaho >Priority: Major > > Repository {{_tmp}} folders under {{achive-tmp}} are filled with dependency > artifacts (.jar files and all) from pom which are not met by the filtering. I > noticed this when shifting from 2.6 to 3.1.0 and it is quite critical because > these dependencies do not come from local repo, but instead they are always > downloaded remotely. > I do have {{dependency:copy}} also before this plugin which doesn't do this > so I bet it has something to do with how the Aether is setup in > {{DefaultRepositoryAssembler}}. By removing the {{}} section > the assembly stopped this. > The end result is now that everything that I've got in my pom is being filled > into {{runner/tmp/repo_tmp}}. > {code} > > provided > false > > > org.mortbay.jetty.alpn:alpn-boot > > runner/tmp/repo > > > {code} > Once the assembly is complete the _tmp folder gets deleted and the end result > contains just that one jar file. > This is kind of a blocker, because I bet people have got used over the years > to cleaning the target folder so that they can get a nice assembly each time > a dependency is being upgraded despite the efforts of incremental builds. Due > to the cleaning there will always be repeated remote downloads because local > repository in settings is not utilized. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (MASSEMBLY-870) Regression: Repository downloads all dependencies remotely into _tmp folders
[ https://issues.apache.org/jira/browse/MASSEMBLY-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16923089#comment-16923089 ] Tuomas Kiviaho commented on MASSEMBLY-870: -- I tried to upgrade from 2.6 to 3.1.1 and the problem still remains. Local repository is still not utilized and the build takes way too long. > Regression: Repository downloads all dependencies remotely into _tmp folders > > > Key: MASSEMBLY-870 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-870 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 3.1.0 >Reporter: Tuomas Kiviaho >Priority: Major > > Repository {{_tmp}} folders under {{achive-tmp}} are filled with dependency > artifacts (.jar files and all) from pom which are not met by the filtering. I > noticed this when shifting from 2.6 to 3.1.0 and it is quite critical because > these dependencies do not come from local repo, but instead they are always > downloaded remotely. > I do have {{dependency:copy}} also before this plugin which doesn't do this > so I bet it has something to do with how the Aether is setup in > {{DefaultRepositoryAssembler}}. By removing the {{}} section > the assembly stopped this. > The end result is now that everything that I've got in my pom is being filled > into {{runner/tmp/repo_tmp}}. > {code} > > provided > false > > > org.mortbay.jetty.alpn:alpn-boot > > runner/tmp/repo > > > {code} > Once the assembly is complete the _tmp folder gets deleted and the end result > contains just that one jar file. > This is kind of a blocker, because I bet people have got used over the years > to cleaning the target folder so that they can get a nice assembly each time > a dependency is being upgraded despite the efforts of incremental builds. Due > to the cleaning there will always be repeated remote downloads because local > repository in settings is not utilized. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (MASSEMBLY-870) Regression: Repository downloads all dependencies remotely into _tmp folders
[ https://issues.apache.org/jira/browse/MASSEMBLY-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178108#comment-16178108 ] Tuomas Kiviaho commented on MASSEMBLY-870: -- This was quite educating discussion http://maven.40175.n5.nabble.com/API-to-resolve-a-version-range-artifact-td5889934.html because https://github.com/apache/maven-plugins/blob/55da60389e9e8326a022bf6b93484978fdb263ed/maven-assembly-plugin/src/main/java/org/apache/maven/plugins/assembly/repository/DefaultRepositoryAssembler.java uses the same approach. [~rfscholte] I tested with my config that my invoker plugin still seems to be playing along nicely. I've been using the Fast Build Configuration https://maven.apache.org/plugins/maven-invoker-plugin/examples/fast-use.html and I think that kind of approach would solve this problem as well. > Regression: Repository downloads all dependencies remotely into _tmp folders > > > Key: MASSEMBLY-870 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-870 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 3.1.0 >Reporter: Tuomas Kiviaho > > Repository {{_tmp}} folders under {{achive-tmp}} are filled with dependency > artifacts (.jar files and all) from pom which are not met by the filtering. I > noticed this when shifting from 2.6 to 3.1.0 and it is quite critical because > these dependencies do not come from local repo, but instead they are always > downloaded remotely. > I do have {{dependency:copy}} also before this plugin which doesn't do this > so I bet it has something to do with how the Aether is setup in > {{DefaultRepositoryAssembler}}. By removing the {{}} section > the assembly stopped this. > The end result is now that everything that I've got in my pom is being filled > into {{runner/tmp/repo_tmp}}. > {code} > > provided > false > > > org.mortbay.jetty.alpn:alpn-boot > > runner/tmp/repo > > > {code} > Once the assembly is complete the _tmp folder gets deleted and the end result > contains just that one jar file. > This is kind of a blocker, because I bet people have got used over the years > to cleaning the target folder so that they can get a nice assembly each time > a dependency is being upgraded despite the efforts of incremental builds. Due > to the cleaning there will always be repeated remote downloads because local > repository in settings is not utilized. -- This message was sent by Atlassian JIRA (v6.4.14#64029)